tpetrina

One way of framing this is that people that prefer to solve problems are actually bad at tinkering and writing good code. Hence the existence of terrible codebases written by devs thet “liked to solve problems for the customers”. It is not that clear cut that problem-solvers have that in addition to the tinkering part nor it is guaranteed that tinkerers don’t like to solve problems. Two independent axis!

I use Deezer - thanks to it I discovered new music that I like. With Spotify if you listened to one Beatles song you got only Beatles recommendations. At least the app is stable and serves the basic purpose of playing music.

In EU we now have a time tracking law mandating companies to track and keep track of their employee’s hours. While one can defend it in a good faith, it is not a stretch to see how it enables and empowers the behavior from this article.

AI is actively being used to build dead internet right now. So many human potential and hours will be squandered by replying to basically spam. Sure, cynics will say that those networks are already spam - but at least you are engaging with a human.

The simplest take is that “white people are not diverse”. So by asking for diverse group means non-white. Predominantly because diversity is _within a dominating white culture with a surplus of non-white people_. It is basically labeling and contextual issue, not intentional. Imagine asking for a diverse IT office in Zimbabve - is the adjective “diverse” the same as in San Francisco?

sonder (uncountable) (neologism) The profound feeling of realizing that everyone, including strangers passing in the street, has a life as complex as one's own, which they are constantly living despite one's personal lack of awareness of it. For them, you are the distant car light, a silhouette in a window, a footprint on a beach, a trash next to the sidewalk.

If blog can be fully AI generated, why even pretend it's _someone's_? Why not simply make it an AI blog for people that want their knowledge to come from LLM, rather than from experience of other people?

In the modern era of minifying JS to squeeze out bytes, in certain cases, for smaller, non-commercial sites, it might be better for devs to learn from reading each other's source code.

A somewhat sobering post explaining the background behind all this complexity. It is very easy to rant against complexity on its own, but respecting the background that lead to it - that requires nuance, history and a bit more words.

That said, one of the major problems is that there is no clear explanation for these boundaries in the tooling and code. Yes, you can `npm install lib` and unless it is documented in readme, it won't be obvious will this run in node only or in web too.