Even if you did make this adjustment, there isn't a good way to know you've done it properly. I just avoid relying only on mirrors. I don't feel safe unless I turn to look.
The "Apple tax" is one part of this, another is that they obviously think people are comfortable enough with signing up via the web on a mobile device, to make this decision worthwhile. Seems worth remarking upon
It’s really incredible how common those people are, and how they’ve managed to eke out a living. The thing that has surprised me most is that there is no predictability to how a candidate will perform on a simple programming exercise, new grads are equally likely to pass as people with 15 years’ experience. (The failure modes are different though, new grads spend lots of time talking through every variable assignment etc; experienced people tend to throw every technique at the wall when they encounter an issue instead of slowing down and thinking through what they’re doing)
There is a whole chain of people involved before software gets designed, or built, or deployed. If you’re making software for healthcare institutions then that should include people with medical expertise.
Sure PHP+Ajax still works, knock yourself out using that approach if you want. I won’t want to maintain your code, but feel free.
While I don’t disagree with the general notion that old stuff still works and new stuff is not necessarily better, this notion is incredibly well-worn around these parts. It really would be nice if people stopped driving it into the ground pretending it’s an interesting or original or contrarian point.
What I do find interesting is one of the replies by someone saying they quit webdev back in the PHP+ajax days, precisely because they found that approach so much less simple than it is often claimed to be. That’s an actual interesting point! But we don’t want to talk about that, we want to talk about “JS devs love everything shiny that came out 3 days ago.”
I almost always just want one of these things to keep a session alive even if I disconnect. (My terminal app has tabs so I don’t find muxing between terminals particularly useful.) But they have 1000 other features which I’m sure must be wonderful but just tend to get in my way.
I’m not sure how much this actually clarifies things, to be honest. But, who knows.
And about the cookie banners, we didn’t add them because we thought normal people give a crap about cookies. We added them because lawyers told us we needed to. Nobody is happy about those things- users, developers, nor designers.
Maybe I’m overstepping here, but I find it unbecoming to assume that everything developers make is just because that’s what they felt like doing that day. We aren’t cowboys, we take orders just like anybody else.
I stopped using booking.com after I booked a hotel for the wrong dates, and they made it really difficult to cancel, and charged the entire price of the stay. Now I use aggregators to figure out where to stay and then book directly with the hotel.
There is much too much consternation over ASI, it really is much ado about nothing. I worked for a couple years on a team that didn't use semicolons and it wasn't a problem, it just didn't come up. Even if you were really fearful of those spooky edge cases we all hear so much about, you can just lint for them.
Much else here is good, but I'd again disagree about function scoping. And I wouldn't say `this` is a minor problem, it's a gigantic disaster and probably the worst part of the language, especially for those just learning.