I enjoyed the blog post. I always like seeing small projects like this as a small act of rebellion against a host of subscription services. An interesting take that I definitely disagree with. I...
I enjoyed the blog post. I always like seeing small projects like this as a small act of rebellion against a host of subscription services.
If an LLM wrote every line of your code but you've reviewed, tested and understood it all, that's not vibe coding in my book - that's using an LLM as a typing assistant.
An interesting take that I definitely disagree with. I could write a substantial bit about why I disagree with it, but I kind of want to see what people think if I just provide the following.
If an LLM wrote every line of your documentation and instructions but you've reviewed, tested and understood it all, that's using an LLM as a typing assistant.
If an LLM wrote every line of your blog post but you've reviewed and understood it all, that's using an LLM as an typing assistant.
If generative AI drew every part of your profile picture but you've reviewed it all, that's using generative AI as a pixel coloring assistant.
The only one I'd personally agree from that list is the documentation one. LLMs let you skip the critical thinking part of problem solving, which is a lot more than being a typing assistant. The...
The only one I'd personally agree from that list is the documentation one. LLMs let you skip the critical thinking part of problem solving, which is a lot more than being a typing assistant. The reason I don't really find this to be an issue with writing documentation, at least the kinds of documentation I'm envisioning, is that the documentation is a derivative work of what it is documenting (ex. API descriptions and examples).
Hmm one part I disagree with is that the code is a means to an end. Code produces a product. In your metaphors, the LLM is skipping the middle part and just creating the product.
Hmm one part I disagree with is that the code is a means to an end. Code produces a product. In your metaphors, the LLM is skipping the middle part and just creating the product.
I enjoyed the blog post. I always like seeing small projects like this as a small act of rebellion against a host of subscription services.
An interesting take that I definitely disagree with. I could write a substantial bit about why I disagree with it, but I kind of want to see what people think if I just provide the following.
The only one I'd personally agree from that list is the documentation one. LLMs let you skip the critical thinking part of problem solving, which is a lot more than being a typing assistant. The reason I don't really find this to be an issue with writing documentation, at least the kinds of documentation I'm envisioning, is that the documentation is a derivative work of what it is documenting (ex. API descriptions and examples).
Hmm one part I disagree with is that the code is a means to an end. Code produces a product. In your metaphors, the LLM is skipping the middle part and just creating the product.