การเขียนโค้ดโดยไม่มี AI: การปฏิวัติวิธีการทำงานรูปแบบใหม่(isaaclyman.com)
isaaclyman.com
Coding without AI: a revolutionary new way to work
https://isaaclyman.com/blog/posts/coding-without-ai/
6 comments
You are correct, it was flagged almost immediately and I'm unsure why (though my conspiratorial brain kicked in attempting to turn up answers). In any case and perhaps as a consequence I feel it hasn't gotten the traction it should have. FYI I submitted the article from my own account after seeing it flagged.
I would like to point out the exceptional quality of the writing itself which forced me to peruse other posts on the blog.
I would like to point out the exceptional quality of the writing itself which forced me to peruse other posts on the blog.
I went back to doing this for my personal projects and guess what, I think its faster too.
I find the idea of understanding the work you do absolutely revolutionary. I hope this becomes a trend that gains traction.
I wish it could be applied to other fields. Imagine, for instance, books? or even maybe blog posts? written without AI.
I'm going to ask Claude to write me a skill I can follow. Maybe I should start experimenting with a tweet or an email, as a proof of concept.
I'm going to ask Claude to write me a skill I can follow. Maybe I should start experimenting with a tweet or an email, as a proof of concept.
Amazing. I feel like you could write entire books about this new way. Think of the fame and fortune that awaits such visionaries! Surely this is the way of the future. The next "Andrej Karpathy", "Boris Cherny", "Peter Steinberger" are just waiting to be discovered.
1. It is the most refreshing article I've read through the HN homepage lately. Not a single em-dash, no "not X. Just Y", none of the other more subtle AI tells. I felt like reading the thoughts of an actual person, not reading an expanded version of a person's core idea.
2. After writing 11 books, I'd been thinking I was basically done with writing, this blog post made me change my mind.
3. I found this part interesting:
> It turns out coding just isn’t much of a bottleneck. What takes most of my time is everything else: figuring out the requirements, resolving ambiguity, waiting for feedback, testing and validating, coordinating with other teams, going to meetings, project planning, and so on. It’s the people stuff that’s slow, not the computer stuff.
It seems like all the talk recently has been about automating all of this "other stuff" now that the coding/writing/image generation/etc part is "handled" by models. What'd be left then?