

I appreciate Typescript for addressing the sins of its predecessor.
I appreciate Typescript for addressing the sins of its predecessor.
And some of those choices are mistakes.
They make nothing. They’re compensated for destroying things, and considering it’s musk, they’re likely given relatively little money in return for their time.
Even if the only thing you do all day is sit on the toilet and yell at the Internet, you’re already a bigger net positive on society.
You’re giving this person a lot of credit. It’s probably all in the same table and this idiot is probably doing something like a for-loop over an integer range (the length of the table) where it pulls the entire table down every iteration of the loop, dumps it to a local file, and then uses plain text search or some really bad regex’s to find the data they’re looking for.
Don’t let the gatekeepers keep you out. This site helps.
It’s more like bash did it one way and everyone who came after decided that was terrible and should be done a different way (for good reason).
Looking right at you -eq and your weird ass syntax
if [[ $x -eq $y ]]
OP is talking about identity theft, not physically losing your card.
“Do leetcode hard on screen share for 12 hours over three months, and then we’ll let you know if there’s any openings anyone here actually wants to hire you for…then the teams will interview you. Oh and if we don’t find a fit within a year of the phone screen you start all over lol”
Google, meta, etc. Fuck them all.
Bonus: If you score really high on the pointless quizzes, then you might get a chance at a remote job, which puts you first on the chopping block for layoffs every quarter!
Extra bonus: There’s an office near you, but we’re only hiring somewhere else right now that had a shitload of layoffs recently due to shitty management that didn’t get fired, so you’ll have to uproot your entire life and place your future in our hands for the privilege.
If you want to roll your own, I’ve had good luck with ASRock Rack motherboards.
A coworker once got an HR talking-to for printing this meme out and leaving it on all the dev’s desks.
I once tanked a production service by assuming it could handle at least as much load as my laptop on residential sub-gigabit Internet could produce.
I was wrong by at least an order of magnitude.
IED’s your IDE.
It took me a year but I broke my team of this habit. The trick was to remind them that the parking lot shouldn’t be scheduled. The whole point is that you continue conversations organically so that it’s more like the beginning of a working session instead of the end of a meeting.
Oh for sure, and some of those are not ok with swapping the interpreter out 🤣
It is, and it’s a valid complaint. Go and Rust have handled it differently than Python or JavaScript, and all of them have their faults and bonuses.
It’s a load bearing S.
https://en.m.wikipedia.org/wiki/PyPy
Their greatest mistake was not naming it Ouroboros.
Managers when a tester does this in a planning meeting, asking for more time to write better teats: 😠
Managers when a staff level engineer does this in a post-fuckup root cause analysis meeting telling everyone what went wrong: 🤤
Managers when the tester points out it wouldn’t have happened if tests for it had gotten written: