Did you pull it before checkout?

Ah, sorry.

Don’t forget rustaceans for rust!

I’ve worked in two open offices and, yeah, I largely hated it. One was just to enable micromanagement and prevent you from taking any breaks. The other was the opposite, in a very small company, having far too many distractions from music to complete nonsense conversations.

I’ve now moved to a fully remote role and we get far more done. No distractions and a tidy environment (my home) to think. The “random interactions” occur in group chats and the odd meet-up. Mixing the right people is sufficient and the setting is largely irrelevant.

Yeah, this is one of those things which sounds great on paper but also introduces problems. I’ve seen people get really annoyed when exception messages are translated because it makes them harder to search for online. That would need to be solved too.

I’ve had huge issues collaborating on a spreadsheet with a Spanish client. It tries to open the sheet in your locale and then can’t find the functions. Insane that Microsoft didn’t even add some metadata to allow me to work on it in Spanish.

Bottom left is when I make a kubernetes cluster to serve up a mock weather API for practice.

Exactly. I used PHP for years, I haven’t “not used it.” It was the first programming language I seriously learned. Writing good code was tedious if not impossible and that became even more obvious as I expanded to C#, Java, Python and C++; none of which tolerated any of the bad and unconventional practices I’d inevitably picked up. Keep in mind, I was actively trying to avoid bad practices and pay close attention to types but still got kicked to the curb hard when I tried other languages. I haven’t had that since.

I appreciate it’s changed since, I’m happy to see it’s not the same dumpster fire it once was, I also don’t care. I don’t actively trash it, I just think there’s usually a better option.

Ruby on rails is alive, just not as popular. ASP.NET is popular but looks nothing like it did then; probably for the best.

Yeah, plus PHP was very popular circa 2011-2016 and laravel was loved by many around that time and beyond. It’s always been a useful language.

Yep, it’s usually an existing idea with progression in a few areas. You could definitely achieve serverless with a cluster of servers hosting the same scripts in cgi-bin and I think that context helps to put it into perspective.

I think it’s a maturity thing. You eventually see so many trends come and go, peaks and troughs of hype cycles and some developers (probably including yourself at least once!) overusing certain new tech.

You eventually discover what works with current tech and then you can become healthily critical of anything new. You see it more for where it can fit and where it can’t.

If you have something small and stateless then serverless is easy and, more importantly, scalable. It was a little easier to see its role once the hype fog had lifted and I had a problem to solve with it.