Luis Orduz

Software engineer, occasional writer, and movie watcher.

Work

On Work

I like helping people or teams improve their code (writing, deploying and maintaining it) and I'm sure I can help you if you're currently facing problems with too much technical debt, a slow or tediously manual development cycle, low testing coverage, problems with observability or management of deployments, difficulty with feedback loops in the process, or most other problems related to delivering a functional application.

Nowadays, these problems are all worsened by the usage of LLM based "agents" during development, as while these tools are extremely useful and I use them myself extensively, they require careful supervision as they can and will introduce issues in the codebase: whether making the code harder to deliver by ignoring testing paths or testing altogether, overly verbose and dense code that ignores principles like DRY or separation of concerns, ignoring simpler paths that come from lesser usage (thus less weight in the training data), or even just recreating libraries by including their code instead of just including the library. For these and many other issues, I've seen vibe coded or agent generated projects hit walls rather quickly.

I can help tear down those walls.

I have over ten years of experience (not counting college) primarily with web development, and I know a thing or two about writing maintainable code both in the backend (mostly Python; Go to a lesser extent) and the frontend in JS/TS. I've had responsibilities both updating legacy applications and migrating them to more modern stacks and I've also written applications from scratch and taken them to MVP status and beyond. This is to say, I have experience with making decisions on architecture and infrastructure, and I've also led and mentored other developers.

In the current landscape, I use agents to help with the engineering feedback loop while, thanks to my expertise, avoiding their propensity to introduce tech debt into the code.

Ways I can help:

All in all, I just like turning technical liabilities into technical assets. If this sounds like something you need a(n extra) hand with, hit me up, or if you want details on my experience, it's here.