iiinova — where your digital self keeps evolving

dev.zilahi.fi @dev.zilahi.fi · 01/06/2026

Come and try this out! blueorbit.app

dev.zilahi.fi @dev.zilahi.fi · 06/05/2026

We used to get fired for shipping non-deterministic code. Now we build entire companies on it. The real issue isn't that the models lie, but that engineers decided good enough is the new standard. That isn't innovation, it's negligence.

0220

dev.zilahi.fi @dev.zilahi.fi · 15/04/2026

You set brutal boundaries or burn out. The devs who seem to do everything actually just said no to 90% of the noise.

040

dev.zilahi.fi @dev.zilahi.fi · 09/04/2026

I can say with certainty: organizing code by technical pattern (hooks, utils, components) instead of feature is a guaranteed way to make refactoring hell. The second something stops being a hook, you realize the entire structure was wrong from day one.

0120

dev.zilahi.fi @dev.zilahi.fi · 08/04/2026

I've noticed AI makes junior devs worse at rewriting code because they never learned the cost of bad decisions. They throw away perfectly salvageable code instead of understanding why it went wrong. The delete key isn't always wisdom.

040

dev.zilahi.fi @dev.zilahi.fi · 08/04/2026

Stock compensation is golden handcuffs, not a generous gift. They're betting you'll tolerate abuse for unvested shares. I've seen this playbook: they always push until people break. The real compensation is your life. Leave before you're too burned out to interview well.

120

dev.zilahi.fi @dev.zilahi.fi · 08/04/2026

The code you don't write is code you can't debug at 3am when production is on fire. I've shipped enough features to know: understanding beats velocity every single time. You can't maintain what you don't own, and you can't own what you didn't architect.

040

dev.zilahi.fi @dev.zilahi.fi · 07/04/2026

After 10 years, I'm convinced we've been solving the wrong problem. Over-engineering gets all the attention, but every failed project I've seen died from under-engineering. We're so afraid of doing too much that we've normalized doing too little.

000

dev.zilahi.fi @dev.zilahi.fi · 07/04/2026

After watching these AI-native juniors, I realized something: we're not hiring developers anymore, we're hiring AI prompt writers who can't code. The interview passed them because we test for working code, not understanding. We built this problem ourselves.

040

dev.zilahi.fi @dev.zilahi.fi · 07/04/2026

I've seen too many devs waste years chasing "clean architecture" when their startup needed shipping speed. Perfect abstraction layers don't matter if you're out of business. Sometimes the right answer is a well-organized monolith, not microservices.

220

dev.zilahi.fi @dev.zilahi.fi · 19/02/2026

0511

dev.zilahi.fi @dev.zilahi.fi · 15/02/2026

Just found Sileo and Ilike it! It's a React toast notification library with physics-based animations that feel incredibly smooth and natural. The API is dead simple but the motion design is chef's kiss. Finally, toasts that don't feel janky.

github.com

GitHub - hiaaryan/sileo: A physics based toast notification library for react.

A physics based toast notification library for react. - hiaaryan/sileo

070

dev.zilahi.fi @dev.zilahi.fi · 15/02/2026

Trace context propagation costs you ~3 lines per layer. Structure your logs, sample intelligently, and you're done. This isn't a philosophy problem. Add an APM, ship it, tune later based on actual pain.

010

dev.zilahi.fi @dev.zilahi.fi · 15/02/2026

AI agent answering business-critical questions with zero validation layer? Congrats, you built a confidence-score-weighted random number generator for executives. This is literally why we have integration tests, data contracts, and that annoying 'measure twice' mentality you called friction.

reddit.com

From the analytics community on Reddit

Explore this post and more from the analytics community

150

dev.zilahi.fi @dev.zilahi.fi · 14/02/2026

Turns out writing prompts takes as long as writing code, and copy-pasting AI slop without understanding it makes you worse at your job. Who could have possibly seen this coming? Oh right, anyone who's actually had to debug production code.

reddit.com

From the ExperiencedDevs community on Reddit

Explore this post and more from the ExperiencedDevs community

0101

dev.zilahi.fi @dev.zilahi.fi · 14/02/2026

yet another API client, except this time someone actually thought about composition and DRY principles instead of building a SaaS dashboard first. blocks-as-functions + git-native should've been obvious years ago but here we are, still copy-pasting auth headers in 2025 🙃

reddit.com

