▲ | james2doyle 9 hours ago | ||||||||||||||||||||||
Totally agree. I use for chores (generate an initial README, document the changes from this diff, summarize this release, scaffold out a new $LANG/$FRAMEWORK project) that are well understood. I have also been using it to work in languages that I can/have written in the past but are out of practice with (python) but I’m still babysitting it. I recently used it to write a Sublime Text plugin for me and forked a Chrome extension and added a bunch of features to. Both open source and pretty trivial projects. However, I rarely use it to write code for me in client projects. I need to know and understand everything going out that we are getting paid for. | |||||||||||||||||||||||
▲ | bdangubic 8 hours ago | parent [-] | ||||||||||||||||||||||
> I need to know and understand everything going out that we are getting paid for. what is preventing you from this even if you are not the one typing it up? you can actually understand more when you remove the burden of typing, keep asking questions, iterate on the code, do code review, security review, performance review… if done “right” you can end up not only understanding better but learning a bunch of stuff you didn’t know aling the way | |||||||||||||||||||||||
|