11–20 of 117 posts
I think this makes sense. I've seen many situations of large software projects where some bug is just open for months or even years and actually very easy to fix. In hindsight then, it was then a lot of missed value if the bug just lingered around for no good reason. If there was some tool that could just run in the background and randomly pop up a PR from time to time, then that would be cool. Good luck!
Interesting that your tagline is "spend less time writing, more time reviewing code" in the video. Developers already don't like reading the code, we even have a ubiquitous acronym for it. Writing is the fun part. In my experience, junior developers become mid level developers by writing code, by practicing, by building small features, by doing grunt work. If they wanted to use an AI to do those tasks for them, I wou…
The value prop is to hire fewer junior devs or even replace them. They don't mean to help junior devs. Also, I'm not sure if you'd enjoy writing code for those "grunt work". I'd love PRs that I can easily check correctness for and would get some small job done.
Also, here's another example of "grunt work". Sweep added a banner to our landing page, and I didn't touch my IDE at all. https://github.com/sweepai/landing-page/pull/226
Interesting that your tagline is "spend less time writing, more time reviewing code" in the video. Developers already don't like reading the code, we even have a ubiquitous acronym for it. Writing is the fun part. In my experience, junior developers become mid level developers by writing code, by practicing, by building small features, by doing grunt work. If they wanted to use an AI to do those tasks for them, I wou…
Wait for deluge of these PR generators to increase the commit count on GitHub.
(1) unless the PRs that they generate are garbage.
Interesting that your tagline is "spend less time writing, more time reviewing code" in the video. Developers already don't like reading the code, we even have a ubiquitous acronym for it. Writing is the fun part. In my experience, junior developers become mid level developers by writing code, by practicing, by building small features, by doing grunt work. If they wanted to use an AI to do those tasks for them, I wou…
The value prop is to hire fewer junior devs or even replace them. They don't mean to help junior devs. Also, I'm not sure if you'd enjoy writing code for those "grunt work". I'd love PRs that I can easily check correctness for and would get some small job done.
I’m not sure. If these AI tools become sophisticated enough it might be better experience to learn how to use them instead of doing the underlying work. Career-wise anyway.
Wait for deluge of these PR generators to increase the commit count on GitHub.
What you just said would be a good thing(1). That would mean that more bugs are getting fixed. (1) unless the PRs that they generate are garbage.
Definitely check out what we've been able to merge now though. The ceiling for tools like Sweep is incredibly high.
Interesting that your tagline is "spend less time writing, more time reviewing code" in the video. Developers already don't like reading the code, we even have a ubiquitous acronym for it. Writing is the fun part. In my experience, junior developers become mid level developers by writing code, by practicing, by building small features, by doing grunt work. If they wanted to use an AI to do those tasks for them, I wou…
Tools like this will be useful for small shops that don’t have a genuine need for a junior-to-senior pipeline. It’s going to create a (an even more?) two-tiered community of developers: one tier that knows the AI tools/tricks to produce stuff, and one that knows how to do it themselves. I don’t know which tier should be considered superior yet: time will tell.
The previous belief here would be the 10 person gets more work done, but that will change as AI developers like Sweep become more popular. There are a lot of additional benefits for small teams, like fewer meetings + faster decisions.
Earlier quoted context omitted.
The value prop is to hire fewer junior devs or even replace them. They don't mean to help junior devs. Also, I'm not sure if you'd enjoy writing code for those "grunt work". I'd love PRs that I can easily check correctness for and would get some small job done.
His point wasn’t about whether the “grunt work” is enjoyable or not, but that it is necessary work for juniors to do in order to gain experience. I’m not sure. If these AI tools become sophisticated enough it might be better experience to learn how to use them instead of doing the underlying work. Career-wise anyway.
We're also trying to make it easy to use Sweep. One outcome is an entirely simulated teammate, which is part of what we're doing with allowing you to review Sweep's PR
Earlier quoted context omitted.
Tools like this will be useful for small shops that don’t have a genuine need for a junior-to-senior pipeline. It’s going to create a (an even more?) two-tiered community of developers: one tier that knows the AI tools/tricks to produce stuff, and one that knows how to do it themselves. I don’t know which tier should be considered superior yet: time will tell.
Yep, small shops definitely benefit. Fewer people means each person already knows more of the codebase. For a 3 person team they might know >50% each, while for a 10 person team they might only know 10%. The previous belief here would be the 10 person gets more work done, but that will change as AI developers like Sweep become more popular. There are a lot of additional benefits for small teams, like fewer meetings +…
After all, if it doesn’t keep pace, the two-tier system I mentioned in my other comment will definitively be such that shops using these tools will not be as good as shops with a more traditional engineer skill development path.