The one thing I do notice is that on some very poorly built websites there will be a bug and it's because they haven't checked in Firefox or because I am blocking things that are no longer blockable on Chrome, but this is rare.
The one thing I do notice is that on some very poorly built websites there will be a bug and it's because they haven't checked in Firefox or because I am blocking things that are no longer blockable on Chrome, but this is rare.
This might make an arbitrary number go up in test suites, at the cost of massively increasing build complexity and reducing ease of working on the project all for very minimal if any improvement for the hypothetical end user (who will be subject to much greater forces out of the developer's control like their network speed)
I see so much stuff like this, then regularly see websites that are riddled with what I would consider to be very basic user interface and state management errors. It's absolutely infuriating.
That was an interesting paper but I'm confused as to what they actually tried to achieve. I'm also confused how they achieve any turning in a model that has infinite friction on one side and zero friction on the other. My brain is having trouble understanding how such a model could ever achieve anything other than a straight line.
I'm not saying that's not true, but we shouldn't take it at face value that Amazon's internal values drove its success. The values stuff seemed to me to be mostly propaganda when I was onboarding at Amazon.
Could it just be basic market forces that caused Amazon to grow, attracting the best talent due to high compensation, which caused a (to borrow terminology from Bezos) "virtuous cycle"?
People talk about Amazon's corporate culture in a way that I don't see them talk about Google, Facebook, Apple, or Microsoft. Which makes me inclined to believe that it's mostly hocum used to justify where they ended up, instead of just attributing it to being in the right place at the right time.
The CEO’s “research” appears shambolic and dumbs down what engenders such loyalty to Southwest. Next thing you’ll know they’ll add 777’s, ERJ’s, and A320’s to the bestiary, because it’s also what the other airlines do. Southwest became the leader because they led and went their own way instead of followed.
At the end of the day, 90% of Southwest fliers choose Southwest because of price and availability. Embiggening the boarding process with boarding zones won’t sell more seats, particularly middle seats.
The 10% of business travelers who choose Southwest crave its no-fuss “Greyhound of the skies” approach, and these will be the most turned off.
CEO pay is like telling your driver to redline the engine all he wants. He’ll outperform the competition (with significant personal upside) until he blows the engine (and gets replaced a few years later, having earned billions).
I personally stopped flying Southwest years ago when someone blatantly cut in line while boarding (like a whole section earlier) and I told the gate agent and he rolled his eyes at me and said "we're all trying to get going" I think their seating and check in system is dumb especially when they set up this elaborate system where you have to rush to check in exactly 24 hours before then get mad when you expect them to enforce it.
Fuck Southwest
Be realistic. For all bad mozilla foundation/corporation/toppahs did, the code is still open source and relatively free. If even something called IceWeasel almost had a shot at forking, the bar is pretty low.
We're talking decades of features they have to support - unless they're planning on strategically dropping support for older unused/deprecated parts of the standard? Even in 2008 Google made the decision to use Webkit for their browser because they understood what an enormous undertaking it would be to write their own rendering engine. That was 16 years ago.
If you already have fundamental web dev knowledge, you'll be able to switch between them easily.
That's why I like Remix. It's react + web fundamentals. I'm happy to jump into a Vue, svelte, angular project. It's not all that different
In the past 2 or 3 years, they just "gave" up, turned it into the biggest most bloated framework in the frontend area while the official Web APIs in the browsers evolved so much that React is actually completely useless and now it is completely useless with a compiler.
I'm wondering if that was actually the reason they pivoted to this Frankstein? The loss of relevance as a frontend library.
Anyway, I jumped off the bandwagon and don't have a say in this fight anymore. But I'm doing my part advising every Junior Developer to not make the mistake of choosing React today.
I feel like from an employability perspective I shot myself in the foot, but I also dislike both of those frameworks. So maybe I should just quit being a front-end developer and try to retrain as something else.
I try to keep it simple: I have the $95/year Chase Preferred. I definitely get way more than $95 every year in rewards. It's also helpful for auto converting currency when abroad (the fees add up like crazy if you let individual services do this for you.)
I'm currently in Paris on a flight I booked with points but I use this card basically exclusively for all my expenses (except ones that have to be paid with cash/bank acct)
I recently tried to get one of these higher tier cards like the Reserve just for the lounge access and even though I have near perfect credit and longtime customer they wouldn't give me the joining bonus. It's not worth it overall, especially with these changes.