It's a paraphrasing of the popular 2024 Joanna Maciejewska quote: "I want AI to do my laundry and dishes so that I can do art and writing, not for AI to do my art and writing so that I can do my laundry and dishes."
Sometimes it's fun to mod something that other people can also easily buy and follow your mod recipe. It's more of a network effect than publishing Gerbers and a BOM.
For example, there are (or maybe were) lots of cheap LED controllers that use proprietary phone apps, but if you crack them open, you find that they're ESP-8266-based, and if you can find the right locations on the PCB, you can reflash them with WLED.
By the way, if you haven't tried 滷肉飯 (lǔròu fàn, or braised pork with rice), you should. You can't walk more than a block in Taipei without finding it, but I've seen it only once in the US.
You can follow the "correct horse battery staple" method the author referred to in the article. Another handy tool is a BIP39 seed generator (https://iancoleman.io/bip39/), but use the generated seed as a small pool of candidates that might catch your fancy. "hockey rival" or "pepper garment" or "frozen artwork" could be project names.
Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that".
Does the modularity make it easy to steal the accessories? I'd be sad if my new customized truck were downgraded to the base model while parked on the street overnight.
On effective engineering teams, there's always at least one person who is fluent one layer below where the rest of the team operates. That person tends to be extraordinarily useful in tricky situations. Examples: someone who can read assembly on a team writing C; someone who spends a lot of time in the browser debugger on a frontend team; or someone who is comfortable stepping deep into third-party library code with a debugger.
If any of these examples are familiar, you might chuckle that of course everyone on the team has these skills. But there's a big difference between someone who can barely parse the symbols, and someone who can actually interpret them and extract meaning.
Five to ten years from now, I have no idea whether software engineers still be coding. But I'm sure there will still be code. Do you want to be the person on your team who is fluent in it, or one of the rest who rely on that person?
We're seeing the first 20 years of the dot-com cycle, but compressed into two years, and trying hard not to fall into the tar pit of ad-supported services.
Hopefully it would be less of a criticism of the system, and more spurring people to ask questions like "Wait, why did you leave a hunting knife on the coffee table?"
Design a scheme that equips parents with better tools to be better parents, rather than one that reduces the scope of parenting responsibilities.
Rick Beato has at least one child with absolute pitch, with stunning ability to name chords and the discrete notes in them. Here's the short video: https://m.youtube.com/watch?v=t3Cb1qwCUvI
I'm not a musician, but I'm told the kid's way of naming the chords is particularly adept from a musician's point of view, and that's because the dad (a very accomplished musician) helped teach the kid. I am sure Rick has made more videos about what he did.
That's right. This requirement makes a little sense if you don't actually know the signer and could conceivably end up in court with a forensic handwriting analyst testifying whether the signature was a forgery. Anything involving notarization, for example, should pass that analysis.
But for the other 99.99% of signatures in the world, any mark at all is fine, and insisting on more is wasteful bureaucracy.
I think they compared the first signature to the second and saw that they were too similar. They wanted the sequence 1. Download PDF 2. Print PDF, 3. Find pen, 4. Use pen to scribble name on paper, 5. Scan paper to PDF, 6. Upload PDF.
Without diving into too much minutiae, a legal signature can be any mark the signer intends to act as a signature. It could be a bird you've trained to poo on command onto signature lines.
In my case, this instance with Schwab was the first of a lot of similar paperwork I was going to have to do, so I pulled the ripcord when I saw how they were going to approach it.