|
|
|
|
|
by thegandhi
1403 days ago
|
|
One of the biggest problems with dev environments is maintenance just like documentation. As a dev, when I am working on my local environment, if something breaks, I usually end up finding some hack to fix it and move on with my feature/assigned task. Most devs leave it to the "new guy" who is onboarding.
I also think having templates as code might be a way to alleviate that issue to certain extent. |
|
This is on the money. The challenge though is still giving engineers flexibility/freedom. Our approach is to have templates that engineers can use but they can fork it and play around with it, make a snapshot of that fork and share it, etc. Its a fine balance though and every team has to figure out what works best for them