you can also yolo on 0 dte options like 10 times in a row and become one too lol. i fail to see his point in that calculation, he takes an obvious truth, which is sustained growth rate = billionaire and nothing evil about that, but then mixes it in with the fact that 99% of companies stall out and then you have to play politics and extraction to get yourself over the hump. show me a company does that without compromising deals and making deals w/ the devil, etc.
the "hard" part isn't sustaining 15% growth over years, it's doing that in a way that is as reductive as he tries to make it "just build something people like!" and not having VCs and other bullshit trying to backstab and force you into making questionable decisions.
lol if this is an attempt by the admin like the DoD thing to "knock them down a peg" it actually has the opposite effect for me, showing that anthropic is that far ahead you have to resort to dirty tricks.
uh, that aesthetic was there long before tailwind, they didn't have a monopoly on rounded corners and that spaced out look lol. Much more ability to adapt than say trying to re-skin a bootstrap template back in the day.
the entire industry has always been converging toward "cookie-cutter" ui, and tailwind is just this cycle's flavor and now on steroids with AI. Honestly for 90% of the stuff out there that's literally fine and probably better. There was a time when being extra creative in FE work was rewarded. If your product is very brand dependent then yeah maybe try to find your "voice" but for the vast majority of them, esp dev focused, they just need to work on other things and not try to re-invent solutions to solved problems.
i know we all like to pretend our meticulously engineered button and drop shadow animations are actually moving a needle, but you're optimizing the last few percent at that point. most saas FE devs should be solving other problems like the UX and performance and not worry about more creative landing pages.
"A lot of programmers may not know this, but frontend used to be a highly specialized skill, requiring knowledge of semantic HTML, CSS, the differences of various browsers, accessibility, progressive enhancement, network performance, interface design and user testing – to just name a few. To distinguish what they’re doing from what “frontend” has become, practitioners of this arcane art nowadays often refer to it as the “front of the frontend”."
that "knowledge" we held was to combat the absolute shit that was the browser ecosystem 20 years ago lol. you could argue it was a time of great experimentation and creativity, but no unified ui/ux patterns, adding in css hacks and doctypes blah blah to try to catch all these weird edge cases, if you're still reminiscing that time not sure what to say. today's tooling while also messy in it's own way is 1000x bettter. also i've never in my life referred to it as "front of the frontend".
"yes" heh. more a human problem i'm slowly figuring out, spend enough time on this earth and it's honestly tiring. social media and modern new cycle prob just accelerates it.
LOL that's some super heavy duty optics framing on what basically amounts to "we paid out a ransom but don't worry the bad guys assured us things were okay"
in korea u can literally leave ur wallet, laptop, expensive bag at your table and go eat lunch or do something else for an hr and come back and it'll still be there (and people are used to it). one of the few places that surprised me more than japan lol.
i was "cto" at 26 (lol). point being outside of securing a better pay package and using it for job networking purposes your "title" is largely irrelevant as a measure against yourself. don't rely too much on some company handing you a title to determine how skilled you are.
i don't think it's an either/or or "best". highly dependent on industry and application. if you're application is complex no amount of "good ux" can replace a good overview/tour (watch people, they will go in click around to get the lay of the land then be confused usually).
after that its determining how people to digest info, some like docs (me), others want to sit thru a video, others NEED a person to guide them in person, some like tooltips, checklists, etc.
i'm not saying you need to litter your app with this stuff, but i don't think there is some magical UX pattern that always works.
that's not the tooling's fault i feel. i've used LLMs to help explore and debug issues, point me to the right documentation to investigate, etc. I WISH i had something like this 30 years ago.
someone probably made this same argument against certain frameworks over the years and juniors still figured it out. we need to stop trying to babysit learning for hypothetical situations.
the bar to "start" is lower and the bar to actually competency is higher now, juniors who want to actually learn instead of just pressing enter over and over again will do so regardless of whatever you do to "help" them.
this is pointless without knowing what they are measuring. you could genuinely moving faster or you could be optimizing for engineers in a rat race to push more code because all their peers are now doing it because those are the metrics you are measuring for "ai productivity".