TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Autonomy vs. QC

1 pointsby stocktechabout 7 years ago
I&#x27;m a first time team lead and I&#x27;m struggling to come up with a good process for my team. The nature of the work is very independent: each developer is responsible for a project from requirements gathering to deployment. There&#x27;s only 2 of us right now, but we&#x27;ll be growing soon so I want to iron this out.<p>On a project basis, I&#x27;ve found a good balance of being involved with specs. I&#x27;m struggling to find a way to be involved with the code itself though. There needs to be some form of code quality control. At the same time, I need a way to teach technical skills to my new hires.<p>I&#x27;ve thought about code reviews, but with 1 dev per project, that could get personal and wouldn&#x27;t identify bigger problems until it&#x27;s too late. If I scheduled code reviews weekly, that seems a little micromanagement to me, but it might be necessary.<p>There is a subtext of under performance and trying to correct it, but I feel like once I put a process in place, the path to improvement will be easier to see.<p>Any thoughts or experience?

no comments

no comments