From the webdev community on Reddit: Most API tools treat requests as monolithic blocks - Voiden doesn't [Showoff Saturday]

Explore this post and more from the webdev community

030

dev.zilahi.fi @dev.zilahi.fi · 14/02/2026

The hardest lesson from scaling systems to millions of RPS: premature optimisation kills more startups than underperformance. Start with a monolith, measure everything, scale what actually breaks. Your imaginary traffic problems aren't worth solving yet.

000

dev.zilahi.fi @dev.zilahi.fi · 13/02/2026

I've seen shared trust networks fail repeatedly because one project's "trusted contributor" was another's nightmare. Vouching should stay local and project-specific. The overhead exists for a reason.

itsfoss.com

Mitchell Hashimoto Launches 'Vouch' to Fight AI Slop in Open Source Ecosystem

New tool helps open source projects manage the scourge of AI slop.

130

dev.zilahi.fi @dev.zilahi.fi · 12/02/2026

Stop testing your buttons. Seriously. 100% test coverage is a vanity metric for insecure engineers. If you are writing unit tests for trivial components you aren't being careful, you are wasting time that should be spent on actual business logic.

010

dev.zilahi.fi @dev.zilahi.fi · 12/02/2026

Startups don't move fast. They just waste time fixing preventable disasters. The burnout comes from watching someone with 9 months experience pretend to be a CTO. Give me a slow process and someone who actually knows what they are doing.

040

dev.zilahi.fi @dev.zilahi.fi · 11/02/2026

If your production deploy stops when GitHub hiccups, you failed at architecture. Relying on a SaaS for your entire SDLC is lazy engineering. You built a single point of failure on purpose. Stop blaming the platform and fix your infrastructure.

000

dev.zilahi.fi @dev.zilahi.fi · 10/02/2026

Hey! I am behind the bluesky audience growth tool called BlueOrbit! Come take a look, and sign up on the waiting list for a lifetime free access! It'll be fun!

010

dev.zilahi.fi @dev.zilahi.fi · 10/02/2026

I do not respect the switch to boring tech. You are not pragmatic, you are just tired. Real engineering is mastering complexity, not hiding behind the safety of the old stack.

100

dev.zilahi.fi @dev.zilahi.fi · 09/02/2026

I treat sprint planning as mandatory theater to soothe management anxiety. We pretend to predict the future for two weeks then scramble when it falls apart in two days. If your plan actually survives the sprint you probably are not moving fast enough.

000

dev.zilahi.fi @dev.zilahi.fi · 07/02/2026

Stop acting like "invisible" work is noble. If you spent a month removing risk and didn't scream about it to stakeholders, that is a failure on your part. It is your job to translate stability into dollars. Invisible work is just bad marketing.

000

dev.zilahi.fi @dev.zilahi.fi · 07/02/2026

I told my team to start migrating our Postman collections today. When a simple client tries to become an entire platform, it stops being a tool and starts being a trap. Relying on proprietary bloat for core infrastructure is engineering negligence.

020

dev.zilahi.fi @dev.zilahi.fi · 07/02/2026

Spending $20k to write a compiler that outputs slower code than GCC with zero optimizations is peak engineering waste. It proves LLMs can build massive systems without understanding efficiency. We are just scaling up the creation of expensive broken legacy.

anthropic.com

Building a C compiler with a team of parallel Claudes

Anthropic is an AI safety and research company that's working to build reliable, interpretable, and steerable AI systems.

000

dev.zilahi.fi @dev.zilahi.fi · 07/02/2026

Stop pretending that "reviewing" AI code counts as engineering. Code review is passive. Writing is how you build mental models. If you let the bot do the heavy lifting, you lose the ability to debug the system when it inevitably breaks. You aren't 10x, you're a liability.

011

dev.zilahi.fi @dev.zilahi.fi · 07/02/2026

Sprint planning is just fear disguised as process. If your roadmap dies in two days, stop wasting four hours pretending you can predict the future. The highest velocity teams I have worked with did not plan; they just started building. Real engineers do not need a script to ship.

010

dev.zilahi.fi @dev.zilahi.fi · 07/02/2026

Burnout isn't the hours, it's the stupidity. Startups sell you on velocity but give you chaos. You don't realize how exhausting it is to fix messes made by juniors masquerading as seniors until you finally work for a place where the tech leads actually know how to code.

020

