This comes up on every single article about timezones. Humans need to know what time it is based on the solar day. If it's 5:00 AM for me and 5:00 AM in Sydney, I have no clue if anyone in Sydney is awake. Timezones are for humans, not computers.
The point is to rely on the abstractions. :) I get similar feelings, especially having been burned by software in the past that purported to abstract things properly. But perhaps unlike other frameworks/libraries, I think Rails has solid abstractions. Of course they're not perfect, but much like abstractions provided by an OS, they are complex, and you mostly don't have to worry about implementation details. (And when you do, that's okay, because the documentation is solid too and the code is available.)
I've been working with Django lately and I definitely had to learn to let go and trust stuff like the ORM. But after watching migrations get handled automatically and easily adding foreign key relationships to tables, I was hooked. I used to be firmly in the "almost never ORM" camp, but that's changed.
I sure am glad my fantastic public high school teachers didn't have your attitude. They sacrificed so much for so little, and I'll tell you what, they made a word of difference in at least one life: mine. From what I've learned of teachers, that's more than enough for them.
Denial is the only way to cope with how impossible it feels to make any meaningful progress. I mean, the alternative is to sit white-knuckled until I die in a food riot. I am well aware of the changes that are coming, and it's one of many reasons why I'm not having kids: I don't believe progress will continue like it has (which was always unsustainable, even without deleterious effects on the climate), and I think the future earth will be much harder for humans in the short term. Sure, humanity will probably adapt, but millions of people might die in the process.
I appreciate the humor, but I think that was a bit of a disservice for her. Because even though you have a cheeky definition, the term does get used fairly frequently in the industry, and it would've been helpful to explain how it's commonly used, even if you don't agree with it.
That's exactly it. For some reason, developers really want to just write code, even though it's for a web service and that web service doesn't exist in a perfect vacuum. (Yes, I do ops, and yes, I'm bitter and jaded.)
Not a day goes by on here where I don't read ten comments reminding everyone that employment is a mutual contract that can be terminated by either party at any time. So I'll say to you what those people say: you can always just get a new job, one where sexism is tolerated.
I have to refresh the page once or twice when attempting to load a tweet in Safari or Chrome on iOS, otherwise I usually get a cryptic "this tweet is not available to you" message or something similar. I also just assumed it was a dark pattern to get me to use the app.
It's because nobody in the industry wants to acknowledge that there's a power imbalance. You really might need a job, but guess what? Your interviewer already has one.