I’d run through PragProg’s Agile Web with Rails first, and then The Rails 8 Way if you want a reference. Books are good, but jumping into videos from GoRails or Drifting Ruby might help more with real world patterns and problem solving with Rails.
Absolutely. I’ve been using rails for almost 20 years, and it’s been mostly a joy to watch it evolve. I will say- there was a short period of time (the webpacker era) where it was losing its allure, but that already feels like a distant memory. For the last decade that I’ve been doing freelance/contract development, I’ve always been able to find plenty of Rails/Ruby work, so it still feels like a valuable thing to specialize in as well. And the Ruby community is just incredible. Rails motto should be “come for the productivity, stay for the community”.
If the drones were “authorized to fly by the Federal Aviation Administration”, then why did the same FAA feel the need to temporarily put in place dozens of drone bans over critical infrastructure?
Because a loud contingent of poorly informed people were looking up at commercial aircraft and losing their minds. The FAA couldn’t really ban all aircraft because this would be very disruptive. And they knew there were not any drones, so a ban on drones made perfect sense because it checked all the boxes:
1. Has no effect on the normal world
2. Quiets down the kooks
I uploaded a photo of a helicopter cockpit, flying up the Talkeetna River in alaska, which was very out of focus in the background. It knew exactly where I was, and even mentioned I was in a helicopter. And that it was fall!
Tip for Meta engineers: when your service is failing, don't just log people out and prevent logins. Display a cute image that shows that the service is drastically failing (like a whale or something), and then people will know to stop trying to repeatedly log in. The public might even come up with a catchy name for the whale.
Beyond unbelievable that going on an hour later, they're still showing "incorrect password" errors. How many hundreds of millions of people have wasted time frantically trying (in vain) to reset their passwords and pointlessly freaking out that their account might be compromised? What a bunch of careless, incompetent excuses for engineers.
Imagine how many hundreds of millions of users waste their time using instagram and facebook on a daily basis. Safe to say they don't mind wasting their customers time
What a poor bunch of overworked human beings, with almost no control over the product they work on. Frantically following the whims of managers, reduced to labour units in this late stage capitalist hellscape.
It probably depends what team you're on, but I would not describe it as "pretty shitty." Being oncall for a 24/7 service sucks, yeah, but for my team it is one week a quarter and I haven't had any outside-of-biz-hour alarms the last few shifts. Other than that -- my work is challenging and interesting, my colleagues are friendly and smart, and my manager is decent. Not a lot to complain about.
Major outages are periods of intense stress and extremely difficult to operate in. The folks troubleshooting may be many things, but careless and incompetent are unlikely to be among them.
I can almost guarantee you're getting mercilessly downvoted because half of the people here are sympathetic Meta worshippers who desperately (1) wish they worked there and (2) know they'd probably contribute similarly to this same horribly engineered system.
Having had a look at desperate Twitter posts during a major outage of a big German email provider with similar failure mode (login failed silently), it seemed like many people assumed that their email account was hacked. Close enough.
Right? I know I was like "oh, I haven't typed in my FB password in eons... maybe I changed it at some point and forgot? But if I change it what happens to all related services, is it going to log out my kids' Messenger Kids devices? Those are such a pain to log in. Should I change my password or not? What do I do?"
Surely the repeated logins can't be helping the situation. I suppose it is entirely auth related across all Meta products. The repeated strain could pose a cold start problem for example.
> Display a cute image that shows that the service is drastically failing (like a whale or something), and then people will know to stop trying to repeatedly log in.
Probably not so easy to implement in behemoth apps, consisting of 20'000 source files...
For anything outside like-ing and post-ing, facebooks UI/UX is horrendous. Even Internet search does not help to find out how something trivial is done... The only way is to watch youtube videos.
> For anything outside like-ing and post-ing, facebooks UI/UX is horrendous.
It isn't perfect for even that IMO.
> Even Internet search does not help to find out how something trivial is done... The only way is to watch youtube videos.
That says more about where the web is heading than about facebook. Video is easier to monetise ATM⁰, and these days people don't put helpful stuff out there just to be helpful as much as they once did¹, so content creators are making them instead of simple web pages.
--
[0] Everyone wants to be the next big influenza who doesn't need a day job to get by.
[1] That sort of people are still out there, though they are somewhat drowned out as the signal-to-noise ratio heads inexorably towards “WHAT? WHAT?! I can't hear a single thing above the manscaping adverts!”.
Unless it's an outage in their ability to log into their own servers, they should be able to swap out the login page with a static HTML page explaining the outage. Maybe a 503 status code.
Yes of course it was. The point is, an hour later, they could have hit a circuit-breaker to get people to stop trying and going crazy over an error that is completely inaccurate.
