TOML

Interesting… me likes it.

It gets more fun if we’re talking SQL data via C API: is that 0 a field with 0 value or an actual NULL? Oracle’s Pro*C actually has an entirely different structure or indicator variables just to flag actual NULLs.

The code is my bible.

If there are no humans in the loop, sure, like for data transfer. But for, e.g., configuration files, i’d prefer a text-based solution instead of a binary one, JSON is a nice fit.

we’ve been out of IPv4 for over a decade now

Really? Haven’t had trouble allocating new VPSs with IPv4 as of late…

It’s funny because it’s true.

knowing majority of them support the agression against Ukraine

Do make me laugh with your sources.

It’s. A. Text. Editor.

Are you referring to any political views its author might’ve had? 'Cos all i could find is some charity stuff.

How is a text editor political?

Java has entered the chat…

Java is to Javascript what car is to carpet or somesuch

Corpos nagging corpos? I’ll get the popcorn.

No gold likes on lemmy? So sad…

Surely you’re not gonna blame the manager… /s

Right off the bat i read

One standout statistic was that projects with clear requirements documented before development started were 97 percent more likely to succeed. In comparison, one of the four pillars of the Agile Manifesto is “Working Software over Comprehensive Documentation.”

You need clearly defined requirements to write a good user story. Documentation comes after.

However, while the Agile Manifesto might have its problems, those stem more from its implementation rather than the principles themselves. “We don’t need a test team because we’re Agile” is a cost-saving abdication of responsibility.

Precisely, once once have i worked in a company where agile was properly implemented and, yes, user stories were well documented and discussed before being developed. All others are just waterfall in disguise, or Fragile™.

However, while the Agile Manifesto might have its problems, those stem more from its implementation rather than the principles themselves. “We don’t need a test team because we’re Agile” is a cost-saving abdication of responsibility.

A common case is a function that uses resources like opening files, sockets, whatever. If there’s an error you want to ensure a clean exit, so at different parts of said function you goto the end where you check if said resources are being used and release them before exiting.

Cleaner than constantly checking at every error.

I get that but it seems as though no one cares at all about efficiency these days.

When your CPU clock is measured in megahertz, your RAM is measured in kilobytes

Ah yes, the good ol’ days when developers programmed for efficiency.

You mean SpaghettiFactory()

Maybe for your use-cases, for mine i find it quite useful.