In those cases the correct answer is "Dunno, but I'll have an estimate by tomorrow after I do some prototyping".
Then you do the janky prototype and try to extrapolate how long will it take to finish it properly. Then double that and be the miracle worker who delivers in half the time :)
But do not under any circumstances be tempted to demonstrate said janky prototype, unless you want to get re-tasked while said janky prototype gets merged into the build because 'schedule' .. and then be haunted by the damned thing for at least the next three years
Yep, janky needs to look janky and be slow and break. Otherwise they'll think it already works :D
That's also why you always keep the UI on par with the backend as far as completion goes. If the UI looks complete -> people think the backend is complete too.
I know exactly what you're talking about. The first rule of the meeting is "shut up" and the second rule is "keep silent" and "watch your mouth". I don't know why it is so hard to stick to those simple rules when the solution to the engineering problem seems so obvious.
Then you do the janky prototype and try to extrapolate how long will it take to finish it properly. Then double that and be the miracle worker who delivers in half the time :)