- 127comments
- 63comments
- 7comments
- 132comments
- 10comments
- 793comments
- 130comments
- 1014comments
- 2comments
- 46comments
- 34comments
- —discuss
- 2comments
- 107comments
- 26comments
- 22comments
- 247comments
- 411comments
- 10comments
- 221comments
- 6comments
- 12comments
- 529comments
- 61comments
- 167comments
- 519comments
- 153comments
- 31comments
- 112comments
- 396comments
Seems more like AI-in-the-loop more than AI-native.
I feel like this post didn't teach me anything I didn't already know or have an intuition about.
I think that’s because across experience levels there really isn’t much to teach regarding “how to use AI”.
The only grind is still just do you know the subject matter, tools and frameworks, etc. because that’s the knowledge that lets you look at the output and say “this is fine” or “this is absolutely the worst implementation I’ve ever seen try again but do X”.
In my experience adding on multiple layers of controls etc aside from basic skills is essentially as useful as a ring of salt and a live offering.
My workflow these days is basically ultracode + PRs. I do control the features that go but barely need to check the code due to the amount of checks: lint, TS, Local AI visual Model for visual check for screen frame comparison (Mac M5 48GB mem), Pixel/Screenshot regression test for basic UI, code coverage/c8 to avoid trash code without tests, etc. etc.
Essentially the tests are just for the AI to remember what they did (as in the description + break if they change smth unintentionally).
Ai native is only a term for the present moment. There is still skill in using ai. We are fast approaching where you ask the ai, and it does the task, there is no wrangling it
So what does it look like? This is a load of booster talk tuned to reel in the devs who appreciate *****.
I'm starting to notice AI power users communicating in a shorthand tech-speak I find unintelligible. I genuinely cannot follow the individual points in this article or what the overall arc is.
Is this something that was already part of web dev or is it new?
I didn't find her article hard to understand. Maybe you have a reading comprehension issue?
It's not the users doing the communication, it's their AIs.
And you, as a human, were not meant to read it - you're supposed to instead feed it back into your own AI agent and have it create a groundbreaking new AI startup based on it. Give it your Cloudflare credentials, sit back, sip a latte, and within an hour or two you'll have a beautiful, fully functional website, complete with fancy fonts, 30 different "No X. No Y. Just Z" taglines, and a $20 monthly subscription, ready to show off to investors. You'll be a highly successful entrepreneur by the end of the week.
Doing drugs sounds both more rewarding and productive.
I find wine helps. Lots of wine.
Looking for a job? This sounds like personal marketing speech rather than a blog worth reading, no new insights no nothing
no shit, it's some medium backed shit website.
Wish i could filter ALL of these, not just those with the medium website
Getting a 502 error. I had to come to the comments to check whether that was the joke.
13,000 tests. That tells you everything you need to know. It doesn't matter how experienced you say you are, if AI is doing all the work including writing and running tests because I know no human is actually reviewing these. I've recently found tests written by Fable that don't actually do anything in a very large codebase. My point is not to advocate for doing any of this manually, but to highlight one of the problems brought about by pumping out so much code.
I hate to sound cynical, but I don't know if bragging about being AI-native is something any of us should be doing. We're really just pulling a lever on a slot machine and crossing our fingers.