I haven’t tried juggling for decades but I did manage to teach myself basic three-ball juggling when I was at university (any excuse to avoid revising!)
I think it took me a couple of weeks though. I’m a bit malcoordinated for that sort of thing in general. I think you’re right that there’s some sort of natural aptitude that not everybody has. Fortunately basic juggling is just about easy enough that almost any idiot can do it.
It failed testing. What you’re describing is the exact same thinking that destroyed Challenger. The O-rings are leaking, they’re not supposed to do that at all, but they’re not leaking enough to cause a failure....
Have a look at this recent Scrabble video where Claude plays semi reasonably and ChatGPT goes crazy https://youtu.be/8opLB1D_RYY (skip to 6:50 for the insanity)
To get both blinkenlights for registers and tri-state for bus driving, use two ’574 chips in parallel rather than a ’377 behind a ’245. Tie the clock and input lines together on both. Tie the output enable low on the one driving the blinkenlights. This way the chip that the rest of the CPU depends on doesn’t have the extra work of driving any load and you only have one chip’s worth of propagation delays.
You just define the structures in terms of some e.g. uint32_le etc types for which you provide conversion functions to native endianness. On a little endian platform the conversion is a no-op.
Add a comment somewhere in the middle of the code they’re working on saying /* I should always remember to lock my computer */ and amend their current commit. Maybe they’ll spot it, maybe code review will notice, maybe not.
reply