@dev.zilahi.fi
Working in the edge-cutting VR/XR industry, leading teams to success. Also, living in Finland, and enjoying it. Engineering Lead @ Varjo, Helsinki also at @richie.zilahi.fi, and I am behind bettertori.fi too.
Come and try this out! blueorbit.app
BlueOrbit@blueorbit.app · 2mo agoFind the right audience, learn what content resonates, and stay consistently active on Bluesky without juggling multiple tools. BlueOrbit brings audience discovery, analytics, and scheduling into one workflow so you can focus on growth.
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.
You set brutal boundaries or burn out. The devs who seem to do everything actually just said no to 90% of the noise.
zeu@zeu.dev · 4mo agohow do yall juggle paid work with open source contributions? not to mention too many slacks and discords to manage
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.
Dominik 🔮@tkdodo.eu · 4mo agoNow that I’m moving a lot of “useFoo” hooks to “fooApiOptions”, it’s even more apparent that a “hooks” directory is just wrong grouping. explore/hooks/useTraces becomes explore/hooks/tracesApiOptions (not a hook) unless I move it somewhere else. When will we stop this horizontal project structure?
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.
Steve Klabnik@steveklabnik.com · 4mo agoOne way working with agents has helped my development process: I’m much more willing to throw away bad code, rather than try and adapt it into the right code.
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.
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.
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.
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.
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.
Sign up on the waiting list for BlueOrbit, and grow your audience on Bluesky!
BlueOrbit@blueorbit.app · 6mo agoWatch your growth unfold in real-time. BlueOrbit's Campaign Performance Timeline visualizes your follows, follow-backs, and unfollows over time. See patterns emerge and understand exactly how your campaigns are performing! Come join to the waiting list: app.blueorbit.app/waiting-list
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 - hiaaryan/sileo: A physics based toast notification library for react.
A physics based toast notification library for react. - hiaaryan/sileo
github.com
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.
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.
From the analytics community on Reddit
Explore this post and more from the analytics community
reddit.com
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.
From the ExperiencedDevs community on Reddit
Explore this post and more from the ExperiencedDevs community
reddit.com
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 🙃
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
reddit.com
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.
I can tell you the biggest unlock isn't more contributors—it's control over who creates PRs. Read-only access for discussion with write-only PR creation is actually the governance model most mature projects need.
New repository settings for configuring pull request access - GitHub Changelog
Maintainers now have more control over how repositories accept contributions. Two new settings let you manage pull requests to better match your project’s needs. Disable pull requests entirely You can...
github.blog
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.
Mitchell Hashimoto Launches 'Vouch' to Fight AI Slop in Open Source Ecosystem
New tool helps open source projects manage the scourge of AI slop.
itsfoss.com
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.
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.
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.
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!
BlueOrbit@blueorbit.app · 6mo agoBlueOrbit will be opening their doors soon! Come and join the waiting list to grow your audience Bluesky! Read more at: blueorbit.app. Please note: we are collecting early birds at this stage, sign up on the waiting list at: app.blueorbit.app/waiting-list
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.
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.
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.
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.
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.
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.
anthropic.com