Yuna

You don't need a framework or a tool,
You need a mirror in this dependency-driven development.

Simplicity is the key. But instead, many are choosing a janitor's life.
Gluing dependencies like it's glitter on a kindergarten project.
It’s not that AI struggles with simplicity. It just learned it from you.

Developers today worship frameworks like ancient cults, adding layers, tools, plugins, and just a sprinkle of hope. A microservice? No. It's a monolith in disguise. 10,000 custom lines of over-abstracted ceremony just to say "Hello, World".

We summon demons. And each dependency is a pact we don't read before signing. Scary, we understand more of the framework than of our programming language.

Today, I wrote a chatbot. 100 lines. Pure Java. No feign, no Eureka, no YAML in sight. It compiles to a native executable. It runs. It lives. It doesn't cry at night. It will stay forever. No .sdkmanrc, no dependabot, no excuses, never legacy.

The more tools you add, the more you suffer. Onboarding grows, maintenance creeps, code rots, metadata multiplies… and actual work quietly leaves the room.

Good services run in the background without much maintenance. No bugs, no Incidents and nearly forgotten.

Don't Keep debating the fastest library while the glue makes it slow anyway.
The real costs are humans. Slow, expensive, and prone to burnout.
Not the €200/Month for 20 more bloated zoo of extra instances.

#JavaWithoutCrying
#KillTheGlue
#DependencyHell
#SimplicityFirst
#CodeMinimalism
#MicroserviceMadness
#FrameworkCult
#CeremonialCode
#LegacyProof
#DevRealTalk
#BurnTheYAML
#OnboardingNightmare
#CodeOverConfig
#NoExcusesCode
#AIReflectsUs
#SoftwareSins
#TheRealTechDebt
#LeanCodeWins
#Coding
#programming

Apr 24 at 6:36amWeb
Show threadGuillem CantallopsApr 24
@LunaFreyja Yes. But. Simplicity is key. You must also avoid creating your own frameworks. I've seen code bases where they created the equivalent of Spring Boot, but poorly done and proprietary. More static and tightly coupled. Onboarding is like... after 2 years maybe you'll be able to make a simple change without breaking the whole company. And anyway, senior developers change the color of a button and persistence fails. But hey, they're "pure Java". That's what they choose to highlight 😜
Show threadPiradixApr 24
@LunaFreyja You write all I think ;-)
One of the problem is that :
- lot of developper love complexity, because they think, a hard job to code is a good job (after the scare, the reward ;)
- Tech leaders prefer to use a software stack where there are lots of questions/answers on the web.
They don't consider that the high number of questions corresponds to complexity problems or framwork bugs. For them, it's a matter of having the resources to answer their developer's questions!