Weird. I just got done beating Link's Awakening it sounds like they're making a new tiny Zelda game. I'm in the middle of playing Superstar Saga and just watched this. I should go play Earthbound next.
As someone whose employer is strongly pushing them to use AI assistants in coding: no. At best, it's like being tied to a shitty intern that copies code off stack overflow and then blows me up on slack when it magically doesn't work. I still don't understand why everyone is so excited about them. The only tasks they can handle competently are tasks I can easily do on my own (and with a lot less re-typing.)
Sure, they'll grow over the years, but Altman et al are complaining that they're running out of training data. And even with an unlimited body of training data for future models, we'll still end up with something about as intelligent as a kid that's been locked in a windowless room with books their whole life and can either parrot opinions they've read or make shit up and hope you believe it. I'll think we'll get a series of incompetent products with increasing ability to make wrong shit up on the fly until C-suite moves on to the next shiny bullshit.
That's not to say we're not capable of creating a generally-intelligent system on par with or exceeding human intelligence, but I really don't think LLMs will allow for that.
tl;dr: a lot of woo in the tech community that the linux community isn't as on board with
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?
A very long time ago I was on psychedelics at a Phish show. I had a blast at the show, but the venue also had an upcoming Guy Fieri event and I ended up confronted with massive posters that were just Guy Fieri's weird head everywhere. I had a really bad time for a while until I got out of there. Just frosted tips and flames as far as the eye could see. I had welcome to flavortown on loop in my head and in that moment I experienced true cosmic horror at the idea that Guy Fieri existed in our universe and we were powerless to stop it.
This reminds me of the time my group played a kobold campaign. We found a halfling scout and dealt with him. Then we made an improvised catapult and launched his corpse into the middle of his camp. And then we snuck in and wiped the rest of the halfling party while they were trying to figure out what was happening.
One of the guys in our party put skills in cooking and rolled a nat 20 making halfling jerky. A few sessions later a wizard or whatever granted us a wish, and we wished for our supply of nat 20 halfling jerky to never run out.
So now we're rolling around the countryside raising hell and handing out halfling jerky to everyone because it is now the most powerful diplomatic tool in our arsenal. We never told anyone what it was made out of and pretty much any NPC who didn't want to kill us on sight got a piece.
I don't remember what happened to the party. I think our GM gave up in disgust after a while. Good times.
Claudia explained to police that her daughter had a demon because she would ‘wake up and scream’ in the night.
I feel like crying. All kids do this. You address this by having a happy bedtime, keeping the room cool, keeping ambient light out.... There's so many options. My daughter and I talk about the parts of the day she enjoyed right before bed so she's thinking happy thoughts when she falls asleep. And she still wakes up every once in a while. She gets a hug when that happens. Sometimes my wife sings her back to sleep.
‘Arely’s death made him question his gift to heal.’
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:
they're not researched sufficiently
is this doable?
should we we even be doing this?
have we actually thought about how hard this will be, or did someone say "well that should be trivial" a bunch?
there's not enough info on the tickets
inexperienced leads tend to just shit out tickets with zero info and underpoint them
they're not broken down into small enough pieces
are you working "implement X" tickets while everyone else is working a series of "implement X: step N" tickets?
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:
someone preemptively optimized it
it's not documented well
it's spidery bullshit code that someone has deep emotional attachment to
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:
they're not supporting you
they're grabbing easy tasks because you're the "code whisperer"
they didn't know what they were doing either so they're vague when you ask them questions
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.
groucho @ groucho @lemmy.sdf.org Posts 0Comments 129Joined 2 yr. ago
👍