mrblampo

My kids have an Ooma landline and haven't gotten bored with it yet. It's been months. The hype is real.

Me too!

Good feedback, thanks! Gemini got a bit carried away writing the README for me. Toned it down and added a demo GIF

DMA in what sub-field?

This is pretty cool

Got a music degree, decided the career wasn't for me, went to a programming incubator, really struggled with interviewing for a while, got a job at a startup, got a job at FAANG, here I am a decade after the career switch

Yep same. "Teach yourself to eat chocolate."

Fun article! Particularly enjoyed the anecdotal evidence from individual soldier's writing.

Thanks, I enjoyed this and it rings true. This abstract concept of "space" getting filled up thoughtlessly, and that "space" being created by unnecessarily breaking things up into smaller parts that don't really need to be separate, makes a lot of sense and I think I've seen this happen.

The article stops short of proposing a clear plan for how to handle the opposite problem, though: Entrenched monoliths. Once a class (or other abstraction) has grown for long enough (e.g. perhaps someone has read this article and is trying to avoid unnecessary complexity of code structure), it can become very difficult to break it up.

Try not to worry about what others think of you, and definitely don't think about IQ. Judgment is so much more important than speed. Why are you concerned with speedy thinking?

Made me laugh out loud

First example seems odd? The author acknowledges that the two proposed alternatives (printing "<function exit>" or actually exiting) aren't great. The fact that the Python REPL provides a helpful hint seems like extra effort to make your life easier. This is especially notable given that in the next example, the author's complaint is about a command _not_ providing special guidance about the thing the user is probably trying to do.