Because software lockouts are bullshit.

It’s a meme, but! This is an excellent analogy. A “full stack” dev will definitely make a taco truck app, but maybe that’s all the customer needs.

Same. I went all in on noctua and haven’t looked back. Just needs a a good dusting a few times a year to maintain peak performance.

Do you have an all-in-one liquid cooler on your CPU by any chance? Something like this

I’ve had one of these leak slow enough that after 7ish years the liquid evaporated and my CPU killed itself.

I had another fail the same way but I caught that one before the CPU failed.

M$ recieves: Root on all your boxxen, all your data, and access to your eyes for ad space.

One of them is a contributor. In general the contributors and the C-suits don’t travel in the same circles. What it really means is that in 30 years Bill Gates has never wanted to meet Linus Torvalds enough to make it happen.

Q1: How many boots do you see

👢 👢 👢 👢

a) 5 Boots

b) 5 Boots

c) 5 Boots

d) 5 BootS

Q2: How do the boots taste?

a) delicious

b) delicious

c) delicious

d) delicious

dataclasses do this for you at the class level. They enforce type annotations at instantiation.

https://docs.python.org/3/library/dataclasses.html

Oh I’m well aware. Took me a solid year to appreciate type annotations for what they are and yeah I’m happy using what we have in stdlib now and not messing with mypy tyvm. The problem is that history is lost to newcomers who have very different expectations. Modern IDE’s mostly solve it though, so for all my Java peeps dipping their toes into the snake waters, listen to your ide

Eagles.

Sheep.

Hammer Head Sharks.

All well known hallmarks of South Carolinian life.

Dude, even just a “FY,I, you sure about this?” would be nice. I gladly embrace python’s by-all-means-shotgun-your-leg-off philosophy, but the noobs could use the help.

python:

a: str = 1

I was sync for me, but hell yeah, it’s been a good couple of years.

say it with me: GET OVER IT CORPOS, MEATSPACE IS DEPRECATED.

So fucking true. I’ve was in an interview, 2nd round, where the recruiter joined the call mid coding exercise to explain that a different recruiter had just given the position to someone else without waiting for feedback on anyone else and therefore they had to stop all in process interviews. She was pissed and apologized. The guy giving the interview just gave me this look like “they do this shit all the time” and ended the call.

Tech recruiters really can be this dumb. I’ve been on both ends several times.

I remember hiring for a test dev, writing the description for the recruiter, I included all the things I’d like to see. Python, test automation experience, open source contributions etc (this was for a public facing repo).

I get back a question a day later asking if they need Java or not. That felt really out of place so I walked over and had a conversation. Turns out they were filtering out anyone who had more than requested. Python AND Java experience? No thank you.

On the upside once we ironed that out I ended up hiring two people I’ve been friends with for a decade+. Sometimes the recruiters just need help.

Now the other side of things…I’ve definitely had recruiters screw up and lose very good candidates, but it was always for stupid shit like they forgot to send the offer letter for a week or they accidentally put them in the “no” pile.

Heh, this one time we got a recruiter ping our team out of the blue saying they had a candidate. No one knew what the hell the position was for. Turns out the recruiters had forgot about a bunch of openings we had closed like a year before, they just never took down the postings. We asked him how he found the job, and the candidate said he manual went through the thousands of open positions until he found one that fit him. He hired him after the first round and he turned out to be awesome.

That’s just built in with extra steps.