&gt; And when the manager says &quot;deadline is next week&quot;, and the new and EXPERIMENTAL and UNSTABLE (gasp) feature is the only way to get it done, you use it.<p>I fail to see how a manager&#x27;s failure to understand that you <i>cannot</i> rely on features that are subject to <i>breaking</i> change or removal at <i>any</i> time, without warning is Google&#x27;s, Microsoft&#x27;s or Mozilla&#x27;s problem.<p>&gt; Now, good luck getting permission to go back and clean up technical debt.<p>If your site breaks because the experimental feature that your manager forced you to use was radically changed or removed -as per the widely advertised, well-known policy regarding experimental features-, and your manager doesn&#x27;t give you permission to fix the mess he forced you into, you -as the programmer- have nothing to worry about. This is clearly a failure of management. :)<p>Will that stop this manager from yelling at you? Probably not. Will this stop you from getting fired? Maybe not. But, seriously: If you get fired because your manager ignored your expert recommendation that his plan would lead to disaster, and -a little while later- his plan leads to disaster, you were working for a <i>very</i> unreasonable boss. It would only be a matter of time until you were fired for some other equally stupid reason.<p>If -on the other hand- you commit to doing something that you later find out is not possible, and you <i>don&#x27;t</i> own up to your mistake, whatever fallout comes from the stupid things you do to cover up your mistake is your own damn fault.