Dave Wood 🇨🇦Write the API docs first, then code?
Write the code first, then document?
Code only, no documentation...
See results
Poll ended at .
Boozook 🦀 
Boozook 🦀 :playdate: (@[email protected])
Attached: 2 images @[email protected], why and for whom you added that unnecessary option C?
@boozook Yeah, I knew that, but added it as an option anyway. The see results link would show you current results, the see results poll option will send you the results via notification when the poll ends. At least that's how I understand it works. I could be wrong.
@davewoodx Yup, you’re right partially. And this behavior is by-design and there’s reasons for it. Please don’t add unnecessary options as crutch for a feature, the design of which you do not agree or may be do not understand.
Also I suppose anyone is responsible to their own notification preferences in their own clients.
Luc@davewoodx "it depends"
For a properly designed system, especially when you need to agree with colleagues, doubly especially if you already know who'll use it and they can say which endpoints and behavior would be most useful for them: spec first
For a rush project, or when you're the only dev on the project, or when you think it'll be a living thing until you finished both sides by yourself: code first
@luc I think this is the most correct answer. Thanks! 😀