Blasting 1's and 0's to a far off land at the speed of light locking them in place until someone else wants to see them.
Any conversation
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
But maybe we'd all be a little saner if we remembered what we're actually doing: building tools to make our lives and the lives of others easier.
This resonated a lot. Iโm glad I read it now, before going totally insane lol. But I disagree that itโs just a glorified spreadsheet. The UI/UX matters, how you present the data, how they can change and so on, all of those things play a role. The good thing with AI is iteration is cheaper than ever, so you can experiment and process the results quickly. But yeah sometimes I just do things here because I just have to be doing something, I canโt leave it alone.
Agreed. The "just" makes the statement sound dismissive, but I do agree with the underlying sentiment that most software boils down to CRUD apps that help people organize information and complete tasks more efficiently. I think the path to developer enlightenment is realizing this truth without despairing over it.