« back

I'm no longer a front-end developer

Mar 03, 2021

True to my word, as of today I'm no longer a front-end developer. Yesterday marked the last day as one, and also the last day at GPM, where I had spent my last 2 and a half years. The first two years I spent almost entirely writing ClojureScript, which I must say is a joy to write, and the rest writing TypeScript, which to me is like my colleagues know, a poor man's typed language.

Funny story about GPM: I was new in Barcelona and needed a job, so I applied to a few JavaScript positions, one of which was GPM. I had just one call with them after which I received a formal offer. Once arriving in the offices to sign my contract I found out that I will be doing ClojureScript instead, which if you don't know is about as different from JavaScript as a thing could be. I also found out that they had forgotten to send me a test job and that it was a bit late for that. Seems all worked out despite these things, and if Clojure were a bit more popular, I'd probably be looking to do back-end Clojure now.

I have no bad words about the company or the people I've worked with. I was told that if I ever find myself in Barcelona again and would like to work for them again, the door is always open - and while it would certainly have to be back-end for me then - I really wouldn't mind. I've met amazing people there and will not miss a chance to invite them for a drink whenever I find myself in Spain again.

So what's next for me? Well, if you read my post on creating a static site generator in Python, you'd probably guess it was Python. I've done enough of job market, developer happiness, and would-i-like-it research to be able to guess with a pretty high probability that I'd be happy writing Python. But once I looked a bit closer into what types of jobs Python would mostly offer, I found it's either automation or data science. Automation is usually low-pay and data science isn't something I'm interested in, and so Python, for now at least, isn't going to work for me. I'll have to find something else.

I'm sure that the transition to back-end won't be an easy one as there are a lot of tools and technologies I need to catch up with, as well as brush up on my algo's and data structures. Believe it or not in my 10 years as an engineer, never really needed too much of that. That said, I'm determined to become a back-end expert, and par for the course, expert in data structures and algo's as well. After all, I've heard that it's impossible to land a back-end job without knowing how to revert different types of trees. Obviously, you'll need a shovel and possibly a crane of sorts.

I know some of you might cringe reading this and think I must not be so bright, and perhaps you are right, but I managed to learn all of this on my own with no mentors and no formal education, just a bunch of googling and of building a ton of side projects, and I've done well for myself thus far, and that's the only measure of success that matters to me. The way I see the world, it's the only measure of success that should matter to anyone.

Here's to the next 10 years of software development, this time as a back-end developer.