jeffreygoesto

WAT?

Where have I seen something like this before. Right HAWK Hildesheim organized (locally) famous "Akkuschrauberrennen" https://m.youtube.com/results?sp=mAEA&search_query=akkuschra...

If only it had a good documentation. I really like the elkjs JavaScript version (thanks, Ulf!) bitte unfortunately transcoding makes transferring the Java docs even harder...

TIL. :) Thanks!

That is why I refurbished my Harman-Kardon amp from 1991 and listen CDs and LPs through it increasingly these days. It drives either some Revox speakers I be also bought at that time or a HifiMan Edition XS. That thing is outright amazing. The pinnacle of mixing was in the 80s as far as my collection is concerned. The 70s were much experimenting and the 90s already too compressed.

What was the playlist though?

They will be shocked. SHOCKED.

Dunno. Zapping the inodes seems almost surgical compared to truncating byte by byte for example? Or do you think you buried them alive that way? Are they still lurking in some dark, uncharted alleys of your filesystem until the final OVERWRITER comes?

Hu!?

https://fedoraproject.org/ for example. SCNR

Meanwhile in Germany (facepalm) https://www.br.de/nachrichten/bayern/wenn-die-eigene-photovo...

I immediately thought "Edward Lee" when I read the title. And sure...

His seminal paper "The problem with threads" [0] and others inspired [1] a lot.

Boy would I love to see what would have happened if he and Joe Armstrong would have collaborated...

[0] https://ptolemy.berkeley.edu/publications/papers/06/problemw...

[1] https://edms.etas.com/

Did you just invent "agile" maybe. ;)

Can't help but think "Doesn't matter if a machine or a human with (even slightly) different background wrote it", maximizing information flow is maximizing common assumptions and "culture" to only have to communicate a small set of current information for the task at hand. Being a team means having built a joint context so to say. This has always been the purpose of design documents and they always were too big or too small. Because you did not write them, but the others. If you only produce code you think they are the past and useless. If you iterate and your team grows, you start seeing the value in always current docs that are containing just what is not in your everyday culture.

All the best for you and your growing family. I had a similar experience recalibrating my values...

All extrapolations are wrong. Even this one. We just don't know how.

The article revolves a lot around the "how" and "why" but does not really answer it's own title. We thought we have the answer right there: in democracies, the people delegates working out the rules to a group of elected people. The rules then are enforced by another, independent group of people. Currently this seems to be broken in (not only) the USA.

Lamport & Chandy, right?

We are using Loom with a C++ adapter for such things. Works reasonably well for us.

To be human is like being the training so much more than the execution. Like the parallel post's game where the speed of light is 5km/h, we always try to but never reach true "perfection" (setting aside the discourse what that even would be). Some overfit, some stop short of being good...

Even if you think you don't have enough impact, reflecting on these issues is better than blindly jumping into the trend.

Reminds me a bit of https://www.amazon.com/Job-Went-India-Pragmatic-Programmers/... tbh (look when that came out), not nearly the same scale but similar questions...

Did you consider writing a small Python script for that?

Somebody wrote in another thread: "intelligence is compression". So. Defaulting to slop is intelligent now. Saves a lot of time and energy.

L9: solving actual problems with A"I", not just increasing the speed of a crappy loop.

Reminds me of a story a coworker told me about his band rehearsal when the new drummer counted one-two-three-four-five-six-se-ven-eight.

Readme sais C++26?

Oh no. As if we didn't have generations of programmers speed running with test code through what is instead of testing what shall be. That must have leaked into the training set...

"The thing I did not anticipate is how much of the value was in the second-order lessons. Nobody files an advisory titled “your REVOKE statements are decorative.” You only learn that by doing the remediation with a paranoid person looking over your shoulder, and then checking the catalogs instead of believing the migration output."

Is such a good and grown up summary. Kudos for writing this up.

We are taking turns in small teams being on duty for only finding and fixing bugs for two weeks. They are working on features with a much sharpened eye after and don't repeat bad habits so easily. Having drilled down to the core gives you the necessary understanding.

An instance of https://profserious.substack.com/p/the-bureaucratic-escalato... ?

You get what 1000 average redditors and stack overflowers would do to your codebase. Not your taste, theirs. Like all the images generated look like the same crap. No messaging from human to human any more.

I mean. For what? For whom?

Do you have to go into that extreme? Could you go back to use it as just one of your tools?

From the headline I was afraid it would be about prisoners of war first.

I loved the comparison of HerbCeptions with expected in https://m.youtube.com/watch?v=GC4cp4U2f2E, a very insightful easy of looking at that topic and really entertaining, too.