About Me
I build automation systems because most software is needlessly complex garbage.
For one, I started as a mechanical engineer. This means I actually understand how physical systems work - how parts move, how energy flows, how things break. When I look at most software, especially in the data/automation space, I see layers of abstraction built to justify management positions rather than solve real problems.
The core issue isn't technical. Your "data pipeline" exists because you refused to design proper data models. Your "ETL solution" compensates for poor architecture upstream. Your "microservices" are just complexity theater that makes simple problems harder to solve.
(And everyone in the industry knows this, but nobody will say it.)
I'm driven by three things:
I. Nerdiness
I want to understand how things actually work. Not the marketing pitch, not the conference talk version - the raw mechanics. This means diving deep into graphics engines, automation tools, and data systems that produce real output instead of shuffling JIRA tickets between sprints.
II. Ambition
Not the venture-capital-scorecard type. I want to express authentic solutions at the highest possible level. Build things that matter. Eliminate entire categories of problems through good engineering. (You know, the ones your current vendors say need manual oversight.)
III. Friendliness
The best technical solutions come from understanding real human problems. I create supportive spaces where people can share honestly about their technical challenges. This means addressing your own ego first - nobody wants advice from someone more interested in showing off than helping.
My philosophy is simple: Most "maintenance" work exists because we built the wrong things. We've created entire industries around maintaining poorly designed systems, then convinced ourselves this complexity is necessary. It's not. Good engineering eliminates problems. Bad engineering perpetuates them.
I focus on automating what others claim needs constant human oversight. Not because I love automation itself, but because I hate seeing talented people waste their lives maintaining broken systems. We should be building new things, not babysitting old ones.
Remember: The reward isn't what you get, it's who you get to see yourself become. I became @automationchad because someone needed to call out the emperor's new clothes in tech. Might as well be me.