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.
Frontend Developer We are seeking a Frontend Developer to build responsive, user-friendly web applications and deliver exceptional user experiences /n Responsibilities Develop and maintain web applications using HTML, CSS, JavaScript, and modern frameworks (React, Angular, or Vue). Requirements - 2+ years of frontend development experience. - Strong knowledge of HTML, CSS, JavaScript, and TypeScript.
What’s your take on oversized Pull Requests? Knowing that it’s the norm of AI assisted development, automation hasn’t still caught up with humans reviewing the changes.. I would and still reject overly large PRs for reasons outside of testing and fixtures.
I previously worked at a credit union where software developer salaries were way under market ($50k–$60k), prompting me to leave and triple my income. I later discovered that the chief of technology hired a former developer and close friend as a remote, part-time contractor at a triple-digit hourly rate. This individual maintains a separate full-time job and works completely flexible hours, 20-40 hours. This feels like blatant cronyism. Is there any recourse?
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?