21–30 of 117 posts
Great I think you made a good choice by interfacing directly to PRs. I'd like to see if I'm able to get my code coverage to 100% with this bot.
This is sarcasm, but I did have a VP who tracked commit frequency for a while. And people heard about it if they weren't commiting enough.
Earlier quoted context omitted.
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 +…
It remains to be seen whether that’s a benefit. This tool replaces experience junior engineers have needed to become better developers. Its future value is dependent strongly on the assumption that AI tools like this will evolve quickly enough to make using them more valuable than other experience. After all, if it doesn’t keep pace, the two-tier system I mentioned in my other comment will definitively be such that s…
Right now you could have some junior devs picking up work that Sweep can't handle in order to grow and learn, and eventually still become senior devs. Having a small team also helps with mentorship (more focused attention).
Finally! My VP of engineering keeps saying I'm not making enough github commits, this is the solution I've been waiting for! This is sarcasm, but I did have a VP who tracked commit frequency for a while. And people heard about it if they weren't commiting enough.
Tightly related to https://second.dev , also a YC company in the previous batch. Though Second is specializing its AI developers to doing code migrations.
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…
What if you have the opposite - a large number of relatively simple bugs waiting to get fixed and not enough junior devs do the work?
I think Sweep is a great idea and all of the additional developer capacity will be greedily soaked up by understaffed organisations.
How well it works will depend on how good those pull requests are. If it takes too much time of senior developers to review the pull requests then that is a problem.
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.
Sweep is targeted towards senior devs that can do two things. 1. review code quickly 2. articulate requirements well 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…
You're assuming that there is a large number of junior devs waiting for the opportunity to learn. What if you have the opposite - a large number of relatively simple bugs waiting to get fixed and not enough junior devs do the work? I think Sweep is a great idea and all of the additional developer capacity will be greedily soaked up by understaffed organisations. How well it works will depend on how good those pull re…
Earlier quoted context omitted.
Sweep is targeted towards senior devs that can do two things. 1. review code quickly 2. articulate requirements well 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
I would honestly just ignore that feedback. It's needlessly reductive and oxymoronic (coding is fun! But give juniors boring grunt work)