The Tech Spec's Tech Spec - Jampa.dev
The purpose of this tech spec is to create a high-level document showing the importance of tech specs, we begin by starting a small introduction to show what the document will be about and then dive into sections.
Currently, there is not much awareness that tech specs have value in their intros that show the context behind the problem and put people on the same page.
Most companies do not have a formal process before creating software, and sometimes engineers are too distant from the context of the problem. They do not understand that the value added by software is not a "high-level distributed fail-safe queue of invoicing processing implementation with 3rd parties", but actually "have a way for people to buy our stuff".
Rushing without a plan generates rewrites as progress goes on, sometimes due to overengineering or new requirements. If we want to avoid those things we start doing things "by committee" where it takes a long time to deliver software due to setbacks creating plenty of meetings, going even slower.
Senior engineers might do fine without tech specs since they have more of a muscle memory, even so, they are not immune to missing their mark because wrong assumptions were made.
