avatar Back to home Volver al principio

Lamentablemente, todavía no hice una versión de esta página en español, perdón!

Not a resume

As the title oh so very subtly implies, this isn’t exactly a resume.

It is, however, a summary of my professional life: people and companies sometimes want to know and my aim for this document is to have a nice, centralized place I can direct them to whenever a resume, cover letter, or any other such thing is asked of me.

No way I’m using LinkedIn.

Overview

If you’ve worked in the tech sector you’ll know as well as I do that getting anything done usually requires a very diverse set of skills, and if you know the startup scene you’ll be aware that rarely do companies hire all the actual people they need.

During the course of my career I have mostly been hired and worked as a backend software developer by US-based startups, my desire to get a project forward has often meant wearing many different hats: I’ve organised teams, done frontend and devops work, tech sales, business development and project roadmapping, even some social media. I’ve been lucky to avoid toilet cleaning duty so far.

I’d like to think this has given me a decent amount of perspective as a software developer, being a part of almost every stage of delivering a product means you get to experience first hand what works and what doesn’t, what can come back to haunt you, and what just isn’t worth it. I’ve had an interesting journey.

Working Experience

After an initial stint of non-tech positions (what I refer to in my mind as “normal people jobs”) I started working at a local software company called Netgate in 2010, coding for a voice over IP solution.

I later moved on to work at a Ruby consultancy shop called Cubox (and later for Neo, after we were acquired by them) that focused on bay-area startups. Later still I worked with a number of startups directly and even set up and ran a developer/designer collective called 13Floor for a couple of years.

Now for some name dropping:

I helped build Marqeta, a technology company focusing on payment processing that went on to power the Facebook Card, I am always happy to see them doing well.

I worked at CloudApp helping millions of users share their files with the best possible experience, that was fun.

I took over as lead developer for Chefs Feed in the middle of a complete platform rewrite, we pulled through! Their amazing-looking site is still very much humming along, better than ever.

Finally, I worked on stuff for heavy-hitters like AT&T and Apple, but their army of ninja lawyers will mummify my body using the NDAs I signed if I tell you anything else about that.

Tech Stack

While I started with Python I’ve done extensive work with Ruby for a number of years, a decent portion of that have been Rails applications although these days I don’t see myself using a rails-style framework for any use case if I have a choice: I prefer simpler toolkits.

I’ve worked quite a bit with Go, Lua, Shell and others, I also speak JavaScript, although I dream to see a world where it is deprecated. I fiddle around with other languages all the time for the sake of learning, the latest of these pushes is with the OCaml language (please pay me to write OCaml).

Maybe doing this as a list was a mistake, I’ve used an extensive list of technologies in production: the major SQL databases and the nicest NoSQL ones (#TeamRedis wohoo!), provisioning/orchestration tools, source control, JavaScript frontend React based toolkits. I can’t for the life of me make a coherent list of them all, whenever something is needed I sit down and learn it.

Open Source

I love open source, few things give me greater pleasure than publishing something and have other people use it and contribute to it, the shared experience of building something in a community just because it’s cool and have that be useful to people.

Nothing beats reading code though, that’s where all the talk stops and yields to reality: you can see my code in my github page, or read a bit more about some of my projects in my blog’s Open Source section.

Technical Talks

A couple of years back one of my places of employment offered to cover the plane ticket expenses whenever we got accepted to speak at any given conference, I jumped at the opportunity and started sending out as many proposals as I could, it became kind of addictive for a while.

Presenting a talk (particularly a technical one) can be every bit as rewarding as publishing open source code, with a very different interpersonal experience typical to conferences, and mixed with an almost unhealthy amount of adrenaline from taking the stage.

I recommend giving it a try: preparing and executing talks has made me learn as much about technical stuff as about myself, as well as given me some of my best ever memories. If you’re curious head over to my talks page for some videos and slides.

Contact

If you’re still reading there is every chance you might want to get in touch and discuss work stuff, here’s my email:

[email protected]

If for some reason you’re reading this in PDF or (gasp) a printout please, please go to my site and read the actual thing on the web, I will attempt to calibrate my time machine to rescue you from the eighties.

pote.io/ncv

Seriously, you don’t even have to type it: scan this QR and you’ll be there.

Thanks for staying this long!