Please go take a look at Rust and/or Swift to see how nice a language without null feels like.
It’s not that there’s no way to model nullability/optionality. It’s just that there’s a much better way to do it. Simple, obvious, composable, no quirks.
They're both fully functional and amazing games. Ceaser 3 is a really fun, "modern" strategy game and one thing I (and my parents) liked at the time it came out is that all the military stuff is optional. You can get just as much glory for building a grown with a huge economy and large number of exports as defeating Hannibal's elephants.
Both of those open reimplementations require the base game, which is very very cheap on gog.com. I'd really recommend it.
I read somewhere that the amount of programmers in the world doubles like every 5 years. That means that at any given moment, half of programmers have less than 5 years of experience.
The biggest problem with intermediate level programmers is their love of hard and fast rules. It's like they have a backpack full of hammers ("best practices") and they're running around hammering everything in sight. For this I feel like it doesn't really matter how much experience you have in an individual piece of tech - the overall amount matters more.
I find it hilarious that you’d mention “20 years of experience”. I work on a team at the moment with one of the most dogmatic developers I’ve ever met, and when challenged his rationale for any decision is “20 years of experience”.
He was recently asked to fix a rather simple bug in a C# project, a language he doesn’t use very often, but he was certain this would be an easy task for him. The project used a small amount of unmanaged resources, and he just couldn’t figure out how the ‘using’ keyword worked. He spent a few days trying to get to the bottom of ‘using’ before demanding to be sent on a C# course, which everybody thought was a great idea because it would keep him busy for a while. Maybe he’ll have “21 years of experience” by the time he gets around to fixing this bug.
Yup. Also, unwillingness to learn, which, to me, is a crime.
Learning is difficult; maybe because it starts with admission of ignorance.
Most of my work, these days, is a ghastly chimera of techniques, from 30 years ago, grafted onto patterns from 30 minutes ago. Real Victor Frankenstein stuff.
But not insurmountable. In my own experience, all it takes is a small amount of consistent effort each day. I've learned a few programming languages that I use regularly like this, I learned sleight of hand card magic like this and most recently, I've learned to play guitar like this. This year, I hope to learn Spanish like this too. Many people don't want to put consistent regular effort in and are looking for shortcuts. That doesn't work.
> a ghastly chimera of techniques
Well, yeah, the right tool for the job, right? But it does work, so...
In order for a programmer to program in many patterns elegantly, one must first have understanding of those patterns and how they are roughly reduced to machine code.
The skill of experiencing trumps the amount of experience.
Bad programmers need to hone their skill to experience in order to become good programmers. The most popular way is to provide them a safe environment to make mistake and learn from it. But the most important way is actually knowing that skill of experiencing and getting out of biases are important, like in this case "if OOP is indeed bad, why is it invented in the first place", and the rabbit hole actually gets interesting from here.
At least that's my take after a few years in the industry.
I recommend people Zsh: it's very familiar, scripts copied from the internet will most probably work and they have lots of flexibility to adjust it to their needs.
I personally have a Mac with Fish installed, I don't enjoy the process of sharpening my tools, I'm willing to give up flexibility in exchange of great defaults.
It's the same reason why after I learned how to use a sharpening stone, I ended up buying an electric knife sharpener.
In my personal experience any radio controlled aircraft coming near a bird's nest will be challenged in the air. It certainly stresses them out in the mortal danger kind of way. It made me change where I do my “Park Flying” before I injured a bird.
I've flown a lot since the late 90's. A bunch of different areas. My dad was very into it. I've never had a bird attack an airplane or helicopter. I've never flown quadcopters/drones much as they require no skill and not fun. The closest I ever saw was a small foamie where a bird swooped towards it. Never came that close and moved on.
