Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I find the people who end up with spaghetti code did so because they didn’t translate their normal processes over.

Being completely methodical about development really helps. obra/superpowers, for example, gets close but I think it overindexes on testing and doesn’t go far enough with design document templates, planning, code style guides, code reviews, and more.

Being methodical about it takes more time, but prevents a good bit of the tech debt.

Planning modes help, but they are similarly not methodical enough.

 help



That works until you make a plan/tests/etc, set the thing loose, and then when it has trouble it decides "actually the pragmatic thing would be [diverge from the plan/change the tests/etc]" and goes off the rails. I'm so frustrated by these things right now.

I have honestly not had that problem much. Being specific, concise, and strong with your prompts helps out a lot.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: