It is if you don’t get pay to run, getting anywhere faster doesn’t help you at all, and it costs more energy. And you gain nothing from it. That’s my point.

These people don’t get to pick whether they use Excel, either. They have to, they just want to get their job done and go home, too.

They don’t get paid to walk upright, basically. So why do it just so someone else can buy another yacht?

Hrm, I would argue that if your update gets in the way of productivity on the user side, then it’s actually worse, not better.

Sure, in a vacuum it might be superior, but that is now what is happening.

We used to rail against our users always wanting an Excel like view for everything, but when you observe them working to understand their work flow it makes sense. They use excel the other 75%of the day, we’re the one breaking their mental flow and ruining their productivity.

Relax, it’s just JSON. If you wanted to not be stringly-typed, you’d have not used JSON.

(though to be fair, I hate it when people do bullshit types, but they got a point in that you ought to not use JSON in the first place if it matters)

This is their “light IDE” basically, the equivalent of VS Code. Their Java IDE is the full thing, well, Eclipse. Although I personally prefer IntelliJ IDEA.

I don’t really need another text editor, sorry.

This is depressingly accurate. 😓

Also the strip stops midway through as Waterfall was an invented thing just for a paper. And during your UP work you actually had the customer put in that input and hence it was like in this cartoon strip.

Because it keeps being crossposted everywhere. Sadly.

Yeah, parts of this article feel like they’ve been written by a GenAI. Which… might have been the point, I suppose.

It’s because the same people who wrote the code usually write the docs, and people who are really good at writing code usually aren’t good at writing docs. It’s two different skill sets that usually don’t coincide.

This is why companies ought to employ technical writers if they have enough documentation. Of course, few ever do, but it’d by the Right Thing™️ to do.

I live in one of Germany’s largest cities, and while this is high, it’s not outrageously high.

I guess to me what sticks out the most is the expected 20% surcharge for “tips” (that get collected by the bosses indirectly anyways as they just underpay their slaves enough to make up for the tips they’re getting). That’s not normal here. You tip for good service, if you pay in cash you also tip to round usually, and you tip if there’s some other outstandingly positive thing about it. I really hate how in the US it’s become so expected to tip, while also having fuck all protection for the delivery drivers, who ought to get a wage where tips are a bonus, not an expectation. It’s just a delivery fee at this point, let’s be honest.

Although I will also say that since I live basically next door to a Dominos, I always pick up, which is ~25%-30% cheaper than delivery. Plus no delivery charge, but that’s based on distance I imagine.

Of course, it’s going to be difficult to find a modern application where each individually deployed component isn’t at least 7MB of compiled source (and 50-200MB of container), compared to this single 7MB war that contained everything.

People want a chat app. If your secure chat app sucks as a chat app, it doesn’t matter how secure it is. It failed the primary use case it was meant to be developed for.

But keep in mind, Signal’s nature is no excuse to have shitty app implementations. In particular to have desktop apps as second-class citizens (and tablets as exterminated not-citizens). You can be a secure chat app. Signal got the secure part done, they’re just struggling with the chat app part.

Signal’s desktop app is as horrendously unusably bad as the project as a whole is good, tbh.

It’s no wonder people prefer stuff like Telegram. It has native apps and all. Or can be used in a browser. Meanwhile Signal is only used in a browser, but you have to download it and it fucks up font scaling and it shits the bed on font antialiasing and it can’t even get UI design consistent with the OS it’s running on and it won’t even use the OS emoji font.

Let’s not even mention how you still cannot use Signal on a tablet.

Yeah was about to say, my phone can’t even tell whether I’m walking or cycling or taking a bus, I have exactly 0 hope it could tell whether I’m driving or not other than not being connected to my car’s bluetooth which will be exactly what they are doing here of course!

I mean that’s pretty neat, but I’m reminded of that time a MongoDB user found an SQL-based database and wrote a lengthy article about all of the revolutionary features. Feels the same every time a Javascript dev discovers a programming language with actual typing.

Seems cool, but also… normal? That’s how languages should all work?

Unified process, which, despite usually not being called that way and/or being codified in the way it is nowadays, is how virtually all early software companies did their development work post-punchcards (when you no longer had to get things done in a single step).

It’s why the “agile is better because iterative hoooo!” is so laughable, because even though we didn’t yet call it iterative - as a distinction from pre-planned, since we thought in punchcards+mainframe vs after that - we did iterative work. Of course we did, software development is naturally iterative and Waterfall was the contrived contrasting example of how a non-iterative process would look.

Definitely. Most often it’s people misunderstanding the “a over b” of agile as “never do b”.

It wasn’t, Waterfall in itself was a contrived example of a bad setup. More common was UP, or something UP-like.