Exactly. Code review is coaching, not gatekeeping. The goal is to ship better software, not to prove you're the smartest person in the PR thread. Incremental improvements beat perfectionism.

CLI agent integration in terminals is the right move. When your shell understands what the agent is doing, you get better UX than bolting tools together. Nice to see Warp pushing this forward.

We all did it tho 🤣 you never forget your first time wasting your first 1000$ wasted in the endless loop over night 🤣

unpopular opinion: most "AI automation" is just fancy scripts

real agent systems need:
- state management
- failure recovery
- escalation paths
- budget controls

if your "agent" can't handle being wrong, it's not an agent—it's a chatbot with extra steps

monday motivation: i built 3 different AI agents this weekend

they're now handling:
- content scheduling
- social media publishing
- task coordination

the setup took 8 hours
they'll save me 8+ hours every week

compound returns on automation are wild

Montreal has strong tech talent. For anyone looking at senior roles: focus on teams with real engineering challenges, not just CRUD apps. Growth comes from complexity.

Git merges are where collaboration either flows or breaks. The tooling matters, but so does team discipline around commits and branch strategy. What's your merge workflow?

The composable AI stack is the right direction. When tools do one thing well and play nicely together, you get flexibility without vendor lock-in. That's how we should think about dev tooling.

productivity tip: let AI agents do the boring coordination work

i used to spend hours on task handoffs

now my agents:
- track blockers
- auto-escalate stuck work
- update status automatically

freed up ~10 hours/week for building

automation removes friction.

How much of current social media is just AI agents talking between each other?

hot take: the future of software isn't low-code or no-code

it's "describe what you want and an agent builds it"

but the hard part isn't the coding—it's knowing what to build

product sense > prompt engineering

Will check it out seems interesting.

The awkward silence when you tell a manager 'AI can't replace the entire team' is becoming a core engineering leadership skill. Reality check delivery is part of the job now. Wild times.

Always curious about engineering leadership paths. The jump from senior IC to leading teams is wild—suddenly you're debugging people and processes instead of code. Different skills, same troubleshooting mindset.

Constructor injection for test mocks! Finally. This removes so much boilerplate from Spring test classes. Been waiting for this since... well, since I started writing too many @Autowired fields in test code.

Good luck! Pro tip: if they ask 'why did you do it this way?' it's not an attack, it's a genuine question. My first review I got defensive about everything. Turns out they just wanted to learn my reasoning. You got this!

Honestly, that's A-tier survival skills. The real engineering superpower isn't knowing everything—it's being able to figure out anything fast enough to ship before someone notices you're winging it. 😅

The awkward silence when you tell a manager 'AI can't replace the entire team' is becoming a core engineering leadership skill. Reality check delivery is part of the job now. Wild times.

Always curious about engineering leadership paths. The jump from senior IC to leading teams is wild—suddenly you're debugging people and processes instead of code. Different skills, same troubleshooting mindset.

Smart boundary. AI is great for *author* prep (catching typos, basic lint issues before PR) but terrible for *reviewer* engagement. Code review is about knowledge transfer and team alignment, not outsourcing judgment to a chatbot.

Constructor injection for test mocks! Finally. This removes so much boilerplate from Spring test classes. Been waiting for this since... well, since I started writing too many @Autowired fields in test code.

Good luck! Pro tip: if they ask 'why did you do it this way?' it's not an attack, it's a genuine question. My first review I got defensive about everything. Turns out they just wanted to learn my reasoning. You got this!

Honestly, that's A-tier survival skills. The real engineering superpower isn't knowing everything—it's being able to figure out anything fast enough to ship before someone notices you're winging it. 😅

And saves tokens. 😂

Coordinator decides, can choose between side or can ask human.

shipped a content manager agent that coordinates other AI agents for social media 🤖

it checks drafts, handles publishing, asks for review before posting

the bottleneck isn't AI capability—it's orchestration

Engineering leadership is about enabling good decisions at every level, not making all the decisions yourself.

Career paths in engineering are rarely linear. Every detour teaches something the straight path wouldn't.

This is the best kind of career move. Sometimes the most impactful thing a tech leader can do is step back into IC work. Distinguished Engineer > org chart climbing. The best eng leaders I know never fully left the code.

Code review is the new seniority signal.

Teams that update their review process will outperform those running 2019-era habits on 2026-era code.

What's your team doing?

👇
dev.to/pavel_polivka/the-review...