fzeindl

I think so too. And it reminds me that I refactored Leaflet's core event-handling and SVG rendering code 8 years ago. It's good to know your opensource contribution play part in such cool things.

Repairing / fixing / retrofitting an old code base always has it's wonders. I've seen much code in my life that was in a bad shape and my approach for fixing was seldomly the same, it was always tailored to the team and situation.

To rephrase from Tolstoy: "Good code bases are all alike, every bad code base is bad in it's own way."

Who would be able to open a 1000 issues? Are you referring to trolls?

You are saying people have less time for their projects now as compared to 10 years ago.

There are so many opensource-projects now as compared to 10 years ago, especially in JavaScript-land, which have an unbelievable number of open bugs.

This is terrible because the majority of these bugs seem to be low-quality, so even if you are a seasoned developer with contribution experience, opening up a bug with the incentive to help simply gets you ignored.

I'm waiting for a bug in next.js at the moment where 404 does not return 404, that has been open for months (https://github.com/vercel/next.js/issues/51021). I don't have the time of writing a PR, but I have written countless PRs and bug-reports and worked on many other open-source projects, so I think I have done my share.

It is elitist, but I wish there was a way for maintainers to sort bugs by the reputation of the reporter, so projects can prioritize high-quality issues.

I write about software engineering and -architecture, am proud about this https://www.fabianzeindl.com/posts/the-codequality-pyramid

Abstraction layers tend to be slow.

What they should focus on is plumbing. Take what exists and connect it in a smart way.

Take React: the idea of applying functional programming and spitting out HTML was a great idea. HTML existed before react. Then they also implemented a virtual-DOM, which was the unnecessary part.

Or react-native: rendering UIs in a functional way is great, but stuffing JavaScript into everything is not necessary.

In Switzerland there are laws covering biddings, where the state has to accept the second to lowest offering, not the lowest, thereby circumventing this race.

1. by using finalizers

2. by using object initialization blocks

If you avoid these two problems you get nano-second performance, because the JVM does not need to run code during object creation and GC.

How do you fix issues with the docker images if you don't understand them?

What do you mean by "top of the tower"? If you refer to my position as software architect, that has nothing to do with it.

I worked at many companies and meeting length was ALWAYS a factor of the company culture not of my role.

Personally I schedule meeting that take 45 minutes max. Most of the time i schedule 25 minutes. The 5 minutes are so people have a break in their Outlook calendar.

It works rather well, it's not confusing at all and if you really want something else you can use require etc.

I disagree here.

But what I found LLMs really useful for is summarizing topics like: "Suppose I want to do XYZ, which steps should I take?" or "I want to write about ABC, how would you structure the article?"

The content is not very good if you look at it in detail, but LLMs provide good overviews and gave me ideas on parts of a topic I overlooked.

More librarian than search engine. I cannot copy and paste and rely on the results but I can rely on that they point me in a good direction.

You can turn this behavior off as site owner.

Agree wholeheartedly. Elixir/BEAM/Erlang are a league of their own.

If the brain could be changed easily it would be very unstable and humanity might have died out very fast.

That is an artificial distinction you made up. I have written many apps and desktop applications, all of which where using 3-10 threads, some of them doing "parallel" work meaning the parallel computation of divide and conquer algorithms, some were doing concurrent work.

I tried async often. I threw it away every single time, because it "infects" the entire codebase. I suspect the only reason async exists is because the Javascript event-loop is single-threaded and there are no blocking primitives in JS. If you don't have access to blocking data-handoff between threads, you can choose between callback hell or async/await.

Please take a look at the video I posted earlier.

A nice talk about this: https://www.reddit.com/r/programming/comments/da141r/ron_pre...

Modern train have an electromagnetic emergency brake system that uses a large magnet lowered onto the rail to stop.

Also the standard braking system using fluids has a clever indirection where it does not activate the brake when pressure rises but when it drops. This is because when a waggon gets loose and the braking line rips and fluids get's out, the waggon should immediately brake as soon as pressure drops.

Maybe there was a fault in the circuitry to begin with.