There are now a whole new class of potential issues, design considerations, and challenges that Rust introduces to web developers which I think is often under-estimated.

Fixing one ownership issue often just shifts the problem to another place, and without a strong understanding of this mental model, it can be very difficult to identify which path from any given node is actually the "right" one, which gets closer to the real solution.

The documentation is awesome, but some crates are under-documented.

Editing Rust is not so much supported in VSCode than Typescript.

The feedback comes from a typescript developer.

Human feedbacks

Never mind that you can also harvest code from any of your shelved projects. I mean why rewrite the Fisher–Yates shuffle algorithm if you have it already in a shelved game? Code for switching the monitor depth (on those early Macs) I moved from game to game… Polygon-point collision code, a sine lookup-table for quick trig functions, a dot-product routine, cross-product routines…

was the whole exercise of my guerilla programming technique a wash? Maybe. But it always served me well

There were times too when a coworker might have said, “You should have used a Bloom Filter” and I was able to come back with, “Yeah, already tried that but the typical data we are seeing is so small that the performance gains were negligible and added unnecessary complexity to the code base so I tossed it.” Boom!

A.B.I Always Be Iterating.

How the author evolved about getting news and updates.
First from social media, then from a curated list on Reddit.
To multiple RSS readers (Feeder, Miniflux) to Yarr.

They share their feeds in the post too :)

A feeback about starting a small business. It is full of insights and experiences.

About running Blue Dwarf

"workarounds to cyber security are the norm, rather than the exception. They not only go unpunished, they go unnoticed in most settings—and often are taught as correct practice."

About IT in healthcare systems. The article provide many examples.

The author avoided debt, but was it worth it?

A great feedback

Mann kann erst skalieren, dann optimieren, wenn es ein Drittels des Tages dauert. Der erste Prozess, um PDFs zu erzeugen, ist total innefizient. Es zeigt auch, dass Optimierungen der letzte Schritt des Produkts ist. Sie haben damit lange gelebt. Die Architektur ist eine gute Beispiel für horizontale Skalierung.

An experience with Axum.