Global Feed Post Login
Replying to Avatar ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

yeah, i find when i ask junie to write code to change things it often just piles on more crap instead of changing stuff. very often i wind up rewriting parts of the code and if it fails to actually debug shit and make tests pass, after 3 times i just usually end up writing the code that was needed by hand. and then, of course, the tests pass because it was written the right way.

they can sometimes save a lot of work but sometimes make more work. learning how to avoid those potholes they fall into is a key part of making the work more efficient.

Avatar
Silberengel 5mo ago

Half of it is frequent commits, so that you can quickly revert and start a new chat. Never spend more than 5 minutes on one solution.

Reply to this note

Please Login to reply.

Discussion

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

yeah, absolutely, when i am writing the code, i might pack more into one commit, but generally best to avoid big commits. the bugs >_<... wasted quite a bit of time yesterday on big commits with new bugs or regressions.

Thread collapsed