3 ms·
1. Build a functional test system, and write a big suite of tests which ensure preservation of behavior. Make it easy to run and see the results. 2. Slowly sta
by caprock 4y ago
1. Build a functional test system, and write a big suite of tests which ensure preservation of behavior. Make it easy to run and see the results.
2. Slowly start extracting code and making small functions. Document like crazy in the code as you learn. Keep the single file or close to it, and don't worry about frameworks yet.
3. Introduce unit tests with each new function if you can.
After all that is done, make a plan for next steps (framework, practices, replace tech etc).
Along the way, take the jr backend engineer under your wing, explain everything, and ensure they are a strong ally.
Call me crazy, but that project sounds like fun.
- peteradio 4y ago> Build a functional test system, and write a big suite of tests which ensure preservation of behavior. Make it easy to run and see the results. Keep it to yourself and don't let anyone know why you are so effective. Demand a raise early once you are sure of your value. Edit: why not? Clearly this is a huge value that would be wholly unappreciated without leveraging it yourself.
- bckr 4y agoOP is leading a team, not hiding in a churning out code. The "secret superpower" strategy doesn't work here.
- peteradio 4y agoWhere does OP say they are team lead? They sound like a junior.
- bckr 4y ago> I have to find a strategy to fix this development team Clearly responsible for team outcomes > without managing them directly Not a people manager. Most likely a tech lead or a technical project manager
- peteradio 4y agoSounds like something they'd explicitly mention. I took it to mean they were a young gun go-getter.