You did the right thing. OOP was invented by people who were worried about their job security, to obstruct others from understanding their code.
ihan normi koodi työ ukko
You did the right thing. OOP was invented by people who were worried about their job security, to obstruct others from understanding their code.
Such a weird rule, but can’t disagree with the supreme court.
I hope it will not be Florida of 2000 election all over again, but in a massive scale.
It’s insane, Gore won by several thousand votes, if not tens of thousands.
In particular business logic that’s not obvious should be documented in comments.
// Typically 1 = 1, but on March accounting wants that 1 = 2. This function makes that mapping.
Just remember to mark all the things you’d like to make better but can’t be arsed to at the moment with numerous TODOs.
Hi colleague! So I found a comment in the code from 3 years ago by you saying you should “improve this”. Is it planned for the next sprint?
Few of the good ones I’ve spotted:
(complicated business logic in messy code) // TODO: check
(…) // TODO: think about better naming
(…) // TODO: This is obviously shit and needs to be changed.
(…) // TODO: THIS IS NOT USED ANYWHERE CONSIDER REMOVING ALTOGETHER (comment made 3 years ago)
I don’t think fusion would be as useful a technology as it would have been a few decades ago. Now renewables (wind, solar, hydro) seem like more and more as the clean and cheap energy of the future. The biggest problem of storage is rapidly being solved with batteries springing up everywhere.
The real problem with fusion is that even if it worked, the plants would be very complex and expensive. It would be much cheaper and reliable to build solar, wind and batteries instead.
Having operational fusion reactors would be cool as hell, but it wouldn’t have that much impact on our lives in the end.
The youngsters are downvoting you, but what you’re saying is sad but true. It’s the reason Bernie never ran as an independent, he knew it would hand the victory to republicans on a silver platter.
Do I understand this correctly, that the first astronaut’s realization is that all data structures are graphs?
If yes, that doesn’t make much sense. How is an array a graph?
That freedom becomes misery on the instant you have to start maintain the code from some other free spirit, whose style is totally different from yours.
I honestly found it funny in a kind of a cute way, but I guess others didn’t feel that way. Oh well, such is life sometimes.
Not to be a dick or anything, but I found it funny that you chose to mention the political career and your opinion of him. Nice touch, but very much irrelevant. Keep up the good work!
If you say so. However, feel free to be one of those people who discover later in life how their quality of life drastically went up with a bit of jogging or going to the gym. “If I had figured this out younger, I would have …” and so on.
Do you even lift bro?
Seriously though, doing some exercise could fix both of those problems. Kicking extinct fish doesn’t count.
Yes, I thought all magic works like that.
I wish this was possible without the whole god thing. What do you do during prayers etc.? Whenever I’ve attended a baptism or a funeral or some such, all I can think about is how much mana the priest is using when casting the bless on the audience. It gets so awkward.
I think they wanted people who follow orders to the dot, not people who have a sense of humor. Sounds like a terrible place to work, but I still understand their reasoning.
Bojack was pure gold. No idea about the rest.
Well, bad code is bad code regardless of the paradigm. I’ve just had bad experiences rewriting some horrible OOP codebases and opted out to use as much functional style as C# allowed me to.
The main problem, as I see it, is that OOP encourages unnecessary abstractions and inheritance. These should be used as little as possible, because they typically increase complexity and make code harder to read and untangle. As an example, I’ve seen people define interfaces that don’t essentially define anything.
Another problem is that OOP encourages mutable member variables. It’s very annoying to try to understand code where class C inherits from class B that inherits from class C. Good luck debugging when the methods of C modify a variable declared in A in subtle ways.
As an idea OOP is very appealing. When I was younger, I would be thrilled to start designing a class hierarchy and interfaces when encountering a new programming challenge. Now I just try to think how to make things as simple and modular as possible.
Edit: of course bad functional code is also bad code. It’s also very annoying to try to understand code where functions pass badly named functions around as parameters and use 10 function compositions in a sequence.