100 karma · joined January 22, 2014
- "micro" level code is adequate. A new feature typically works as expected, and code is well documented. But macro level everything's wacky: no architectural consideration, lots of duplication, dead end paths, dead code. Nobody ever took the time to understand the context surrounding a change and figure out the most appropriate way to integrate it.
- there's no consideration for infrastructure, or how the code is run (my world). Last week we ddos'd ourselves after someone implemented a 1/s poll that runs on every open browser tab, worsened when the frontend's reconnection logic fired 1/s with no exponential backoff.
- zero critical thinking... First thing everyone did during that incident was to ask their LLM of choice why the platform was down. Investigating by hand (and my findings thereof) was dismissed, because surely Claude knows best.
I'm too old for this stuff.
This sounds great, can't wait to check it out. After taking a Permaculture Design Course, I fell in love with the ideal of living a better, more "luxurious" life that has not only a lower impact on the planet, but a positive impact. I'm on my way down that path, but still figuring out how to make it replicable.
Recently tried a demonstration at SF's Exploratorium which involved biting a metal bar, and the result was incredible!
Most bone conduction headphones I find when searching (eg AfterShokz) appear to rest against the bones around the ear, so I'm not sure if they're as effective.
I'm working on something vaguely related, a grid-based synth-controller/sequencer with a bunch of i2c shift registers and laser cut hardware. I've been thinking about building a pressure-sensitive hex-layout keyboard next, you've given me a bunch of ideas and inspiration.
Before deforestation, carbon would be pulled from the atmosphere by trees, turned into plant material, fall to the ground as dead leaves or whole dead trunks and be sequestered into the soil as they broke down and were buried.