Hello World (Again): Why I'm Writing After 8 Years

Eight years ago, I published my last blog post — a basic tutorial on a since-defunct website that, like many well-intentioned developer blogs, quietly faded into the background as life got busy. Since then, I've gone from leading application teams at a startup to driving technology strategy at MOTIX Connected within Aioi Nissay Dowa Europe, part of the Toyota group. I've built large-scale data pipelines that process millions of IoT events from vehicles on the road, championed functional programming in enterprise settings, and witnessed AI evolve from a buzzword into a genuine force multiplier for software teams.

So why start writing now?

The Inflexion Point

We're at a fascinating moment in software engineering. The tools we use to build software are evolving faster than the software itself. AI-assisted development isn't coming—it's here. However, the conversation around it often overlooks the nuances that matter: how do we effectively integrate these tools into our workflows? What architectural decisions make sense when your team can ship 10x faster? How do we maintain quality and sustainability when velocity increases?

These are the questions I'm wrestling with daily, and I've learned that the best way to refine thinking is to write it down and share it.

What I Bring to the Table

My journey has been unconventional. I started as a freelance web developer, the kind who'd take any project to pay the bills. Over the past decade, I've worked my way through senior engineering roles, led application and mobile teams at a startup during its acquisition, and now serve as Principal Technologist — a role that sits at the intersection of hands-on architecture and technology strategy.

My focus areas have crystallised over time:

AI-First Development: I'm not just interested in building AI features; I'm obsessed with how AI tooling fundamentally changes how we build everything. Developer velocity, code quality, and onboarding, AI is reshaping the entire software development landscape.

Cloud-Native Architecture on AWS: I've spent years building production systems on AWS, from serverless applications to complex data pipelines that process telematics data from Toyota and Lexus vehicles in real-time. There's a massive gap between "using AWS" and building truly cloud-native systems that leverage its full potential.

Functional Programming in TypeScript: I'm an active member of the Effect-ts community, and our entire engineering team builds on a TypeScript + Effect stack. Functional programming isn't academic theory—it's the most practical approach I've found for building maintainable, composable, enterprise-grade applications.

Mobile-First Experiences: Although I've worked with various mobile technologies, I have a soft spot for Swift and SwiftUI. There's something deeply satisfying about building native experiences that feel like they belong on the platform.

What You Can Expect Here

This blog won't be another "10 JavaScript tips" or "React vs Vue" comparison site. I want to explore the deeper questions:

• How do we architect systems when AI can generate most of our boilerplate?
• What does functional programming look like in real-world, production TypeScript applications?
• How do we build data products on top of massive IoT streams?
• What engineering practices actually scale as teams and systems grow?

I'll share real experiences—the wins, the failures, and the lessons learned from leading teams building production systems that matter. Expect technical depth, but also honesty about trade-offs and the context in which they occur.

Let's Build in Public

After eight years of silence, I'm committing to writing regularly. Not because I have all the answers, but because the process of articulating ideas publicly makes them better. I'm here to share what I'm learning, challenge assumptions (including my own), and connect with others navigating similar challenges.

If you're interested in functional programming, cloud-native architecture, AI-assisted development, or want to follow along as I explore these topics, I'd love to have you here.

Let's see where this goes.

— Krisztian