Platypus

In my experience, very, but it’s also not magic. Being able to package an application with its environment and ship it to any machine that can run Docker is great but it doesn’t solve the fact that modern deployment architecture can become extremely complicated, and Docker adds another component that needs configuration and debugging to an already complicated stack.

Eh, depends on the language and the context. I still use 80 for C, but I’ve found 120 to be a much more reasonable number for Java.

I’ve been migrating one of my company’s apps from microservices back to monolithic Java. It’s wonderful. I haven’t touched a line of yaml in weeks.

I read that one, he literally described himself as mediocre programmer and is excited about gpt as a way for mediocre programmers to be competitive again. I’m sure he’s in for a really fun time when he has to find a bug in 12k lines of AI spaghetti he bolted together.

doesn’t understand that this is a useful first step in debugging

reacts with anger when devs don’t magically have an instant fix to a vague bug

Yep, that’s a manager

In my experience refactoring lots and lots of crappy code left by devs long gone, a dev who can write useful comments is by and large a dev who can write code clean and simple enough not to need them. If the code doesn’t have informative names and clear separation of concern, chances are a comment won’t help because the dev didn’t really know what they did that worked in the first place.

I presumed it to be a standin for just directly using Math.max, since there’s no nice way to show that in a valid code snippet

Not using thief is professional incompetence unless you’re doing something deeply cursed

Fair enough, though I contend that for a common-case application like a database-backed REST API where the architecture is basically standardized there is no meaningful time difference between writing crappy code in a clean architecture and writing a crappy pile of spaghetti.

I’ve been tasked with updating some code a senior programmer (15+ years experience, internally awarded, widely considered fantastic) who recently left the company wrote.

It’s supposed to be a REST service. None of the API endpoints obey restful principles, the controller layer houses all of the business logic, and repositories are all labeled as services–and that’s before we even get into the code itself. Genuinely astounding what passes for senior-level programming expertise.

That’s what’s really irks me be about JS–you can do just about whatever but you’re not supposed to.

It’s an imperative language, but best practices are to use it functionally.

You can omit semicolons, but best practices are to use them.

You can use sloppy equality, but best practices are to always use strict.

Same–I think maybe the point is just that the angle is precisely correct to line the windows up perfectly

It’s admittedly quite good at what it was originally supposed to be: a voice chat service for playing games that’s easy to join, use, and share. The troubles began when they started trying to pivot to be a general-purpose public internet space provider, because the platform was never supposed to be that and they’ve done absolutely nothing to support it.

Only the ones who don’t grow up to be total code monkeys

Smex ftw