DJBunnies

7 ms·

61.
by DJBunnies 1y ago
Did you audit the code?
62.
by DJBunnies 1y ago
Ever seen somebody type on a keyboard that learned on a typewriter?
63.
by DJBunnies 1y ago
Flip side: What if somebody needed to identify one? “Is this thing dangerous?” > Nope.
64.
by DJBunnies 1y ago
I feel like well defined RFCs and standards are easily coded against, and I question the investment/value/time tradeoff here. These things happily regurgitate training data, but seriously struggle when they don’t have a pool of p
65.
by DJBunnies 1y ago
Samurai Jack too, we like good colors and style and writing.
66.
by DJBunnies 2y ago
Luddite. We need a cash/credit alternative, and it’s currently our best shot.
67.
by DJBunnies 2y ago
That’s not irony tho.
68.
by DJBunnies 2y ago
If only we had checksums or file hash integrity.
69.
by DJBunnies 2y ago
You obviously have not worked a lot, this term is everywhere from my experience, ubiquitous even. Terms like this one, “alignment”, “low hanging fruit”, all not super accurate but established industry terms.
70.
by DJBunnies 2y ago
You could have done all that for your peers instead.
71.
by DJBunnies 2y ago
The whole JavaScript ecosystem is a mess.
72.
by DJBunnies 2y ago
Eth is governed by those with the biggest stacks, so it’s not really something to be taken seriously.
73.
by DJBunnies 2y ago
If only we had a mechanism for demonstrating correct and incorrect ways to use a particular software. We could expect failure conditions or assert correct outcomes. It could become a little library of examples that change over time, as the
74.
by DJBunnies 2y ago
Because people are dumb and don’t want a book that you have to recharge every day.
75.
by DJBunnies 2y ago
I think a better question here is: why is game code so exploitable? A: laziness and cost. It just doesn’t matter the same way that baking code matters, I guess. So they toss on some cheap anti cheat instead of architecting it safely (expens
76.
by DJBunnies 2y ago
Yea but TSMC produces good stuff.
77.
by DJBunnies 2y ago
Yeah why did he rebase unreleased code? And the “right” RC only has to be right enough to solve the issue.
78.
by DJBunnies 2y ago
I think we’ve worked for the same org
79.
by DJBunnies 2y ago
I’m skeptical it has basis in medicine, but I’m here to see too.
80.
by DJBunnies 2y ago
Yea but it’s coupled with an incredibly leaky distribution system. It would be so great to regulate fixing that instead of getting rid of it entirely.
81.
by DJBunnies 2y ago
Ok I’ll bite, higher hashrate (bitcoin) means it’s more secure from attacks. So it’s not being burned, it has a purpose here.
82.
by DJBunnies 2y ago
I mean sure, you can take the “high road” and belittle its users and how they have a different area of focus than yours, but the reality is that skipping linkedin will 100% make you miss engineering opportunities. But you still get to scoff
83.
by DJBunnies 2y ago
Yeah it was a kaizen ticket the group filed after the last sprint.
84.
by DJBunnies 2y ago
Uhhh, physics?
85.
by DJBunnies 2y ago
Not exactly universal as such.
86.
by DJBunnies 2y ago
Wild world you must live in.
87.
by DJBunnies 2y ago
Not at all, it’s just unfunny.
88.
by DJBunnies 3y ago
The tolerance must be a nightmare
89.
by DJBunnies 3y ago
Post your specs you dinosaur
90.
by DJBunnies 3y ago
It’s just a single stack trace of dependencies highlighting a bad verb. Not great but nothing to get in a twist over.

More ›