re: Fixing your Documentation Problem VIEW POST


I typically meet with my team to plan our solutions and then we take notes of some.l decisions like interfaces, patterns, data structures and such. I'll try to write it down in a cohesive way next time and push as documentation. Sounds good.


That's already better than what most do, so you have a head start! There's always more you could be doing of course, it's just that making it a required step in the process will keep you more consistent at it. Thanks for sharing your experience!

code of conduct - report abuse