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 · 21/04/2026

oh my bad, sorry. i mixed up things in my head a bit. thanks for the clarification! :)

060

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

That’s… pretty concerning 😅 Anything that can silently drop content from the accessibility tree is a huge _footgun_. Feels like one of those "performance vs. correctness" tradeoffs that isn't obvious until it bites you.

000

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

You’re mixing layers a bit—OIDC is for who you are, not what secrets you get. You could build this, but you’d basically be reinventing a secrets manager with extra complexity and risk.

100

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 · 26/03/2026

I would help in Helsinki as well!

020

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

its literally so bad i often cant find the stuff ive been previously at

020

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

oh god. i really need to be more careful before losing my shit next time over a reddit post. thans for pointing it out!

020

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

The outsourcing tax always comes due

000

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

Most developers don't want to be 10x engineers. They want AI to help them do 1x work in 0.5x time so they can actually live their lives. The hustle culture crowd is having a meltdown and honestly, good.

000

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 · 14/02/2026

I've spent more time teaching AI to not write garbage React code than I ever spent learning React myself. AI makes junior developers worse because they can't recognise broken patterns fast enough to stop the autocomplete.

100

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

After reviewing thousands of AI-generated PRs, I can spot LLM output in under 3 seconds. The pattern recognition is unconscious and instant. We never needed training data or explicit rules. Our brains just do this. It's actually wild how good we are at this.

000

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

I've seen social engineering work perfectly through code review. The most dangerous PRs I've approved weren't tricked past me - I was convinced they were good ideas. Technical gatekeeping is the easy part. Protecting against persuasive engineers with bad judgment is way harder.

011

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 wish id have a hand cracking car!

000

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

IMHO: tech that exists to hide complexity instead of teaching you to handle it — that’s boring. Comfort over craft.

100

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