We already have contracts in place to get security patches. That’s usually the InfoSec team’s problem anyway.

As a developer, my life gets hard due to library support. We manage internal forks of multiple open source projects just to make them python 2 compatible. A non-trivial amount of time is wasted on this, and we don’t even have it available for public use. 🤷‍♂️

My company makes it super easy for me - we’re just going to continue on python 2.7 and add this to the long list of reasons why we’re not upgrading.

Please send help.

“it actually depends”

Yes, it depends. But in this scenario we’re not discussing if statements with one or two conditions. We’re exclusively discussing multiple complicated conditions. :)

I’ve had at least one code reviewer ask me to put all the logic in the if ... line rather than use a variable or two in order to “simplify code by reducing the number of variables.”

At the very least, this article helped me confirm my own bias of “that guy is a moron” and I can send this article to him the next time he reviews my code.

Yup, that’s indeed the format used in some European countries. Canada was surprising though. 🤷‍♂️

I live in Canada and I’ve never seen “1.000,00”. Canada (at least the anglophone part that I live in) follows the usual “1,000.00” format. Why is this library using commas as decimal separators?

In a former workplace, we had a process that was close enough to what’s recommended in the blog, and it worked well. Really well even, there were hardly any ego clashes, everyone would negotiate a consensus and we had “spike” tasks in our sprints so that we can take the time to think about and research complex problems.

And then the fire nation attacked…

A director left the firm and they hired someone from Amazon. He said that we should have a “bias for action”, and got rid of this process, and a lot of other stuff we had going for ourselves using other such catch phrases.

Getting him as a director was probably the worst thing to happen as we were under pressure to deliver stuff quickly all the time, and we’d then have to rework most of the shit because of missed requirements, or tools used not being insufficient for the task at hand etc. He was okay with it though, because “we delivered (shit) quickly”, and “our efficiency went up as indicated by the team velocity charts”.

Pretty much the entire team had left the company in ~1.5 years, and customer satisfaction metrics were in the gutter when I left.

I don’t know if he misunderstood “bias for action” and implemented it badly or if that’s genuinely how people at Amazon operate, but I won’t even think of joining AWS. Fuck that noise.

I’m a “full stack” backend dev - I mainly do backend work, but make minor changes to the frontend, like adding a button to a page that already has 3 other buttons.

I’ve got a couple of friends who didn’t want to do even the occasional front end work and moved to devops. They’d rather deal with k8s and monthly on-call rotations than deal with frontend.

I don’t know who gave you the impression that all backend devs think of front end as “easy”, but it’s definitely not the case, at least in my friend group of n=4. We treat frontend as insane arcane magic and we don’t want anything to do with frontend because we find literally everything else easier.

I used to work on some insurance software that went haywire in 2018 when a 20 year policy was created. That wasn’t a fun month for us.

Also, wtf, 2018 was 6 years ago!?

What did namecheap do? I’ve got a bunch of domains with them. 🤦‍♂️

Sub to a bunch of hobby communities and browse only those rather than the “all” content if you want to get rid of the doom. You’re gonna have lesser content to consume, for sure, but that’s just a bonus in my book.