@cmddx When I was a teenager I was really into gamedev and demoscene and I wrote lots of little games and things, but whenever I tried to do something with a bit more scale the purist in me would demand that the entire project be had to be cross platform, or had to use a finite state machine to control program flow, or a fugging event pump and the project would immediately die the moment I found an edge case that broke the pattern/obsession.

I once spent 4 months optimising a pixel plotting routine in 386 assembler for a school project. It was really very fast, but the project was not to have the fastest pixels and I ended up triggering a CPU timing bug because the code was too optimized.

Look what I am trying to say is that:

a) I carry around the mental image of George Broussard from 3D Realms tweeting "cutting is shipping" right before his company collapsed

b) I can ~taste~ your post. I can feel the gentle whisper of it on the back of my neck. It leeches the marrow from my bones, cruelly snatches the warmth from my body. Your post haunts me and looms over the projects I manage quietly singing my doom.

@cmddx

There is place for if-else blocks and there is place for event systems. And where they fit does not depend only on what you are doing but also on what you have available at the moment. The time of the programmers who were starting with a blank canvas is long gone.

The most critical task programmers have of which the AI cannot relieve them is to decide what fits where when, and when things should be thrown away because they are no longer productive.

@cmddx I want to put the Litany Against Scope Creep on a poster or an Etsy cross stitch or something, but for content marketing.

I always think of cooler things to add to a project that are "easy" or "quick" while I'm researching it... And it adds another 10 pages to the end guide 😭

@cmddx

Sounds like a mentat to me.