When I see a complex socioeconomic phenomenon described as "just" I know for certain that someone is about to spectacularly fail to have read books.
This is value stream mapping. No, business process reengineering. No, systems dynamics. No, a Krebs cycle. No, ...
People could always do these things. It was never a sword that only AI enthusiasts could draw from the stone. By god people, the AI has read books, can't you give it a bash too?
Right. Because something is reducible, modulo a bunch of stuff you're not looking at, to a simplistic model, doesn't make it "just" that. Use of the word "just" is often a good tell you're about to read something naive.
I recognize all these words, I can sense, perceive, parse and reason about all of these words. Yet I cannot derive a sensible meaning from them. The pragmatics is of a flailing fish singing Waltzing Matilda to a teleporting cucumber.
There's nothing transparent or inspectable about a sparse fog of floating point numbers. Rendered as a picture it's the color of a television, tuned to a dead channel. As a sound: ksssshhhhhhhhh. If you see anything in it that you believe is a real discrete phenomenon then I have a face on Mars to sell you.
You know what is an inspectable algorithm? An algorithm. The old-fashioned kind that were intensional and not gigantic quasi-extensional stews connected to nervous cats in boxes. I'm so tired of this madness. So entirely bloody exhausted. Out of all the manias I've lived through in this trade the current one is by far the most absurd, wasteful and destructive.
Mate until last week I had quite literally unlimited, unmetered access to frontier models from every major lab. No quotas, no brownouts, none of the stuff civilians gripe about. Chairman Mark had handed out the titanium amex and said "go forth and multiply my expenses".
What I saw was not ~ * ~ actual work ~ * ~. It wasn't "real stuff" either. What I witnessed was the most spectacular immolation of surplus I have ever seen. So much time, money and intelligence being pissed up against a wall in order to show the boss what a jolly good job you're doing.
When I tried to use it for actual work -- with, I repeat, utterly limitless amounts of tokens to burn -- it sucked balls. No matter how breathless the hype that this generation had finally cracked it, they all sucked. It produced flabby, buggy code by the gallon. It routinely fucked up and wasted my time. More than once I would wrestle with something for two or three days, give up, then bang a good solution in about an hour. Yes, I used rules and skills and .md files and and and and and and. Skill issue, you say? Well look, if hammers shot spikes through my hand one time in 20 then the skill issue is using the bloody doomhammer in the first place.
The actual work being done here is manic bullshitting and pissing in the village well. Shipping clanker clinker isn't productivity.
I work at Meta (though after next Wednesday, maybe not).
I signed the petition.
Am I hypocrite? I think another version of me would think so.
I signed up because nobody else would take me on by the time they offered me something. After having only 3 months of work out of 18 months, with savings depleted to zero, facing the prospect of losing health coverage and having to fall back on family, I took the deal.
Hate me if you like. But I have a 40-odd year head start on hating me, so I doubt you'll make any kind of dent.
------
In any case, pushing back, anyhow, anywhere, is better than nothing. Let's not get stuck in HN's favorite argumentative shortcut, the Nirvana Fallacy.
Hard to say, lots of things I guess. One was that I was never good at the current interview triad and needed to practice it a lot. Another was my resume, not impressive to a certain kind of hiring manager and recruiter.
Still another was that I asked blasphemous questions like "will I get to sleep?" and voiced controversial views like "teams focused on quality move faster".
The thing is that you sometimes get quite daft reasons back. One place said "you gave more examples from Pivotal than Shopify". Well yes, I was at Pivotal about thrice as long, that's how time works. I just let it slide.
There aren't enough things an executive can go to jail for.
Fines don't do anything to deter bad behavior. Either:
* The company pays
* They pay and the company mysteriously increases next year's comp / grants a "loan" / etc
* D&O insurer pays
In all three cases the money comes out of the shareholders' hides. It provides zero personal deterrence. The payoff matrix, as seen by a sociopath, makes it rational to always defect against the common good.
The only punishment that can really focus attention is physical imprisonment in a facility they can't choose.
SOX did this for financial reporting and gee shucks it turned out executives can follow the law after all!
I think it's totally fair, but I would assume that most Spring projects make significant DX tradeoffs compared to a full JS stack or serve an API rather than html.
1. Spring + Handlebars: You can either write the html template in a string loosing syntax highlighting and other LSP stuff, load it from a file loosing colocation.
2. Handlebars + webcomponents. They simply bundle all the web components into a single file, which breaks down when they get large and you don't need every component on every route.
3. Tailwind: Looking online you can get it working with spring boot, but the route chosen here is a script to run the cli, which again means every route ships every tailwind class used anywhere.
IMO a team like yours can either:
* Use LLMs, in which case you aren't "anti-AI".
* Not use LLMs currently, but the non-use is not due to following a principle, in which case you aren't "anti-AI".
* Not use LLMs and promise never to do so.
I'm happy you are trying something new. But you hurt yourself by engaging in something very old: disingenuity.
(edits for presentation and grammar)
reply