Docs for FI.
Devs are responsible for Trello management. Usual columns:
- Milestones (client or internal due dates, no feature/bug tickets here)
- Assets (SOWs, wireframes, design specs, no feature/bug tickets here)
- Pending Merge
All development + meeting time should be tracked in Harvest.
It's common for juniors to shortchange time tracked due to concern that they're spending more time than they "should." This is wrong. Track all time.
FI follows a git-flow-esque branching strategy.
Master is production code. Features and bugs map directly to Trello cards and should be tackled in branches following this convention:
So for Trello card 420—which describes a new feature, full text search—you would create a branch named:
Juniors should not push directly to master without submitting a pull request for their feature or bug branch and its acceptance or merge by the lead for the project.
maintaining code quality
The dev lead for a project is responsible for its code quality. Sometimes the lead will be the only developer. Sometimes they'll be developing alongside another developer. Sometimes their only relationship with the code base will be through peer reviews and pull requests. But it's still their baby.
A useful internal place for questions without answers yet. This prevents DMs to your dev lead from going unnoticed.
FI-wide peer reviews happen for an hour, once-a-week. You can find the current schedule here.
Some peer review strategies:
- Code author brings a problem or two to the session, explains how they solved the problem, and why it doesn't quite feel right.
- Author presents his or her Worst Code™ for review.
- Reviewer checks week's commits for interesting or confusing solutions. Discuss.
If you're stuck on something for twenty minutes, ask for help. It's simple.