I started writing code in 2012.
Most of my knowledge has come from being thrust into situations where I lacked the necessary qualifications and having to figure things out on my own. The rest has been generously shared with me by people who are willing to teach. This website is, in part, an attempt to repay that favor.
Where I've worked
I spent several years at Spud Software in Michigan as a software developer, working primarily in the C# / .NET stack. My role was to create applications to the client's needs, or work on existing, legacy, apps. One day you're working on a workflow management system, another day you're building dashboard visualizations. It was fun, and you learn a lot in that environment.
After that I joined Leasecake as the first engineer. I spent four years as the Principal Software Engineer and two years as the Director of Engineering. I built the original product end-to-end alongside the founders, and then I grew and managed the team as the company expanded. It was another challenge that I truly embraced and grew from.
Since August 2024 I've been at SendJim, first as Principal and now as VP of Engineering. I'm grateful to be working with a team of people who are passionate about what they do, and I'm excited to continue building features that help small businesses grow.
What I'm actually good at
First, when I’m given a task, I become fixated on finding a solution, even if the problem is unclear or challenging. I tend to simply figure it out.
Second, I understand legacy codebases and work within the existing framework. While I enjoy working on new projects, I recognize that older projects generate revenue, so I do my best to make the most of what we have.
Third, I have a passion for teaching and explaining complex topics in simple terms. I believe that documentation is crucial for a company’s growth, so I take it as seriously as I do the engineering work itself.
What I'm interested in right now
Practical applications of LLMs as tools for engineers, not replacements for them. I built Sunny Bots because I wanted the leverage of Claude Code without losing the structure of my own workflow. I think there's a lot of room for tooling in this space that respects the user's intelligence.
I'm also interested in teaching — through writing, through internal documentation, through the long-form explainers that take a week to write and save the reader an afternoon. If you're working on something in that space I'd love to talk.
How to reach me
Email is best: marco@sunnyorlando.dev, but you can also reach me via LinkedIn.