And the discussion on whether or not to pin versions.

Pinned, these packages work together, but don’t automatically pull in security updates.

Don’t pin, things randomly change on each build, best of luck debugging things.

Only the very junior ones who are writing code without understanding why they’ve been asked to write it. Anyone with more than about 18 months experience will be able to start deciding what to actually build, and I haven’t seen LLMs be particularly helpful with that yet.

Exactly. I got a drive by downvote which is a shame. Some people are in a situation where they’re happy to take a risk, and know that if it fails they won’t be destitute, and sometimes you might be paid more to account for the risk. Or less, but you get stock options to account for the risk. They’re all valid options as long as you’re not forced into it.

Someone else wrote some code, and he reviewed it and approved it, and merged it into the codebase.

Not sure why this is downvoted. It’s a lifestyle choice that is a genuine choice. You don’t have to live in SF if it’s not for you.

It’s not what you know, it’s who you know

All seems pretty random, and not very scientific. Why not try 5 layers, or 50, 500? A million nodes? It’s just a bit arbitrary.

I’ve never had it well explained why there are (for example , in this case) two intermediary steps, and 6 blobs in each. That much has been a dark art, at least in the “intro to blah blah” blogposts.

Not necessarily escape. More, experimenting out in the world, then run home and decide that the planet is entirely backwards.

Sounds like a great way to get a chair upside the back of your head.

You say outsourced, but it’s not like (men largely, but probably everyone) were super in touch with our emotions previously.

They literally have a shark jumping joke in one of the episodes

Finally, thanks I’ve been trying to remember the name of this for ages

I’m not sure there is a correct way to do this

Oh good god

I have the opposite issue with helm charts, where true and false are very, very loosely defined.

This is why I ask for the schema at the same time as asking for (even example) data at the start of a project. Don’t tell me you have the data, give me proof there’s a standardized structure, or the length of the project just tripled.

The fix might be 5 mins. Figuring out wtf was wrong in the first place is the time consuming bit. Especially if the report doesn’t contain a repeatable process to trigger the error condition.

Put it in the backlog and we’ll prioritise it in the next sprint planning. Except we’ve already got a good idea of what’s going in to the next sprint, so we’ll probably get to it in a month. Or two. End of the year tops. Bring it up in the quarterly planning if we haven’t finished it yet, and maybe we can squeeze it in before Q2. Unless the win the ACME project in which case all hands will be on that, so actually plan for it to be in production by Xmas. No, the one after that.

Wholesome