March 30, 2026 at 12:00 am
Comments posted to this topic are about the item Prompt Requests
March 30, 2026 at 4:59 pm
I recommend watching the video on https://github.com/github/spec-kit.
I'm in two minds about the new world. On one hand, it encourages us to be more hands-off, more managerial. On the other side, I like the hands-on, and I never wanted to be a manager.
I've been astonished by what carefully structured prompts can achieve. My tip would be to ask Claude code to help you summarise the prompts you enter into a more efficient form to achieve the same thing.
March 30, 2026 at 7:16 pm
The end result of the demo video on the GitHub Spec-Kit, to me, is almost no different than what you can get with a million already made templates. He had an AI generate a static HTML web site. Sorry, but I’m not impressed by that.
Writing and documenting a specification is good, by all means. It is a requirement for us at my job. I don’t think you can, or should, do enterprise software development without them. It is a form of communication and documentation that is needed by many other people that are involved in the grand process, not just developers. So from that aspect, I would say GitHub Spec-Kit is good. But it should have been something you’ve already been doing.
To one of Steve’s points about the AI prompts, I’m considering including the prompts I write as part of the source code that I check in. And for source files that have been generated by the AI, marking them as such. That would be no different than what we have always done in the past with generated code. For example, in a .NET WinForms project, you have Form1.designer.cs, that is auto generated and marked as such. Why would the AI generated code be handled much differently?
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply