4 ms·
Sometimes I have this dream vision of a software company were the only management tool is a huge board of git commits with clear commit messages. The small team
by kriro 10y ago
Sometimes I have this dream vision of a software company were the only management tool is a huge board of git commits with clear commit messages. The small team meets at the beginning to set the goal and timeline. All code gets reviewed by multiple people and every programmer knows the rough project status by looking at the git-board and is actually eager to try the product each morning since everything is CIed. The only time meetings are called is when someone realizes they are in over their head and needs help or if they feel they'll need longer than they thought.
Just a big newsfeed of git commits and everyone can magically understand how it all works together. You stroll into the office and look at the board and see the 24 commits since you left and all the changes immediately inform how the product has changed in your head. You play around with the product in awe, brew a cup of coffee and read over the great new sorting algorithm that john committed a couple of days ago, smile, crack knuckles, ready to rock and roll writing whatever you write.
- discordianfish 10y agoI believe this works very well and is what I would propose for a small team (5-8 engineers) working on related things (let say your typical react+node+mongodb stack). I don't think this scales beyond that. Even with a small team it's not realistic to expect your engineer to understand both the commits in the iOS frontend, the golang backend and the AWS terraform templates. But your comment makes it clear that we should define where such workflow should be applied. One size won't fit all, especially on this regard.