Emil B

I guess that’s it, the “new js framework every week” era is over. No new ideas, no QoL improvements. We are just stuck with what we have forever

All engineering effort is being rerouted. If you can implement a flawed standard in 10x less time, why bother improving the standard itself? You’ll literally gain more by improving compile times, so that’s the focus now

There’s always visible degradation in services/products when a provider decides to become “everything.” Retailers pushing their own branded products, apps closing integrations and rebuilding third-party features themselves (Claude, X). Streaming platforms producing their own content (Netflix)

result: quality goes down, previous partners get pushed out of business, new players struggle to enter the market, innovation slows

Hot take on LLMs: they exist largely because humanity has failed at systems engineering. We keep producing half-baked standards with too much room for interpretation. Then we ship new fixed versions with backward compatibility. Then another standard appears And the cycle repeats over and over

Thousands of frameworks. Thousands of incompatible APIs. Auth systems full of foot-guns. CLIs nobody remembers how to use. We can’t seem to build tools that are as simple as going to an LLM and saying: "I need you to do this"

big tech social apps algorithms don’t even need you to open a post anymore. Leave it on your screen a few seconds longer than usual and you’re pushed into suggestion hell. And I really need "It was a mistake, forget I was here" button on youtube, tired of opening videos in incognito mode

Love the tech behind bluesky and atproto. The overall decentralized design clicks fast and makes so much sense, I think because it lines up well with scaling approaches you deal with in everyday backend jobs

And then there’s ActivityPub. When you’re designing a social networking protocol it probably makes sense to involve companies that actually run social networks at scale - but that wasn’t the case.

Love the tech behind bluesky and atproto. The overall decentralized design clicks fast and makes so much sense, I think because it lines up well with scaling approaches you deal with in everyday backend jobs

And the fact that it is currently driven by a single company is great, because from my experience when open protocols/standards start out in consorciums/stardands-orgs - they usually fail to establish a "hard", fully interoperatable standard

illustration of how the green economy works. They don't even plant a tree for every .green domain sold

My brain is resisting to focus on texts that are obviously AI-generated. Even at work, a simple "good job!" expanded to "I’m genuinely enthusiastic about this step, especially because it’s deeply rooted in a results-oriented, revenue-focused mission".... come on man, I'm not reading this shit

It reminds me about soviet poets. Official, state-approved authors were writing in a dictated, "intellectual" language. But some self-published poets with simpler, direct and even aggressive style became more popular and loved.