A thing that hallucinates uncompilable code but somehow convinces your boss it’s a necessary tool.
A thing that hallucinates uncompilable code but somehow convinces your boss it’s a necessary tool.
Nah it’s just extra protein.
J. D. Vance sounds like a men’s big & tall outlet with weird font on their sign.
This is the hardest thing to un-train with new employees: be honest about your mistakes. I will not get mad about a mistake. Everyone makes them. The best thing to do is call it out so we can move to fix it. If you keep making the same mistake, maybe we have a talk about your process to see if there are any blind spots.
So many people try to hide their mistakes or reframe them as successes and please do not do that. Own it, see if you can learn anything from it, and let everyone know so we can help you fix it.
Ugh.
Yeah. Also, superficially good looking people can still be sketchy weirdos. Vibe, context, and prior relationship are much more important than looks. Of course, some people can’t get their head around this and start blaming literally anything else: their height, their bone structure, a worldwide conspiracy against them. It’s crazy.
Oh good it’s not just me.
Source: how it went the first time
I became a dad late (around middle age) and was telling dad jokes way before that. My theory is it’s less about becoming a father and more about getting older and just wanting to annoy people for my own amusement.
Steps to test: “Idk try some shit”
Trump becoming president and having MUCH worse policies for the Palestinians becomes much greater.
Oh you mean Donald “Let’s try to move our embassy from Tel Aviv to Jerusalem because appearing neutral in the Israel/Palestine mess is hurting my chances of re-election” Trump? That guy? People actually think he’s going to be better for Palestinians? Really?
Yep. This is the way. Also, you’d be surprised how many devs don’t run through their own QA steps before asking other people to verify.
Yuck.
This is pretty coherent for an ambien post. I had a friend that used to hang out on groupchat after he took an ambien and at a certain point he’d just start sending random strings of text, but really emphatically.
“I’m a specialized clerk interested in mathematics” if you don’t wanna get burned.
At some point, they’re gonna have to debug it.
Dang, Nick Hexum aged well.
If you’re trying to pull your weight, and it sounds like you are, the problem is either with the tasks, the codebase, or the teammates:
Potential problems with the tasks:
A ticket needs: clear repro documents (if necessary), screenshots, and clear steps to reproduce. It needs more than “Title: Add X to Y. Description: We need Y in X. Implement it.” unless you’re intimately familiar with the codebase. And even if you are, you still need a paper trail to back up what you’re doing. If you’re not closing tickets, be very chatty in the comments. Share where you are, problems you’re running into, and who you’re waiting on for help. If there’s a consistent theme to the things you’re fighting, keep a list of them and bring them to your manager. Be your own advocate and be very transparent about all the research you’re doing because other people didn’t.
Potential problems with the codebase:
Hey, it works. But it’s not documented, someone decided to be clever instead of elegant, the local story sucks, or it’s optimized to such a degree that you have to refactor just to add a simple option ("lol why would we ever need that data here? It’s inefficient!)
Potential problems with teammates:
Everyone pulls their weight. Everyone communicates in clear, declarative sentences and provides examples if necessary. “I don’t know” is an acceptable answer. Evasiveness, vagueness, specialized jargon, or acronyms point to the dev being insecure about their knowledge in that area. Be very suspicious of the word “should”: “that should work”, “that shouldn’t be hard”, “you should be able to…”
And, as an aside, I’ve seen this happen a lot. A new dev or contractor comes on, blows through tickets, gets good marks, and an existing dev or two get called out for not contributing with the same frequency. One of two things are happening here: the new devs are getting softballs, or they’re creating a lot of subtle tech debt that someone else will have to fix because they don’t have a full picture of the codebase. Eventually, those devs will be where everyone else is, but it’s still frustrating.
Hang in there.
Not the flex he thinks it is.