Live data from Hacker News

Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

github.com

81–90 of 278 posts

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#81
post #74

I use openspec and love it. I’m doing 5-7x with close to 100% of code AI generated, and shipping to production multiple times a day. I work on a large sass app with hundreds of customers. Wrote something here: https://zarar.dev/spec-driven-development-from-vibe-coding-t...

>large sass app

>hundreds of customers

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#82
I've tried several of these sorts of things, and I keep coming away with the feeling that they are a lot of ceremony and complication for not much value. I appreciate that people are experimenting with how to work with AI and get actual value, but I think pretty much all of these approaches are adding complexity without much, or often any, gain.

That's not a reason to stop trying. This is the iterative process of figuring out what works.

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#83

Earlier quoted context omitted.

Code is a cost. It seems everyone's forgotten. Saying "I generated 250k lines" is like saying "I used 2500 gallons of gas". Cool, nice expense, but where did you get? Because it it's three miles, you're just burning money. 250k lines is roughly SQLite or Redis in project size. Do you have SQLite-maintaining money? Did you get as far as Redis did in outcomes?

Openclaw was mostly build by AI. It had 400K lines of code.

You didn’t answer what does you 250k lines do? How much money does it make? How many users does it have?

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#84
I tried it once; it was incredibly verbose, generating an insane amount of files. I stopped using it because I was worried it would not be possible to rapidly, cheaply, and robustly update things as interaction with users generated new requirements.

The best way I have today is to start with a project requirements document and then ask for a step-by-step implementation plan, and then go do the thing at each step but only after I greenlight the strategy of the current step. I also specify minimal, modular, and functional stateless code.

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#85
"I am a super productive person that just wants to get shit done"

Looked at profile, hasn't done or published anything interesting other than promoting products to "get stuff done"

This is like the TODO list book gurus writing about productivity

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#86
How come we have all these benchmarks for models, but none whatsoever for harnesses / whatever you'd call this? While I understand assigning "scores" is more nuanced, I'd love to see some website that has a catalog of prompts and outputs as produced with a different configuration of model+harness in a single attepmt

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#87
There should be an "Examples" section in projects like this one to show what has actually been made using it. I scrolled to the end and was really expecting an example the way it's being advertised.

If it was game engine or new web framework for example there would be demos or example projects linked somewhere.

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#88

Earlier quoted context omitted.

GSD and superpowers aren't CLI wrappers?

It's a cli wrapper. Don't know how you could say it wasn't. edit: GSD is a cli wrapper, Superpowers not so much. Both are over-engineered for an easy problem IMHO.

No it's not. It's using Skills and Agents and runs always inside of Claude Code, Gemini CLI etc...

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#89

"I am a super productive person that just wants to get shit done" Looked at profile, hasn't done or published anything interesting other than promoting products to "get stuff done" This is like the TODO list book gurus writing about productivity

[dead]

Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

#90
post #78

Earlier quoted context omitted.

It's a cli wrapper. Don't know how you could say it wasn't. edit: GSD is a cli wrapper, Superpowers not so much. Both are over-engineered for an easy problem IMHO.

Both are dramatically over-engineered. & That's okay. I find them to be products of an industry reconciling how to really work with AI as well as optimize workflows around it. Similar to Gastown et al. Otherwise, if you can own your own thinking, orchestrating, and steering of agents, you're in a more mature place.

I think that's fair, if they were created today I'm sure the creators would make different decisions, a penalty of getting there first.
Post reply on HN