fn1

We should stop calling it "technical debt". That word suggests a clean account that can be paid off from time to time.

Instead let's call it "technical clutter", because that is what it is.

It's the equivalent of an unclean workshop with broken and unused tools lying around. You trip over everything, you cannot find anything, your tools hurt you or slow you down.

Managers need to understand that technical clutter is central in hindering and slowing development. Not a separate account that is not affecting work.

I don't get this. Isn't the main benefit of next.js proper splitting of server/client code, prerendering and such?

None of that is needed on a native platform.

I wonder if many of the problems with automatic driving could be solved using platooning (https://www.youtube.com/watch?v=lpuwG4A56r0, https://www.youtube.com/watch?v=9Re__KRr4NU).

There could be dedicated lanes assigned to the autonomous cars and platooning-protocols that ensure that the cars use their automatic capabilities only on relatively safe highways, only queued between other autonomic vehicles.

Should be a more predictable environment and thereby safer

There's a nice article by Martin Fowler about this topic: https://martinfowler.com/articles/cd4ml.html

* A german book about functional programming in Haskell, Opal, ML and Gofer. [1] * Some introduction into "Communicating sequential processes" (I cannot recall which one) to get a proper concept about safe ways of multithreading. * "Linux for dummies" to get a firm understanding about unix, the shell etc.

[1] https://www.weltbild.at/artikel/buch/funktionale-programmier...

A tip, since i see a UPC modem: The puma6 chipset has a bug which causes various latency issues and connection drops on Wifi. Better use a different WifiRouter behind the modem.

Why is consciousness always assumed to be a constant? Why not rather call it introspection?

If you zone out, are you still conscious? Or if you are watching a movie and not thinking about yourself, are you still conscious?

I know this comment is not very helpful, but the lack of a module-system and the lack of threading are unfortunately the biggest issues that JavaScript had from the start.

* Use an IDE (Like IntelliJ Idea)

* If there's no architecture-document that gives a short (3-5) page overview on the layout of the code then start writing one.

* Skim through the folders / packages / classes and write down a few obvious questions that pop into your mind while "speedreading" the code.

* Try to make an improvement to see how the whole CI/CD process works.

* Look through the list of direct dependencies / libraries and see where they are used.

No, Kotlin since 2015, TypeScript since 2017.

I have programmed Java/Kotlin/TypeScript for 5+ years in terminal/vim. Then for 3 years in Eclipse. Then for 8 years in Intellij IDEA.

I would never go back to VIM for coding.

> Just about every array operation I could want is there, waiting for a code block. In other languages, things don’t flow like that.

This is a question about standard-library. The standard-library of kotlin is equally amazing (but Kotlin more or less requires the IntelliJ eco-system of course).

16. Avoid helm.

Why not build a scanner for common structures like "isArray" and automatically submit a PR to replace the usage with built-in tools or something like lodash.

(I know program comparison is akin to the halting-problem, but for simple templates it should work).

> We are still in the early days of software where lots of people are clamouring to invent the silver bullet to make it all work better [...]

I have a feeling that (especially in devOps/kubernetes) often there is a wish to have a magic button/command that does everything. Like in a rube-goldberg machine.

What is forgotten then is the cognitive overhead of templating YAML inside templating YAML which is needed for the magic-button to be configured.

And if the buttons behaviour needs to be changed very few weeks, not much is gained.

I have found that both Microservices and serverless work well for "batch-type" writing applications where data is processed asynchronously.

It does not work so well for interactive reading applications like a REST-api.

I have added "slow".

I have added more languages. C++ scraping does not work yet for some reason.

> This one is curious. The website appears to suggest that the list of open issues being presented was generated over 4 months ago.

It was generated today. 6.10, not 10.6. Fixed it.

> My second question is what is driving the short list of technologies?

I will add more languages.

I second that. I love splunk as well.

Costs can also be reduced by spending some development-effort into abbreviating logs and being smart about deciding what to log and where.

This is because "Copy'n'paste" programming get's more and more common.

I see more and more juniors pasting code or shellcommands from StackOverflow with careless ease, without even pretending anymore that they're interested in how it actually works.

> how hard it is to implement a modern filesystem that won't eat users' data.

Why is that so hard? Because of edge-cases? Caching/Timing considerations?

> Re-form the Police

Triple their pay, but also enforce strict no-tolerance rules on misbehaviour and select candidates more carefully.

> but postgres' support means I still can should I ever need to.

And since postgres supports indices on arbitrary expressions you can use CREATE INDEX for the json-queries in your WHERE:

CREATE INDEX ON publishers((info->>'name'));

The testing suite for the JDK, which allows you to tell if something is compatible to Oracle Java.

> where you'll try (unsuccessfully) to merge user profiles and data.

Why? Can't a monolith be refactored?

Semmelweis did not go insane.

He was actually one of the fathers of evidence-based medicine by counting number of death in hospitals after child-birth.

He discovered that when women where treated by doctors MORE deaths occurred than when women where treated by nurses. The reason for this might have been that the doctors also dissected corpses at university and brought germs from this when examining women.

That was the problem of the message: He postulated that his peers, the noble doctors were directly responsible for a high number of deaths. This was a message nobody wanted to hear.

Since he became more and more outspoken and angry that nobody believed him, they shut him up by luring him into an asylum where he died.

Later his methods were approved, since the young students had no bad conscience about having indirectly killed women in their career.

> If you thought managed memory was good, wait until languages start managing access control, authentication, concurrency and persistence layers for you.

This exists in 4GLs (https://en.m.wikipedia.org/wiki/Fourth-generation_programmin...)

This came up in the javascript-world.

Just a small tipp: Doing a pullup mostly depends on the latissimus dorsi muscle. It's about keeping a steady, stable body while pulling. Pull with your back, not only with your arms.