One could argue that with AI writing so much code, the ease with which humans can read & understand it (for review purposes) is even more important than before.
162 karma · joined July 19, 2013
Old English was a Germanic language, later heavily influenced by Norman/French vocabulary. French of course descended from Latin, and Latin and Germanic languages both belong to the Indo-European family of languages. (The "C" language of humanity, if you will.)
The lack of debugger support will put some off, but I bet they'll get to it someday. It's already progressed so much in the four or five months I've used it (esp. Vim Mode).
To be fair, Democrats are historically only marginally better in that regard.
...sounds good to me!
Even worse than the verbose, repetitive, and error-prone conditions/joins was the few times when something big in the schema changed, requiring a new column be added to the compound key. We'd have to trawl through the codebase and add the new column to every query condition/join that used the compound key. It sucked.
I'm becoming a true convert, though I occasionally must drop down to a termianl for advanced vim features. That's high praise coming from me, as I have a high bar for adopting new tools.
Combine that with one headline-grabbing (apparent) suicide during a deposition, and we're now all primed to notice these deaths and attribute intent.
Instead, if you focus on not repeating the important “knowledge” of your code (algorithms, business rules, etc), it’s easier to avoid the trap of over-abstracting.
A few years ago I had to migrate an ancient VM running OpenSSH (for SFTP only) to our k8s cluster. 99% of the users had passwords instead of keys. Easy enough to run sshd in a container with a mounted volume, but I wanted something to recognize and block repeated bad login attempts (the old VM had no such protections).
sshd doesn't do it natively, fail2ban wasn't a good option since you generally don't want a pod messing with a k8 node's iptables. What I ended up with was a Ruby script with 3 threads: One to monitor the auth log for failed logins, a second to lock accounts with repeated failures during a given window, and a third to unlock them after some period (and in the darkness bind them). Definitely some caveats in there, but it was an improvement over the status quo.
And I can assure you, the bad kind you describe is not the exception. What percent it actually represents no one knows, which is a whole other problem. But it's not just a few people here and there.
There are huge networks of people and conferences full of vendors selling parents do-it-all-yourself curricula. In the 90's and early 2000's Bob Jones University (even most evangelical Christians think they're too extreme) found it profitable to sell pre-recorded math and science lessons for high school level homeschoolers. And while I know what valence electrons are (my public school peers probably forgot), I also thought the Earth was 6000 years old into my mid twenties. And like I said, they didn't make and sell all those videos just for me.
It would be great to have more hard data on the current state of homeschooling/home tutoring though...
So from a purely practical standpoint, don't home school MOST of your children. If your daughter is truly on the autism spectrum and the local public school can't effectively deal with that, then +1 for homeschooling her. For children who don't have special needs like that, there's no real need for it. You can send them to public school and still be involved in their education. Learning how to think and learning how to learn are perhaps the most important skills, and they can still be learned in the home.
So come up with a short term plan, then worry about the long-term plan later. If you really think you're cut out for this (and yes, truly ask yourself that in a mirror), find a part or full-time remote job right now. Take whichever you can find first. Plan to send your kids to public school except for the autism spectrum one. This will allow you to give both her and your new job a reasonable amount of attention. Even with only 1 child at home you'll find it quite challenging, though hopefully also rewarding. Probably not exactly what you wanted to hear, but practical solutions rarely are.
If you've read this far, allow me to vent about homeschooling for non-special-needs reasons. Please don't. There's a reason everyone thinks home schoolers are weird. We are. Despite parents best intentions ("best" ranging from individual attention to religious dogmatism), we have near zero interaction with our peers. When we do, it's a very small number of them and for very short periods. We have near zero experience interacting with anyone or anything outside the home. The real world becomes terrifying when you're stuck in a small, safe, homogeneous bubble and don't realize it. Finally, we're with our parents and siblings nearly every minute of the week. That is incredibly unhealthy for a family - being stuck in a house ALL THE TIME with your classmates and teacher. We were all a little miserable, especially in the teenage years. Now if your primary reasons aren't religious, some of that can be avoided, but it will take a concerted effort, which will take time away from your job. And your kids will still turn out a little weird and possibly resent you, even if just a little, for not letting them be "normal."
MVC outlines very clearly the areas of responsibility for the framework. But many of the popular MVC frameworks take it a step further, declaring that MVC should be the primary dividing lines for your app code and business logic, with little thought given to separation along functional/domain lines. (Or in DHH's words, "The framework is the application!")
So is it any wonder that 10 years later, the industry is freaking out because our nice, clean MVC apps became business logic casseroles? Microservices can help with that, just like MVC can help with the PHP spaghetti code that came before. But none of those things can substitute for basic design principles.
I wonder how things would be different if 10 years ago, instead of app/models, app/views, and app/controllers, Rails had promoted app/auth, app/billing, app/spline_reticulation, etc. Might such a simple thing have pushed us in a better direction, leaving microservices to the 10% of apps that really need them? Or would we all have followed that pattern to illogical extremes as well?