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

currently AI focus is very narrow. I treat it like a junior dev where it can repeat structure it's given and then I basically "approve" it or I use it like a super robust autocomplete where it knows what I'm writing next like 80% of the time. also good for bouncing ideas to see if there's something someone else had done similarly.

there is no way in hell I would tell it to "generate X feature" or "fix X bug" wholesale. half the time it is just dead wrong in it's approach and it's more time consuming to grok what it did exactly and then either 1) suggest an alternate approach and 2) fix what it did wrong.

like i get it, in the end if it generates the right code and it works then most people will call it a day. but longevity is in being able to understand and maintain your codebase and at this point i can't trust it to do that. it some sense it reminds me of (and still reminds me of) those wysiwyg site builders where sure, your output might be fine for 90% of those cases like a simple landing page but the code underneath is a big pile of shit. good luck if you need to break out of that box at any point.

i guess all to say AI will start replacing low level static site facing stuff. for instance if you're selling cookie cutter WP themes i'd be worried at some point. for everything else it's a non-factor right now.



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

Search: