![]() (Or as often happens, the product manager shows a draft product spec to an engineering lead, who then writes a draft tech spec, which leads to a bit of horse-trading on features, SLAs, and assumptions. Ideally, a tech spec is based on a solid product spec. The tech spec is an excellent tool for this. It’s reasonable to set aside time for thinking through problems, planning, and communication. Provide documentation for future teams.Įxperienced engineers know that the majority of their time won’t be spent writing code.Consider operational and long-term support costs.Improve the accuracy of estimates and timelines.This helps to avoid wasting time on dead-end solutions or building the wrong thing. Remember: a software engineer’s job isn’t to write code but to solve problems.Ī tech spec forces you to think through complicated issues and to get everyone on the same page. The point of a tech spec is not to impede progress, but to take a brief step back and think things through. Some software engineers may regard writing specs as unnecessary process that gets in the way of the agile approach. ![]() ![]() Before writing code to solve all but the most trivial of software problems, a software engineer should write a tech spec. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |