![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/913b482d-9012-449f-bc87-b1f4463e7154.jpeg)
They fly now?
They fly now?
Nobody ever pays me in wigs
The anticipation as you figure out a new IRQ and DMA configuration so you could play with your new toy
“I guess I can’t, then.”
“That’s my name! You got it in one! Good job!”
Dedicated to testing, absolutely, but they don’t necessarily require expertise regarding implementation.
Not to mention the fact that the more code there is, the more bugs you have.
It was $5k worth of training, and well worth it, since you still remember the lesson.
Reminds me of an issue while carrier-testing a to-be-released smartphone. The third party hired to do this testing would sideload an app to run the tests, but it would try to do something hinky in the background with logging, leading to an infinite retry loop for opening a nonexistent file, effectively doubling the device’s power consumption.
It draws unfortunate parallels.
I do agree that the proposals to abolish “black” feel a bit misguided though surely well-intentioned; the etymology of “blacklist,” for example, has no relation to race whatsoever. However, there are unfortunate parallels with how “black” and “white” people were and indeed are still treated differently.
It is stupid, and it’s because of a failure to understand the nuance.
I will not inconvenience myself or anyone else by making any changes to existing configurations, which will surely break workflows, but I don’t give a shit what the main branch is called as long as it’s obvious.
There aren’t “slaves” in git, though. The term “master” in that context is that of a master copy.
I’d argue that abolishing the term “slave” isn’t the worst idea, implying that the word “master,” only in context where it’s paired with “slave,” should go as well - but that, of course, requires nuance, which a simple word filter lacks.
No, you can’t say “master,” either.
Programming, not Ruby.
Documentation should be larger than code.
Tests as well.
They should stage a coop.
And only one of those runs has complete logs containing the actual error causing the failure.
Oh Christ, I can’t believe I missed that.
Operating on low sleep and responding before coffee.
I shall flog myself now
That’s unary.