368 karma · joined July 23, 2024
There's a joke I've told many times in interviews if they ask me to define what a full-stack engineer is, to which I joke "It means I do whatever the senior engineer doesn't want to do, which 99% of the time is front-end". The people I tell it to laugh, because it's funny but also because it's true.
On the front-end you're dealing with more customer/users and it's inherently more of a servile role, while it's much easier to be stubborn, eccentric, 'powerful' in the tech-facing backend.
I'd also wager there's a certain "tech purity" angle too, given the inherent reverence foisted upon lower level languages and programming fields that is seemingly rife.
To play devil's advocate on myself, perhaps it's more that the higher end technical complexity challenges for Front-End aren't commonplace enough. I've had the fortune to work in a field where the level of necessary technical complexity on the front-end part of my job is very high, so ymmv
"End of the Road for Google Drive in Transmit"
The being unfamiliar with Transmit the "and" gave me a startle
hence why it's a current go-to in the protestors playbook. If/When such laws are introduced, different tactics will be used instead, I predict.
Knowing the rough order of events (as per the flow of a story) is important, as is the relative timespan, but a lot of history schooling puts too much emphasis on knowing the exact dates of certain events, which I think really subtracts the experience for many.
If you actually believe that, consider yourself very lucky.
React, like any FE framework, can be implemented well or implemented badly.
React benefits from a very strong (imo the strongest) ecosystem, so if you set up your tooling and patterns correctly its fantastic.
Here's my personal preference: NextJS as the backbone, RTKQ as the central data retrieval/API calls/caching management, RHF for form handling, ag-grid for data grids, and MUI as the component library (can optionally switch this to any equivalent).
If components are designed sufficiently generic and customizable, RTKQ is used to keep data fetching on component instances, and central state storage is avoided as much as possible, it's a great system. Unless you just really hate JSX syntax or something.
So even if there is tiered support, they'll want an SME on some aspect of the system on-call as a fallback for higher/highest level triage.
It's hyperbole like this that makes me a constant skeptic.
https://emilkirkegaard.dk/en/2013/07/intelligenceiqgre-by-ac...
My last company had codium on our internal codebases for PR review/summary. I found it neat, but I never saw it make any suggestions that surpassed linting. But as a lazy dev who didn't want to rewrite all the details I put in my commit messages when making a PR, I felt it did a pretty good job summarizing.
Funny story: One time I jokingly asked it to rate the skill level of the programmer who wrote a certain PR (which was created by me). It was very complimentary of my skills, which I shared in the humor chat about how it was a very smart AI. The very next day I was laid off (unrelated, it was along with most of my team).
PHP usually ranks pretty high on many "developer hate" polls, so it's not too shocking to me that Hack never got the hype of React or Golang.
Cruises fill the "cheap Caribbean getaway" segment for the sizable American population where getting a passport or not having a criminal history would otherwise be a blocker.
Arguably it's also a motivator in why Cruises have the reputation they do, but that's beside the point.
25 years later it still isn't (joking... kind of)