Any software teams adopt coderabbit.ai or similar tools to their team workflow after adopting agentic assisted coding? I’m genuinely curious because I’ve noticed that agentic coding only gets you to the next bottleneck which is reviewing code.
1
Any software teams adopt coderabbit.ai or similar tools to their team workflow after adopting agentic assisted coding? I’m genuinely curious because I’ve noticed that agentic coding only gets you to the next bottleneck which is reviewing code.
Do you think software engineering should be a licensed profession? Or do you think it eventually will be? There is so much at stake at times with what we do. While I think software a decent enough job with regulation where it really matters (financial or self driving like development), I’m sure it’s not to the par of what it should be. To add, engineers have a pretty easy recovery should they act in bad faith.
How do you handle a PM who won't stop creeping the scope after sign-off? Seriously, every single sprint it’s the same story. We agree on the goals, lock it in, and then a few days later it's "just one more small thing." Except that "small thing" completely blows up the architecture and wrecks our timeline. How do you guys manage PMs who do this without completely destroying the working relationship?
I just graduated with my bachelor's in computer science at 26. I had a good GPA, but it took me a few extra years to get through the program for various personal reasons. My main concern right now is the age gap. Since I'm starting my career a few years behind the typical age group, I'm worried I might never catch up financially or professionally. Will companies view my age as a red flag for entry-level roles, and does starting later cap my ultimate career trajectory?
Valuable metrics are a quiet superpower. What are some you like to pay attention to? Here are some GH metrics that have helped me: 1. PR Cycle Time — how long from PR open to merge. If this spikes, something's blocking the team. 2. Review Load per engineer — who's doing 11 reviews while others do 1? 3. Stale PRs — PRs sitting unreviewed for 5+ days are a team health signal, not just a delivery signal. 4. Deploys per week — Teams that ship frequently have fewer big-bang releases and lower stress
I've just been made redundant with 15 years experience in web development & software engineering. I've had a pretty bumpy ride - I've never been given a promotion and I have done everything from bug fixes to line management and architecting & infrastructure so my CV is not looking great. Mostly due to being in the wrong place for too long (small companies, failing companies). Any advice on what I can do to beat the market, from people who have experienced this recently?
Not code rabbit specifically but cursor code reviews do find some bugs and we get claude to auto resolve it. It lightens the load but not too much. Prevention is better than the cure tbh... scoping your task before coding it up makes it more likely to have a smaller PR which in turn makes it quicker to review and resolve.
I figured, so has your ram adopted both?