To be honest, I have no idea what kind of user the Gemini app was built for. It's just too frustrating to use
2,935 karma · joined March 8, 2026
No promises on code quality, of course. Cheap things are cheap for a reason, right?
It's not work-related — feel free to reach out just because you want to get closer
The performance gap between free and paid AI models is massive. The resulting divide between children from low-income and high-income families is quite evident based on my observations in my country. It will only get harder to keep up.
I don't support UBI either. The fact that UBI is even being discussed means the market is broken. The problem is that in the current market, prices for freelance work tied to intellectual labor have been absolutely crushed by AI. Looking at indicators from Booth or the Korean freelance market, "middle-tier" jobs are disappearing. While currently established professionals remain unaffected for now, the volume of work has drastically decreased for developers or writers who are still building their reputations. There are statistics from Japan showing this as well. My workload has also decreased to a ridiculous extent. The so-called barbell structure is becoming entrenched.
The core issue is this: if that happens, how will society handle the dissatisfaction of such a massive number of people? If more than half the population are workers, there is no problem, but if more than half are unemployed, that is a serious issue. Income polarization is continuing to accelerate.
Because there are no aristocrats without slaves, capitalists need workers to elevate themselves. Wealth and power are strictly relative, and they need miserable ornaments to make themselves feel like "awe-inspiring beings." To confirm their own sense of superiority, capitalists require human spectators who look up to them while suffering in misery. Why else did ancient Rome unleash lions and gladiators in the Colosseum?
Later on, things made by humans will become expensive luxuries, while commoners like me will be fed UBI—the bare minimum bread for survival—along with cheap, AIslop.
If making money by learning a skill increasingly requires a longer time investment, you have to endure the period it takes to learn that skill and build a reputation, which is incredibly difficult for the average working class. It requires the financial backing of a wealthy family to afford a college degree, travel to academic conferences, and survive on low wages. And if someone can endure all that to build a reputation, it will naturally lead to a massive concentration of wealth at the very top.
From a cost-benefit perspective, I think it's a terrible idea. In the case of a massacre, long-term instability makes it hard to build a supportive faction. But if you provide just the bare minimum to survive through UBI, the capitalists will gain a loyal faction that will act as their Red Guards to attack dissidents, which I think is much cheaper in the long run. There are already plenty of people who blindly defend corporations even when they do terrible things, right? In my opinion, UBI is simply the cheaper option. Historically speaking, post-massacre recovery has always ended up costing much more.
As automation takes over, the value of labor collapses, and workers' market bargaining power under capitalism is the first to crumble. Ultimately, this drives up the value of real assets. I agree that tech companies can profit and gain the upper hand in negotiations simply by demonstrating a machine before licensing it, as this alone diminishes the value of workers. I am seriously worried these days.
Out of curiosity as to why 3M would insert this commonality into me to help us share a sense of solidarity, I looked up some safety-related research papers. I came across a 3M technical paper by Seacat et al. (2002)[1], which claims that under their experimental conditions, no harmful effects were observed up to a certain dose.
Seeing this perfectly illustrates just how much science and technology are dictated by the institutions they are affiliated with.
The problem is that I am the one who has to maintain that code. The reality is that code ultimately follows the prevailing trends and paradigms of its era. Most developers tend to stop growing around their 5th to 7th year (this is purely my observation). They settle into the complacency of having shipped a single complete program, an experience they usually hit around their 4th year. As a result, when you do actual maintenance work, you end up facing things like C++98 code or .NET codebases where the dependency graph is a complete disaster.
Compounding the issue is that these types of companies have very little technical exchange with the outside world. And that specific way of writing code ends up acting as a sort of gatekeeping mechanism.
Sometimes, I feel like programming ultimately boils down to how well you can read and adapt to these shifts in paradigms. The coding trends of today will likely become the outdated legacy of tomorrow, and someone might eventually tell me, "You write old code." It is always a difficult problem.
This tendency is especially strong in code-behind frameworks. Because the domain logic directly relies on the state of UI controls, the business logic becomes entirely entangled with the view itself. And what is the result? Every single architectural layer ends up stuffed inside a specific event handler.
I could understand if this came from a small outsourcing shop, but what baffled me was that this was the codebase of the top company in the world in that specific domain.
And to top it off, you sometimes have to integrate with an SDK where the methods are literally named function1, function2, and so on. It is always a thrilling experience.
Code that completely disregards collaboration, utilizing outdated algorithms in the name of "optimization" and making it utterly unmaintainable for anyone else.
We learn about ADTs, Result-first approaches, Composition Roots, and code hygiene, yet at some point, code that simply "works" becomes what ships to production.
Communities advocate for building "good software," but the reality in the field is that most of it is "code written just to clock out for the day." I hear "it works, so don't touch it" in dozens of different variations.
The quality of an open-source project contrasts sharply with that of delivered enterprise software. People settle for the "if it works, it's fine" mindset because in open source, the code itself represents personal reputation, whereas in contract deliveries, meeting the deadline is ultimately the core objective...
It feels like the world is always polarized.
Can we truly define intelligence as prediction, prediction as compression, and compression as the process of finding the upper bound of Kolmogorov complexity?
Can the statistical compression of data really explain everything? I don't know. What exactly is intelligence? Honestly, in everyday life, I rarely think about what intelligence actually is. I usually just focus on what the task at hand is and how to get it done, which makes this a fascinating question.
When you code with AI, you realize there is something fundamentally different from humans. The qualities that make a good senior programmer and the qualities that make a programmer good at orchestrating AI agents are similar, yet there is a subtly different feel to them. I might not be able to fully articulate it, but...
What exactly is the fundamental difference that creates this subtle distinction?
1.Corporations that sponsor scholars dislike it.
2.Politicians dislike it (because if TRU were adopted as the standard, the unemployment rate a critical metric for evaluating their political achievements—would drastically increase).
3.The current system fundamentally operates on legacy metrics, despite the widespread knowledge that they fail to accurately reflect reality.
It seems to me that TRU captures reality much better, so I am wondering why it is not widely used as the standard.