Things We Don’t Do in Our Team

Photo by Anwaar Ali on Unsplash

We don’t have long-lived branches other than master

We don’t assign developers to repositories

We don’t have User Acceptance Testing (UAT)

We don’t blame

We don’t write a wall of text on cards

We don’t do hours long sprint planning

We don’t tell the team what to do

We don’t ignore technical debt

We also don’t over-bake our technical solutions

We don’t split people into Operation and Innovation

--

--

--

Software Engineer | Technical Lead | Engineering Manager jamiewen00.gitbook.io/tech-lead-handbook/

Love podcasts or audiobooks? Learn on the go with our new app.

Did Covid-19 kill the open-concept office?

How to Weaponize Impostor Syndrome

What Are The Signs Your Boss Is Threatened By You?

signs your boss is threatened by you.

Relentless, but not Reckless

Tips for My Retail Training: 5 Ways to Get the Most Out of It — HALIGHT

What’s coming up next for BeNext?

Cohort Based Certification Program for HR Professionals

How To Search For A Sales Gig You’ll Love (And Rock At)

Meet Disorder, Your New Best Friend

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jamie Wen

Jamie Wen

Software Engineer | Technical Lead | Engineering Manager jamiewen00.gitbook.io/tech-lead-handbook/

More from Medium

Managing the software development team

What Ugly Pull Requests Look Like

Don’t just be a heads-down coder

The Daily StandUp Kick