3 ms·
Developers are lazy. They don't want to write technical specifications. They can barely be bothered to write a README with the design or make an ADR. They can't
by 0xbadcafebee 5y ago
Developers are lazy. They don't want to write technical specifications. They can barely be bothered to write a README with the design or make an ADR. They can't even be bothered to write tests half the time.
It's also hard to explain to your bosses that you won't have any actual code for 6 months.
Experienced lead devs will use it on projects where accuracy and reliability is paramount. Otherwise it's just seen as yak shaving.
- hwayne 5y agoHow often do you floss?
- Jtsummers 5y ago> It's also hard to explain to your bosses that you won't have any actual code for 6 months. Formal methods don't have to mean "stop the world and do nothing else". They're tools for thinking through (often) harder problems in a systematic way. They're applicable through every stage of development. During initial design and requirements gathering (where I've seen and used other methods, like describing systems via state chart and state machine models), during development to clarify some confusing portion of the system, in analysis of problems (like the ones I described in my other post), and so on.
- Zababa 5y ago> Developers are lazy. They don't want to write technical specifications. They can barely be bothered to write a README with the design or make an ADR. They can't even be bothered to write tests half the time. I would be bothered if I was incentivized to write documentation instead of shipping features.