[tsunamifury]

I’m sorry but in a practical corp environment this is a fast track to be fired. You become the person constantly in the room enumerating edge case doubts that aren’t often even relevant. You map the blockers vs the opportunities and end up focusing the team on them.

The goal is to avoid blockers, not enumerate them uselessly.

Can it be done? Yea? Sure ok then let’s figure it out. The million ways it can’t aren’t relevant.

[albatross13]

I love this line of thinking, it's how old companies I worked with developed entire rest APIs using only AWS Lambda and after sinking tens of millions into it they abandoned it :)

CAN IT BE DONE? OH YEAH!

[robofanatic]

at least now they know that it can't be done

[tsunamifury]

But this is the classic engineering mistake in how they communicate. They replace “why should we do this” with “we can’t do this” and it leads to the same old stupid conversations with eng who are probably pretty smart but have no self awareness of their communication failures