Isn’t problem solving mostly put things together of what you’ve learned before?
I have a great uncle. The best uncle. He’s telling I’m the best Pokémon player by the way. He works at Nintendo. It’s a wonderful company I tell you. And do you know what he say? It’s all true!
Imagine doing whatever I want with my free time.
It’s an entertaining video. I watched it to have something in the background while doing chores.
I agree that people shouldn’t have to die over this, but Putin is dedicated to the invasion on Ukraine. He won’t stop just because someone kindly ask him to stop over the phone. He’ll continue until there’s no Ukraine anymore, and then he might also go for Moldova and other former Soviet countries.
Ukraine has to defend themselves for as long as Putin is willing to continue the war.
Go tell Putin and his friends to stop the invasion and hand back all the Ukrainian territory they’ve stolen. It’s easy!
I agree, and I count that as “key information that’s difficult to understand from the code”.
IMO, comments should be used to provide value to the code. If they’re used too much, then readers of the code will more likely stop reading them altogether. They already got what they need from the code itself and the comments usually don’t add much value.
If they’re sparse, then that’s a good indication they’re important and shouldn’t be missed.
I think comments are good as a last resort when it’s difficult to communicate the intention of the code with other means.
If I find code that’s hard to understand, I’ll first try to find better variable or function names. Often this is enough.
If it’s still too difficult to understand, I try to restructure the code to better communicate the flow of the code.
If that doesn’t help (or is too difficult), then I might add a comment explaining key information that’s difficult to understand from the code.
It was featured in a PlayStation showcase last year. The most notable part of the trailer was a burger. I’m not kidding.
There’s also the $100 million development cost
Joseph Anderson has made a similar trolley challenge. It’s a cinematic masterpiece: https://youtu.be/RgqRIFj4Zrk
I liked when they said “it’s concording time” and concorded all over the place.
Right now I’m mostly using the Xbox One controller (on PC). It’s a controller that feels really good to hold. No weird gimmicks like motion control either. I think it’s one of the all time greats.
Runner up is GameCube.
Shit in terms of having no players and being pulled back after just two weeks.
From what I understand, the game itself was alright. It had no major technical or gameplay problems. At least the team of programmers and game designers were competent.
The main issue is that the game was incredibly unappealing, and I believe this can only come from poor leadership.
It’s probably not even the artists fault it turned out this shit. My gut feeling is that the game is victim of incompetent leadership. Indecisiveness on important matters and micro management on stupid things.
It’s also the same incompetent leadership who will get bonuses and promotions after this.
The only problem is to ensure the entire team agrees to only use it like an interface and nothing else. But I guess that’s the only proper way to do it in C++, for now.
In your example, the declaration of ArrayList look like:
public class ArrayList extends AbstractList implements List {
}
The dependence on AbstractList is public. Any public method in AbstractList is also accessible from the outside. It opens up for tricky dependencies that can be difficult to unravel.
Compare it with my solution:
public class ArrayList implements List {
private AbstractList = new AbstractList();
}
Nothing about the internals of ArrayList is exposed. You’re free to change the internals however you want. There’s no chance any outside code will depend on this implementation detail.
If the lists have shared components then that can be solved with composition. It’s semantically the same as using abstract classes, but with the difference that this code dependency doesn’t need to be exposed to the outside. This makes the dependency more loosely coupled.
I usually break it out using composition if that’s ever needed. Either by wrapping around all the implementations, or as a separate component that is injected into each implementation.
What’s happening is that support from VC money is drying up. Tech companies have for a long time survived on the promise that they will eventually be much more profitable in the future. It doesn’t matter if it’s not profitable today. They will be in the future.
Now we’re in a period where there’s more pressure on tech companies to be profitable today. That’s why they’re going for such anti consumer behaviors. They want to make more with less.
I’m not sure if there’s a bubble bursting. It could just be a plateau.