Again, did you actually read the comments?

Is SQL an API contract using JSON? I hardly think so.

Java does not distinguish between null and non-existence within an API contract. Neither does Python. JS is the weird one here for having two different identifiers.

Why are you so hellbent on proving something universal that doesn’t apply for the case specified above? Seriously, you’re the “well, ackshually” meme in person. You are unable or unwilling to distinguish between abstract and concrete. And that makes you pretty bad engineers.

Did you read the comments above?

You can’t just ignore context and proclaim some universal truth, which just happens to be your opinion.

Nope.

If there’s a clear definition that there can be something, implicit and explicit omission are equivalent. And that’s exactly the case we’re talking about here.

That’s exactly not the thing, because nobody broke the contract, they simply interpret it differently in details.

Having a null reference is perfectly valid json, as long as it’s not explicitly prohibited. Null just says “nothing in here” and that’s exactly what an omission also communicates.

The difference is just whether you treat implicit and explicit non-existence differently. And neither interpretation is wrong per contract.

It can, but especially during serialization Java sometimes adds null references to null values.

That’s usually a mistake by the API designer and/or Java dev, but happens pretty often.

Well, yes, but the underlying issues still persist, so it’s not exactly a sustainable strategy.

I have to say, I’m getting more and more frustrated by the bad code I have to write due to bad business circumstances.

I want clean, readable code with proper documentation and at least a bit of internal consistency and not the shoehorned mess of hacks, todos and weird corner cases.

They re-invent everything for no reason. Every mundane device has been “re-invented” using big data, blockchain, VR, now AI and in a few years probably quantum-something.

The entire tech world fundamentally ran out of ideas. The usual pipeline is basic research > applied research > products, but since money only gets thrown at products, there’s nothing left to do research. So the tech bros have to re-iterate on the same concepts again and again.

Summary: nothing of value

uNuSeD rAm Is WaStEd RaM!!!

And the new Teams is not simply a replacement, no. It’s called “Teams (for work or school)” or something, while the old app is “Teams classic”. Both look the same and are the same sluggish mess. So why exactly did we do all that crap?

Again, that’s not what obfuscation means.

Also, what exactly is the difference between cat and journalctl? You can’t read a text file without a program either.

Of course, raw text files are more common, but what you’re drawing up here is a mixture of old man yells at cloud and tin foil hat territory.

So literally every program on your machine is obfuscated. Linux kernel? Obfuscated. Wayland? Obfuscated. And even VIM: obfuscated.

You’re creating problems where there are none.

Are you really sure, you’re using “obfuscation” right? Because that implies that someone intentionally makes something harder to read to hide something. That’s not the case here. Nothing is hidden, it’s all there, the formats are well defined and easy to read.

Das wäre möglich, aber die Verwaltung kriegt das nicht hin.

Die könnten das einfach als Teil der Ausschreibung aufnehmen, aber das tun sie nicht. Und für die Hersteller ist das auch gut, weil man dann ganz schöne fuckups einfach unter den Teppich kehren kann. Ask me how I know…

Es ist leider so, dass die “IT” Abteilungen in vielen Behörden einfach gnadenlos unterbesetzt sind und deswegen quasi Geld verschwenden müssen. Teilweise sind da dann nur drei Leute, die einfach nur die verschiedenen Dienstleister jonglieren. Für mehr Personal gibt’s aber kein Geld und für 50k kriegst du halt auch niemanden.

I think you are either trolling or you fundamentally don’t understand, what you’re talking about.

Nothing is obfuscated. You can download each and every code file, audit it, and build the binaries from exactly that code. You can even compare the binaries to the ones provided by major distros thanks to reproducible builds.

Just because you don’t understand code, doesn’t mean it’s obfuscated. Following that logic, even a loaf of bread is “obfuscated” because you don’t understand sour dough.

Weil die Leute es mit sich machen lassen und momentan tatsächlich absolute Flaute auf dem Arbeitsmarkt ist.

Wir haben seit einiger Zeit offene Stellen für die ganze in-house IT in mehreren Positionen und Skilllevels offen. Soweit ich das einschätzen kann, ist das Gehalt wohl auch ganz okay. Aber es kommen kaum Leute und erst recht keine qualifizierten.

Zumindest FISI bilden wir selbst aus, aber da wir die auch langfristig planen müssen, ist da für Einstellungspraxis natürlich eher konservativ.

Die sind dermaßen überarbeitet, dass die den Witz nicht verstehen würden.

Dieser Preis ist das einzig gute Argument gegen Home Office. Ich kann das nirgendwo raufkleben, weil das Büro 250km entfernt ist.

It’s because they think it’s what you’re doing for a large project. Simple as that. There’s no future demand, the client doesn’t care, and I’m not right because they said so.