HN user

ookblah

1,403 karma
Posts3
Comments396
View on HN

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.

i actually like that the crop snaps after the fact, it reminds me that the crop is in fact active, same with rubber-banding type stuff.

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".

I caught the car 2 months ago

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".

you learn by struggling and slogging through, even as a senior if your shit breaks it's on you to understand why. no LLM will shortcut that process for you (even asking LLMs why something is wrong requires you to actually understand it eventually, aka LEARNING). how that happens is up to the person.

i don't understand all this fear projected as if people won't have agency of learning just because LLMs make it easier to do certain things. i don't think it's contradictory at all. half the people here will never have to wrangle the bullshit i dealt with 20 years ago and i'm sure when i was dealing with it there was another 20 years of bullshit before me lol.

if you vibe code your app with no regard for the underlying code you will pay the price for it at some point in the future, anybody worth their salt will slow down enough to figure it out the "artisanal" way.

having tried to wrangle this on my own over months and still seeing gaps everyday i have to raise severe skepticism on this lol.

you mandate and "solve" this in a few weeks over 1:N channels and measure on a metric that nobody even fully understands yet = someone getting paid to bullshit some metrics on agentic productivity to executives. i agree with other posters, 12 months until a dumpster fire of shit reveals itself.

FWIW, i think it is the future but not in the way that'd described here.

pretty much you have to build for humans as the "source" of truth and then have a robust agentic surface if you want to survive as a company. after using linear (for ex.) u can really see how it all fits together, i can be in cli, co-workers in slack, cowork, whatever and update tasks from anywhere). i refuse to use shit where i have to context switch by going into an app now. posthog is another good example of where it's going. the dirty detail now is that you HAVE to have the actual app so you can still manually look at data and do operations.

mcp is really easy for non-techies to understand. if i own the system, can install cli tools, cli + skills beat it every time and i can tweak, etc. if you're asking someone else to do that there's real friction. i'll sometimes use mcp if i just want to get up and running am not watching context as much, then if they offer a cli i'll just move to skill + that or write my own wrapper off the api.

"I’ve helped found six companies in my life, and been involved in the start of a handful of other startups and nonprofits, and literally every single one was full of people who love to work hard"

lol, no offense, but if you helped found the company this pretty much excludes any impartial view of what your employees actually might feel, and i say this as a founder myself.

it's a wonderful thing to have a team that is on board with you and the mission, but at the end of the day they just want to go home and relax and you want to work on your baby.

that's not to say people are lazy by any means, just don't drink the coolaid too hard. even if i'm working for someone else i'm using my hard work to optimize my free time not putting in extra work unless i'm getting paid for it.

conductor was a non-starter for due to requiring the github + PR workflow. do you just allow management of a local repo without pushing us into a specific git flow? worktrees for diff work is fine, just if you want to handle the merge yourself (for whatever reason) how would that work.

ask ai for advice, ask it to steelman an argument, ask to replay what your situation from the other perspective (if it's involving people), push it hard to agree with you and pander to you, then push it to disagree with you, etc.

once you have all the "bounds" just make your own decision. i find this helps a lot, basically like a rubber duck heh.

i feel like people should be focusing on the damaging things that aren't just "ai" (like what he hell does that even mean, it's too broad?).

dark app patterns, gambling, etc. like seriously, i know we all want to hate on llms or whatever stealing our jobs or making us stupider but has this been any different from the past in that regard?

whether it be radio, tv, computer, internet, video games, etc. all of these claimed to be doing something "to the children" but i agree with another comment said kids will figure out a way to learn and utilize the tools given to them.

did me "offloading" my thinking to google or some computer instead of cracking open some library book or doing calculations by hand damage my thinking at the time? no... because a sufficiently motivated person will learn regardless, figure out why things work the way they do, and rather it's better access to said information that helps.

we should be fixing the motivation problem rather than the tools which we've been trying to do for decades. teach people the framework for solving problems and critical thinking. kids nowadays have way more things demanding their attention and it's been on a decline far before this AI wave (cough social media). we literally sound like old farts lol.