2 ms·
Me: For this POC you've given me, I will do an old-fashioned HTTP form submit, no need for anything else. Architect: But it must have websockets! Me: Literall
by suzzer99 2y ago
Me: For this POC you've given me, I will do an old-fashioned HTTP form submit, no need for anything else.
Architect: But it must have websockets!
Me: Literally nothing in this POC needs XHR, much less websockets. It's a sequential buy flow with nothing else going on.
Architect: But it has to have websockets, I put them on the slide!
(Ok he didn't say the part about putting it on the slide, but it was pretty obvious that's what happened. Ultimately I caved of course and gave him completely unnecessary websockets.)
- deleted 2y ago[deleted]
- ticoombs 2y agoI always try and push back on those beliefs, about reasonings why they believe it will be faster or more efficient than some other solution. I've found , if you could type cast those people, they would be a tech architect who only uses "web scale" items. (Relevant link: https://www.youtube.com/watch?v=5GpOfwbFRcs https://www.youtube.com/watch?v=5GpOfwbFRcs )
- suzzer99 2y agoI call them Powerpoint architects.
- kigiri 2y agoMy strategy for this kind of situation is to avoid direct rejection. Instead of saying stuff like "it's unnescessary" or "you are wrong", I push for trying first without. I would say: > Once we have a working MVP without websockets we can talk again to think about using websocket. Most times, once something is working, they then stop to care, or we have other priorities then.