Earlier quoted context omitted.
> If you don't do that you'll run into the same problems as you would if you hire a contractor to build your codebase without understanding what they did for you. I guess the difference is now that the contractor is cheap or free (because it’s a LLM), whereas in the old days you’d either hire a person to do the work and not understand or pick up a book and figure it out yourself (or go to school, or whatever). Figuri…
I have a feeling that if there was not a healthy amount of competition in the space, the prices would start to trend towards the cost of human work.
I Spent 24 Hours with GitHub Copilot Workspaces
71–76 of 76 posts
Re: I Spent 24 Hours with GitHub Copilot Workspaces
#72Hmmm, wonder if there's cheaply sourced labour of the human variety in that loop then?
Re: I Spent 24 Hours with GitHub Copilot Workspaces
#73Earlier quoted context omitted.
> but if you try that you'll find yourself supplying an enormous amount of context you didn't expect to have to communicate. Context not even directly related to the code at hand, but about the broader business or industry, past lessons learned, something the CEO said to you last week about the feature, etc. Basically you go from programmer to product manager, except you also get to micromanage a non-sentient program…
What prevents an AI agent from becoming the product manager as well, and communicating with you (the customer) to clarify requirements?
Re: I Spent 24 Hours with GitHub Copilot Workspaces
#74To me the effect seems similar to going from assembly language to C or from C to Java or Visual Basic. It's a new level of abstraction that saves massive amounts of time.
I think the amount of work for software developers will increase just like it did back then. Many software projects are never started because they will be too expensive. If they can be done by half the number of people in half the time using AI tools, they might get a "go" instead.
Re: I Spent 24 Hours with GitHub Copilot Workspaces
#75When reading posts such as these, it occurs to me that AI is increasing the rate / lowering the bar for developers to make the jump to leader / architect. Look at the lessons that the author has learned here: * More specificity == better * The importance of clear bulleted delivery items / criteria-for-success * Unspecified details around a general goal is a ripe area for disappointment All of these are things that a…
This isn’t architect level planning. Even a junior developer should be able to work from vague requirements and build a mental like that.