magic_lobster_party @ magic_lobster_party @fedia.io

Posts

0

Comments

417

Joined

11 mo. ago

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 like to mix between OOP and FP for different levels. OOP is great for higher architectural problems. FP is great for everything under it.

And yes, inheritance was a huge mistake. Just use composition and interfaces instead.

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 JSON is more robust than XML by now. Mostly due to its simplicity. There are few reasons why anyone would pick XML over JSON these days.

It makes you want to die on a hill

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.

Yes, I think so. The downside with Python comes when refactoring the code. There’s always this double checking if the code is correctly indented after the refactor. Sometimes small mistakes creep in.

It’s really hard to tell when Python code is incorrectly indented. It’s often still valid Python code, but you can’t tell if it’s wrong unless you know the intention of the code.

In order languages it’s always obvious when code is incorrectly indented. There’s no ambiguity.

I don’t like YAML because it’s overly complicated. The specification is like 80 pages long. How the hell did they think that was a good idea?

JSON on the other hand is super simple. It doesn’t do more than it needs to.

Just compare this: https://yaml.org/spec/1.2.2/

With this: https://www.json.org/json-en.html

The entire JSON specification is shorter than just the table of contents of the YAML specification!

Another thing I like about JSON is that you can format it however you want with the whitespace. Want everything on one line? Just write everything on one line!

If data can be represented as a JSON, then there’s generally only one way to represent it in JSON (apart from whitespace). In YAML the same data can be represented in 1000s of different ways. You pick one.

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.

Turn on a lamp

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.