Skip to main content

About Me

Howdy!

My name is Ariel Villanea. I'm a software architect who's been in the industry since 2008; fresh out of high school and never went to college. I was born in Costa Rica but am now residing in Minnesota. I've learned that I definitely prefer the weather here in Minnesota. Some people think I'm crazy for it, but I've come to love the cold more than the soupy humidty of the tropics.

Since joining the industry, I've spent my time doing my best to turn every complex technical challenge I come across into an elegant, long-lasting solution. I've spent most of my career in C#/.NET ecosystems, but I do love learning new technologies and have had plenty of exposure to Java, Oracle, and Python workflows as well. I also spent some time in a leadership role, but I honestly prefer being closer to the code and technology.

Motivations and passions for work.

I've always been way more interested in finding solutions meant to last 7-10+ years rather than implementing systems designed for perpetual upgrade cycles. When I get involved in projects, I always like to look beyond the MVP checklist and find why that checklist exists. Maybe it's cheesy, but I really enjoy delivering solutions for clients that truly make their lives easier or their work more enjoyable as opposed to simply checking off requirements.

I love technology and I love talking with my end users just as much. I've always felt that if I don't know why I'm building something, I shouldn't be wasting mine or anyone elses time until I do. I also get a particularly excited joy when discussing requirements and I'm able to give my users scenarios they didn't consider, allowing us to harden and tighten up the deliverable for long-term use.

Motivations and passions for life.

Outside of work, I am a huge nerd. Gaming, music, anime; basically anything that falls under the 'nerd culture' umbrella probably holds its own place in my heart. And yes, that includes running and playing D&D and other tabletop games. Beyond all that, my biggest passion in life is actually my story telling. Since I was a teenager, I've been a hobbyist writer and love telling people all about my intricate deep lore I've built over the years. If you have nothing else to do and want to hear someone rant about science-fantasy stories for a couple of hours, ask me about my writing.

On the technology side of things, I've also recently gotten very into VR and AI. They're currently unrelated to each other, but they are my two biggest techy nerd interests at the moment; I often find myself having to decide if I want to continue playing with AI or put my headset on; lately, AI has been winning that fight, though.

My current focus.

As mentioned above, I've recently decided to transition away from management roles in my career. It was fun to be a director, and I found the work very engaging, but... every time I get a chance to work with code or new dev tools, I'm reminded how much I love being hands-on with technology. As such, now I'm focused on looking for opportunities that allow me to do what (I think) I do best: Technical Architecture and Solutions Engineering. I'm currently pursuing Solutions Architect and Principal Engineer positions (remote or local in the Minneapolis area), where I can apply my expertise to build problem-solving solutions for users, so if you know of any opportunities that would be good for me, let me know!

That being said, I will say that one of my biggest pride points in my career is that I've often found myself mediating between technical and non-technical teams when they're at odds. I've been lucky in my life to be put into situations where I've been able to flex my ability to cut through departmental tensions, provide honest assessments of technical realities and business constraints, and even facilitate collaborative solutions, avoiding the whole "I'm right, you're wrong" conversation to cut to the "okay, but how do we succeed as a team?" discussion. In my experience, real progress happens when technical teams understand business needs and the reasons behind them while feeling valued for their skills, all while the business teams understand the where's and how's of technical constraints without feeling like they're being gaslit or overwhelmed with esoteric jargon.

Let's talk!

If you want to learn more about my work, check out my professional history for details on projects I've worked on and roles I've played. Otherwise, feel free to connect with me on LinkedIn to discuss how I might be able to help you or answer any questions you may have about me.

Thank you for taking the time to read through all this; I hope you have a wonderful day!