If you can convince the higher ups that migrating tooling provides business value, you can do something that requires zero insight or creativity for a few months and at the end of it be promoted for organizing a successful migration despite delivering zero measurable business value. The effects of the migration are gonna be second and higher order effects that are impossible to separate from the rest of the business so you can just claim the tooling was the leverage that let the people doing first order work succeed. Being a tool astronaut lets you claim a portion of everyone else in your orgs success without ever taking a professional risk, since your odds of being called out for an ineffectual change are near zero, since there’s no first order signals.
I’m not saying modern tooling is useless; I don’t use ed, cc, and make for my development. But there’s a huge difference between a zero to one tooling effort and an N to N+1 tooling effort. The first one requires figuring out all the implicit/implied/manual parts of the process. The second one is often just turning one set of configuration languages into another.
NorCal to SoCal using regional airports (avoid sfo lax etc) can be less than 2 hours door to door. Online check in + no checked bag means you can show up at small airports 30 minutes before takeoff. 50 minutes in the air, 10 minutes to deplane and leave the airport, and less than 15 minutes driving on either end and you have 2 hours door to door (and a lot more leg stretching than driving the 5).
Skid is another word for shipping pallet and it’s called skid row because it’s next to the freight train lines into downtown. Pallets would get stacked high along the streets, hence skid row. There are plenty of cities across America with their own area called skid row. The name has nothing to do with the current homeless population.
It is common for poor industrial areas to end up with large transient populations, but that’s a case of convergent evolution.
Ehh they make great products for smb/coliving/coworking spaces, where you need better hardware than the box the ISP gives you but you don’t need the kitchen sink that comes with Cisco. Simple enough that a slight savvy frat bro or small business owner can set it up in an afternoon and have seamless handoff across a large space with several access points and PoE.
You can’t unsend an email because you can’t force someone else to delete something. Emails end up as files on someone else’s server. Claiming this is a UX issue is intentionally missing the point. If this is legitimately a foreign concept to you, an afternoon setting up postfix and playing around with it might be worth your time. Email is a protocol, not a program. A “delete” request would be just that, a request.
You can “unsend” on those platforms because the GUI does not display files saved locally, it always fetches them from the server. If you could “unsend” on a version control platform, then it would cease to be distributed version control. The code would have to live inside the VCS app (the same way messages are in memory in slack), or you’d have to give a network daemon delete privileges on your file system.
Imagine if youtube-dl used the model you’re proposing. Letting the git equivalent of “unsend” propagate through the system takes you from a redundant system to, not a system with a single point of failure, but even worse, a system with many points of failure.
Git is for helping develop open source projects, where sometimes a random gal who will never show up again fixes a small thing and sends the maintainer the diff through email. If you want a tool for the high trust environment of your individual team, git will never be what you want. It literally wouldn’t work for its intended workflow if it did what you want.
Many creative productions take on a similar structure to what he proposes. Many entities, some individuals, some partnerships, and some corporations, come together to produce a single work. The associations dissolve when the work is finished.
The great grandparent to your post (the one who initially brought up the necessity of rote learning) is a quant at a market maker.
Anecdotally, my favorite professor from undergrad (born in China, PhD from the best department in his field [my personal opinion]) said he thought the reason for Russian/Chinese dominance in certain areas of math was due to how those areas benefitted very much from rote practice. He advised all of us (American undergrads) to drill and kill certain techniques in order to build up our pattern matching.
I don’t think they’re advocating doing hundreds of worksheets on the power rule or trig substitutions or memorizing line by line proofs. Our brains do follow formal rules when doing math, but the insight necessary to find a way to solve a problem that isn’t straightforward isn’t through application of rules, it’s through a tacit intuition that you build up by doing lots of math. There is no other way.
It’s like how everyone feels like they understand physics to a PhD level while watching the Feynman lectures, but if you were to hand them any of the problems afterwards, what seemed like such a natural stream of thought is just simply out of reach. It’s much easier to go over something and declare “this makes sense” than it is to come up with that something in the first place.
I’ve found Elixir (+Erlang/OTP) to have some incredibly powerful primitives that make it fairly simple to develop concurrent programs.
OTP underpins WhatsApp, Facebook Messenger, and Discord. People have been building very cool high availability embedded Linux projects using the Nerves framework. It’s very good for certain types of concurrent programs.
It won’t take over HPC simulation any time soon, but most of us aren’t working at Sandia, Oak Ridge, etc. Its great for systems that should naturally scale out but don’t map naturally to a GPU. For systems that want to scale up but are forced to scale out due to frequency limits, it’s not as good as C++ written with uArch in mind.
This is how some video game demos are managed. Subtle color variations are used throughout the game window to uniquely finger print each copy of the game during media blackout.
When I tell people that Finnish middle schools don’t have bells and the kids just go places when they need to they look at me in disbelief. Kids live up to the expectations they are given. The patronizing nature of the American education system is one of the reasons why people here have such a hard time taking personal responsibility for things in my opinion.