> As a 43yo developer, my advice is to push back on this. Make it clear from the first moment that it's their problem, not yours. Yeah you can both be positive

> As a 43yo developer, my advice is to push back on this. Make it clear from the first moment that it's their problem, not yours. Yeah you can both be positive about the fact that you will get to work on the project and deliver it. You can also make sure that they understand that the dates will almost certainly slip up front. And try to dodge anything that sounds like a promise for a deadline. The reality is that they probably don't care anywhere near as much as the tone of this article is making it sound. If they can get the deal signed and get something delivered in twice the time as was agreed to, and which isn't fully baked and may be more of a beta release, they'll be happy. And if they're not well then they've set you up for failure, and the worst thing they can do is fire you. As long as you understand that is their issue, that should relieve you of your burdens. Usually though if you come off as a "straight shooter" who is self confident then they'll remember the delivery and not the slipped schedule and bugs. What you don't want to be doing is projecting as much anxiety over deadlines and estimates as the article here does. Even if it sounds ominous that there are contractual deadlines, in reality usually neither side of the deal wants to blow up the contract if the schedule slips by 3 months (or whatever) as long it eventually gets delivered.