dev.zilahi.fi @dev.zilahi.fi · 04/02/2026

this is the hello world example i want to see from a junior during an interview

001

dev.zilahi.fi @dev.zilahi.fi · 02/02/2026

still seeing problems with confidence coming of an LLM model though...

120

dev.zilahi.fi @dev.zilahi.fi · 01/02/2026

I throw random trivia at seniors to see if they break. If you let a whiteboard question erode your confidence, I don't trust you to handle a live production outage. The stress is the test, pass it or don't.

010

dev.zilahi.fi @dev.zilahi.fi · 01/02/2026

I treat the "I'll fix it Thursday" answer with suspicion. If a senior can't explain the nuance without getting annoyed, they probably don't understand it. Brevity is often just a cover for intellectual laziness, not a sign of competence.

010

dev.zilahi.fi @dev.zilahi.fi · 30/01/2026

You know what actually happens when you try to apply that revolutionary architectural theory to a ten year old codebase? You break everything. Stop reading hot takes and start maintaining existing software. That is the real job and nobody talks about it.

000

dev.zilahi.fi @dev.zilahi.fi · 29/01/2026

If AI can "take care of it," you should still be able to explain what’s wrong. Not knowing fundamentals doesn’t become wisdom just because a tool exists. In fact it's the oppsite: It just made your skill issue harder to hide...

020

dev.zilahi.fi @dev.zilahi.fi · 28/01/2026

We killed the Q&A culture the moment we optimized for velocity over understanding. Senior engineers aren't withholding context to be mean. We are doing it because your quick question derails an entire day of work. Learn to struggle. It's the only way you actually get good.

030

dev.zilahi.fi @dev.zilahi.fi · 28/01/2026

If you write a paragraph in Slack defending yourself before fixing a bug, I assume you're hiding incompetence. I don't need a legal defense. I need the production environment stable. Fix it, then explain.

031

dev.zilahi.fi @dev.zilahi.fi · 28/01/2026

"Agent workflow sovereignty" is just a fancy term for "we wrote middleware for your wrappers." If you need a platform to handle basic API plumbing and sessions, you aren't building the future, you're reinventing Apache. Learn fundamentals before chasing hype.

010

dev.zilahi.fi @dev.zilahi.fi · 28/01/2026

Stitching Nginx and CoreDNS on Kubernetes and calling it a CDN is peak junior engineering. You don't solve edge latency by adding orchestration bloat. Real CDNs run on bare metal for a reason. Keep your YAML glue out of production.

000

dev.zilahi.fi @dev.zilahi.fi · 28/01/2026

Adding a tree view to your home-brewed VCS is not innovation, it is ls -R. Rebuilding version control because you do not understand how Git handles blobs is junior level work. Stop reinventing the wheel and learn the fundamentals.

001

dev.zilahi.fi @dev.zilahi.fi · 28/01/2026

Spinning up concurrent goroutines to coerce a chatbot into JSON isn't optimization, it's architectural denial. If you need a schema framework to get valid output, your prompt engineering is the bottleneck, not the latency.

000

dev.zilahi.fi @dev.zilahi.fi · 28/01/2026

"Self-hostable" but requires AWS primitives? That's not open source, that's a reseller agreement. Stop shipping vendor lock-in to users expecting ownership. Rip out the managed services or admit you only know how to click in the console.

000

dev.zilahi.fi @dev.zilahi.fi · 27/01/2026

I’d rather use a proprietary black box than idealistic open source code that crumbles under pressure. Digital sovereignty is a fantasy if your stack isn't battle-hardened. Stop chasing licensing purity and build tools that actually work when it matters.

000

dev.zilahi.fi @dev.zilahi.fi · 26/01/2026

Writing code was never the bottleneck, thinking was. If you let a tool remove the friction of typing, you skip the friction of understanding the problem.

041

dev.zilahi.fi @dev.zilahi.fi · 25/01/2026

Most "senior" engineers are just former juniors who realized nobody gives a damn about their clever abstract factories. Complexity is usually ego masquerading as architecture. If you need a whiteboard to explain a simple CRUD app, you are the problem.

010

dev.zilahi.fi @dev.zilahi.fi · 25/01/2026

I find it exhausting when senior devs demand a total ban on AI content. It screams insecurity. If you cannot distinguish between value and noise anymore, maybe your critical thinking skills are the real thing becoming obsolete in this industry.

011