I find myself building bespoke tooling for my own #swdevnotesfollow and #ainotesfollow workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
..then of course I have to contend with - "Is this going to be a maintenance nightmare in the future?" and then I still usually conclude "no, the maintenance will be aided by the same approach that the construction was".
It's interesting how dramatically and quickly the scales have changed in this equation - and for such a wide range of software.
For example, I am looking for a coding agent coordinator with a particular (but not all that insane) set of requirements. I used both Claude and Perplexity to show me options and break them down by fit against my requirements.
I got completely different lists! No overlap!
And no perfect fits.
It will become increasingly harder to find niche markets for software when those people can just build it themselves exactly how they want it. In the end, people want to accomplish tasks, and the AI is going to be building the software on-the-fly exactly for that task, why do we need generic software that may or may not be a fit?
Yeah. It makes me think that protocols for exchanging data between apps will become even more important in that landscape. But maybe, not - maybe each exchange is another bespoke AI-driven implementation?
Protocols, infrastructure, containers, those kinds of things. I was actually playing around with an idea for a minimal markup language + runtime that can be utilized by AI to spin up apps more easily, and brainstorming it with ChatGPT, I have a feeling something like that will appear soon to complement MCP.
i recently finished hemingways "the old man and the sea". very highly recommend for anybody that wants something short and memorable. left me feeling something between inspired and nihilistic
This strangely reminded me of golden days of Twitter. There was a point I absolutely love Twitter. This is also a reminder for me to pick up a book instead of reading a load of random stuff online.
Thank you!
Big holiday today in Greece, bells ringing, bands singing, people gathered in the village, eating, enjoying life and I'm spending it inside coding. I don't feel bad and I'm not #antisocialnotesfollow, it's just that I'm a bit odd. I don't like these forced gatherings. Feel stressful.
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
hot take: "consumer #ainotesfollow " doesn't exist. at most it's just better search, but the ai assistants like grokbot or now instinct aren't ever going to be big. new devices and personal agents are DOA
textlog runs on a 2.5€/mo vps 1 core/2gb ram, using just one instance of Bun with its embedded SQLite. Works perfect and I run a few other apps as well on that machine.