Tell me more about technical specifications. How were the specifications written, to what level, how were they coordinated with the customer, and how were they handed over to the developer?

Technical specifications (TS) were written considering the project goals and customer requirements. The process usually included several stages:

1. Requirements gathering: discussing business goals, functionality, and constraints with the customer.
2. Formalization: describing functional and non-functional requirements, including usage scenarios.
3. Detailing: the level of detail depended on the complexity of the task — from general descriptions to specific APIs and data formats.
4. Agreement: the TS was discussed with the customer, and revisions were made to clarify and eliminate ambiguities.
5. Handover to developers: the finished document was handed over to the development team, often with additional explanations and examples.

For example, for a new feature in a web application, the TS might include descriptions of user stories, interface requirements, response time constraints, and security considerations. This approach ensured a common understanding and reduced the risks of misunderstandings between the customer and the team.