DEV Community

Cover image for Welcome to TechRay.dev: Why I'm Writing About AI, Agents, and the Future of Building Software
Raymond for TechRay.dev

Posted on Originally published at techray.dev

Welcome to TechRay.dev: Why I'm Writing About AI, Agents, and the Future of Building Software

Hi, I'm Raymond Busuttil, and this is the first post on my new corner of the internet.

I've wanted a place like this for a while. Tech moves fast, and the last couple of years have felt like a decade of change compressed into a few seasons. I spend a lot of time reading, tinkering, and building with the latest tools, and I kept catching myself explaining the same things to friends and colleagues over and over. A personal site felt like the obvious next step: a place to think out loud, share what I learn, and hopefully save you some time along the way.

What TechRay.dev is about

Three things will show up here more than anything else:

Trending tech. I'll cover the tools, platforms, and shifts that are worth paying attention to, and I'll be upfront about the ones I think are overhyped.

AI, practically speaking. Not the breathless "everything is about to change" version, and not the dismissive "it's just autocomplete" version either. I want to look at what these systems are genuinely good at, where they fall over, and how to use them well in real work.

Agentic coding. This is the one I'm most excited about. We've moved from AI that suggests the next line of code to AI that can plan a task, read a codebase, run commands, fix its own errors, and hand back a working result. That changes how software gets built, and it changes what it means to be a developer.

Opinion, with receipts

Expect two flavors of content on this blog.

The first is opinion pieces. I have views, sometimes strong ones, and I'll share them. But I'll try to hold them loosely. If I change my mind about something, I'll say so, because in a field that reshapes itself every few months, the people who never update their opinions are the ones who get left behind.

The second is helpful, hands-on articles: how-tos, workflows, lessons learned, and the occasional "here's the mistake I made so you don't have to." If a post doesn't leave you with something you can use or think about, I haven't done my job.

A quick take on agentic coding

Since it's going to be a recurring theme, here's where my head is at right now.

The biggest shift isn't that AI can write code. It's that AI can now work on code. There's a real difference. Autocomplete helps you type faster. An agent can take a goal like "add pagination to this endpoint and update the tests," explore your project, make changes across several files, run the test suite, notice something broke, and try again.

That's powerful, and it's also where people get into trouble. A few things I've come to believe:

  • Your judgment matters more, not less. When code is cheap to generate, the scarce skill becomes knowing what to build, spotting what's subtly wrong, and deciding what "good" looks like.
  • Review is the new bottleneck. Agents can produce changes faster than a human can carefully read them. Learning to review efficiently, and to structure work so it's reviewable, is a real skill.
  • Clear instructions beat clever prompts. The people getting the best results aren't using magic phrases. They're giving agents clear context, tight scope, and a way to verify their own work, like tests or a build step.
  • Small, verifiable steps win. Asking an agent to rebuild your whole app in one go is a gamble. Asking it to do one well-defined piece and confirming it works is how you make steady progress.
  • Fundamentals still pay off. Understanding how systems work, how to debug, and how to read code makes you a far better collaborator with an AI than someone who's just accepting whatever comes back.

I don't think agents replace developers. I do think developers who learn to work with them will have a serious edge, and I want to help make that transition less intimidating.

The healthy skepticism clause

I'm optimistic about this technology, but optimism isn't the same as cheerleading. AI tools make mistakes, sometimes confidently. They can introduce security problems, invent APIs that don't exist, and produce code that looks right but isn't. Hype cycles also tend to skip over the boring stuff: cost, reliability, maintenance, and the impact on people's jobs and careers.

I'll try to cover the full picture here, the exciting parts and the uncomfortable ones. If something is impressive, I'll say so. If it's a shiny distraction, I'll say that too.

What's coming next

To give you a taste of what's ahead, here are some topics I'm planning to dig into:

  • How I set up my workflow for building with AI coding agents
  • Common mistakes people make when delegating work to an agent (and how to avoid them)
  • What to look for when choosing between AI tools and models
  • How to keep your own skills sharp while leaning on AI
  • Honest reviews of new tools and releases as they land

If there's something specific you'd like me to cover, I'd genuinely love to hear it. This site will be better if it's shaped by the people reading it.

Thanks for being here

Whether you're a seasoned engineer, a curious beginner, or just someone trying to make sense of where technology is heading, I'm glad you stopped by. I'm figuring this out as I go, and I'd like to do it in public, with you along for the ride.

Grab a coffee, look around, and check back soon. There's a lot to explore.

Until next time,
Raymond Busuttil
TechRay.dev

Top comments (0)