Well done Gonzalo Simon ! Good stuff.

Did you have a chance to explore the AMQP protocol? Melvin Koh No single-point-of-failure -> This ruled messaging queue out Why are queues a single point of failure? You can set up automatic retries with a broker like RabbitMQ. Errors are propagated back to caller/client/consumer You can use acknowledgments for this using the brokers as well.

I have a little more than four years of experience, and luckily I have had the chance to work across backend, frontend and DevOps. I would say shipping and designing backend systems is still my forte, very shortly followed by Devops and frontend work. Whilst I want to continue growing wrt my backend skills, my immediate focus is to get my DevOps and backend skills right upto to where my backend skills are. When you have 4+ years of experience, I would expect you to take ownership of individual modules and ship them, so knowing things across the stack is a necessity I would think.

Frameworks exist to make our job easier and build applications easily. There are reasons to pick or not to pick a framework like @gijovarghese has mentioned in his well composed answer. My personal favorite reason to pick any framework would be to keep your state in sync with the UI, I think that's the core problem a framework solves. Pick a use case - let's say you're building a Social media app. Try thinking about your codebase on pen and paper in Vanilla. Now, repeat the same process, but this time, assume that you're using a framework. I for one believe that the later is a lot simpler to maintain. " not worry about keeping up with the latest front-end javascript trends" - You may not want to use the latest framework, but you need to keep yourself updated with the latest trends to write code in the best (and if that best is amongst the latest trends, you need to pick it up) way possible. Take ES6 VS ES5 for instance. Variable hoisting used to be a huge problem until ES6 became the standard. I understand the frustration when people are giving you all sorts of ideas or are marketing their favorite frameworks, but if you do your research today and pick one, you will actually achieve your goal of writing simple and maintainable code. Good luck!

How was it working with some of the best minds at Andreessen Horowitz? Is it true that Andreessen could clock around 180 wpm on the keyboard?

"It's ok, test in production". What the absolute hell!

Hashicorp's Terraform and Consul, PHP, Go, and AWS Lambda

Oh, this has been the story of my life of late. :) You don't necessarily need to know HTML and CSS, to find a job. You can still write backend JS code and business logic on the front-end using JS.

I mostly use the ones others have mentioned, but I am very very surprised to see this command being left out; pretty sure this is the command I use the most. history

You identify the endpoints that have a bottleneck and take the parts that cause the bottleneck out the endpoints and make it a microservice. The endpoints can talk to the microservice using say something like a RabbitMQ queue.