With regards to Elm and some others, you have Functional reactive programming, reactive programming, Rx, it goes by a variety of names. It’s most famous for transforming UI development some 8? 10? years ago with the widespread adoption of React. But it’s been around longer in various forms. Implementations can widely vary but the general concepts are very similar.
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.
Holy cow. This! Exactly this! It happened in big corp., I am working at right now. As an engineer, I just watched it happen. When I tried to explain to other engineers, most didn't get it. Only a few got the trajectory we were put in by higher ups for credits they were aiming to get. But those few were onboard or powerless as me.
We just observed it happen. As the engineers, we did our job best we could regardless. Things broke, we fixed. Somethings rolled back, and even for those they claimed credit & celebrated for re-inventing the wheel.
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.
It's not named after homeless people, I'm saying the character of the place has been the same since like the 1890s. That part of town has always been full of transient and destitute people no matter the flavor of local government, is the point I was trying to make. The OP comment was implying some false correlation between homelessness and progressive government. Lest we forget it was progressive government initiatives that ended the great depression and both peace and wartime public works projects, not private corporations, that finally got people back to work decades ago.
That is indeed the progressive interpretation of those events. The other interpretation is FDR's progressive policies extended the Depression into by far the longest in US history.
The banking runs were caused by the fixed exchange rate between gold and fiat money - in 1929 one could double one's wealth by buying gold from banks at the official exchange rate. This naturally caused endless runs until the banks either collapsed or FDR (correctly) suspended such sales. The banks remained crippled for lack of money because the Federal Reserve Bank (not a free market bank) failed to understand what the problem was.
The country came out of the Depression late in the 30's because of vast quantities of money flowing into the country from foreign countries buying arms.
If you're going to correct someone, isn't it worth spending just a few minutes doing due diligence? Skid row comes from logging roads where the logs were skidded down the road.[0]
Not even Bay Area prices. A Jr. SWE after overhead (benefits, HR, laptop, office-space,...etc) is easily costing the company 150k+/year in most markets.
Indeed, but take it a step further. Two ten thousand dollar servers in your basement with UPS and some rudimentary failover configuration is basically fire and forget. Remote in monthly and install updates. Done.
Until there's a power outage, flooding, malice, etc.
I think the main issue is that the cloud providers don't publish much about outages that don't affect the end-user. I mean a failed hard drive happens all the time, but S3 is never affected by that.
Depends on your bandwidth requirements. Also, if you want even higher reliability, you might consider getting two independent internet links into your basement, which is pretty doable in an urban setting.
For a long time, my off-site backup was at my grandmother's house because it was the furthest geographic location I could give someone a box who would leave it plugged into their Internet. ;)
Amps * Volts is power. Power is a proxy (a moderately good one) for air movement (a mix of volume/mass at a specific [back-]pressure).
It’s not likely that a silent 2W fan will move a similar amount of air as the stock 14W fans. The enterprise gear from HPE is pretty well engineered; I’m skeptical that they over-designed the fans by a 7x factor.
Operating voltage tells you “this fan won’t burn up when you plug it in”. It doesn’t tell you “will keep the components cool”.
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.
Ubiquiti is amazing for your home. You can cycle 50km on your Peleton and still get excellent WiFi signal. Which other router can deliver such outstanding performance!
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.
> Emails end up as files on someone else’s server.
When I use my Gmail account to send an email to another Gmail user, this is obviously not the case. Many adults in their twenties have never used a desktop email application - at my company the younger new hires need some time to figure out how to use Outlook, and they're engineers. They've grown up with the cloud as a given, local storage as the exception, and centralized messaging apps as the default method of communication.
I'm not going to argue about whether way of thinking about computing is any better or worse, but undeniably convenient, and it's definitely the direction we're headed.
Thanks for the explanation, but I ran mail servers for ~25 years. I am familiar with the technology, and in the mid-90s even wrote a chapter of a book explaining email. And I've been using version control even longer. Maybe try rereading what I wrote without the assumption that it comes from ignorance.
I think your comments are coming from ignorance, though.
Without trying to be snarky - All your comments directly ignore that what you're proposing values one stakeholder more highly than another.
People keep pointing out that there are two users involved in this exchange, and they both weigh equally, and you dismiss them and talk about running mail servers 25 years ago (who cares?).
You keep saying "I should be able to unsend my email". Let me rephrase your question - Why should you be allowed to delete my email?
I have in fact never said "I should be able to unsend my email". Once. In my life. Please try to argue with my actual points; I don't have time for straw men.
>Asking to unsend an email is a reasonable request. The answer could be yes or no given the circumstances, but it's only an absurd question to people who have taken a 1980s technological choice and treat it as some sort of unalterable gospel.
---
We're here answering affirmatively that "No" is the right answer for a LOT more reasons than an appeal to authority and history, and you accuse me of a strawman?
Yes, I am indeed accusing you of a strawman. You seem very much in the discussion to win it, whatever that means to you. I can only hope that, having decided you are victorious, you'll now leave me alone, because none of your comments seem particularly productive to me.
