“the serial output from my test unit turns into garbage and it happens at completely random times!”
“Did you make sure they were plugged in all the way?”
“WHAT?!?! ARE YOU SUGGESTING I DON’T KNOW WHAT I’M DOING?!?!”
Some time later
“Yeah, it turned out to be the serial connection was loose.”
It’s a surprisingly good comparison especially when you look at the reactions: frame breaking vs data poisoning.
The problem isn’t progress, the problem is that some of us disagree with the Idea that what’s being touted is actual progress. The things llms are actually good at they’ve being doing for years (language translations) the rest of it is so inexact it can’t be trusted.
I can’t trust any llm generated code because it lies about what it’s doing, so I need to verify everything it generates anyway in which case it’s easier to write it myself. I keep trying it and it looks impressive until it ends up at a way worse version of something I could have already written.
I assume that it’s the same way with everything I’m not an expert in. In which case it’s worse than useless to me, I can’t trust anything it says.
The only thing I can use it for is to tell me things I already know and that basically makes it a toy or a game.
That’s not even getting into the security implications of giving shitty software access to all your sensitive data etc.
They’re they’re, it’ll be all right.
Haha! Jokes on you! It was mostly gnu makefile calls to ruby scripts!!! You’ve just broken the build a million different ways!
Last time somebody did this to me there were a lot of sit downs about how to properly chop up large scale code changes and why we don’t sit on our own branch for two months.
“How long will this take to get in?”
“Well, two weeks for me to initially review it, a week for you to address all the changes, then another week or so for me to re-review it… Then of course we have to merge in all the changes that have been happening in primary…”
We no longer have humor, it’s been beaten out of us by code reviews and merge conflicts.
I caught a junior trying to reimplement an existing feature, poorly, in a way that would have affected every other consumer of the software I’m a code owner on a week or two ago. There’s good reason to keep them around.
PRs suck to do, but having a rotating team of owners helps, and linting + auto formatting helps with a lot of the ticky tacky stuff.
Honestly, the worst part is “newGuy has requested your review on a PR you requested changes on but he hasn’t addressed” that’ll get you in the ignored pile real quick.
DON’T YOU DO IT!
DON’T YOU FUCKING DO IT!
KEIL ALREADY REQUIRES A BLOOD SACRIFICE YOU’RE KILLING US ALL YOU FOOL!
With enough grit and time, yes :D
Edit: ok not mainline, but Linux in some form or another anyway.
You can run a “soft” (semi-hard?) Processor on a Spartan, you could run Linux on that at least.
Also me waiting for the junior dev to address review comments satisfactorily.
I’m moving to a few acres this weekend, assuming everything goes well. We got plans for a giant garden, a duck run, and fruit trees. This meme is all truth.
Being fully remote is a great gig if you can swing it.
Maybe that’s a good thing?
The only caution I’d add about doing it as a hobby too is that it’s super easy to burn yourself out. I think that’s why so many of us get into woodworking and gardening lol
“if you’re the smartest person in the room, you’re in the wrong room”
The short answer is “practice”
The longer answer is, do it a lot. Listen in code reviews. When you investigate bugs, do actual root cause analysis, understand the problem, and understand how it got missed. Don’t stop learning, study your languages, study design patterns, be intentional in what you learn.
I had good mentors that were hard on me in reviews. Developing a thick skin and separating criticism of you from criticism of your code will help a lot in terms of learning in reviews.
Source: 10 years in the field. (Senior SW Eng. Focused on embedded systems and VnV)
“Where does this green wire go?”
I appreciate HW engineers and techs. I’m not afraid of datasheets, circuit diagrams, or a mso and they’re always patient enough to explain things to me so I can make the rocks behave. Or at least tell me how to go from diagram to board lol.