<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>arnvald</author><text>Most deadlines in my career so far were arbitrary. Sure, some deadlines were driven by fixed events, for example Christmas promotion has to be launched before Christmas.&lt;p&gt;But in most cases when I asked managers about the reason behind the deadline, the answer was something like &amp;quot;oh,I promised this team&amp;#x2F;director we&amp;#x27;ll do it by then&amp;quot;. When I dug deeper to see what happens if we miss the deadline, it appeared the said team would be just fine, there were no real life consequences, just that they wanted to finish their part of work by certain time, and they depended on us.&lt;p&gt;I&amp;#x27;m not saying deadlines are useless, but they&amp;#x27;re very often driven by some arbitrary promises made by managers before even consulting developers about the complexity of work to be done.</text><parent_chain><item><author>PragmaticPulp</author><text>It’s always fascinating to read these anti-deadline articles that assume deadlines are arbitrary things that exist for no reason.&lt;p&gt;That might be moderately true for, say, someone developing a new app feature that gets shipped to users who aren’t expecting it. However, it’s not true at all when the software development output is a gating feature for real-world contractual obligations and other such business drivers. In that case, target dates must be carefully forecasted and estimates must be performed with great care and detain. This doesn’t guarantee that a target date will be hit, of course, but it’s not impossible to produce estimates that are reasonable accurate a large percentage of the time.&lt;p&gt;Estimation, planning, and progress tracking are difficult skills that must be learned, but they’re not impossible. I suspect many of the developers who believe that target dates are always arbitrary, pointless, and impossible to estimate have mostly worked in big cash-rich environments where it didn’t really matter when a feature shipped. If you go to the other end of the spectrum and talk to engineers who work in industries where target dates are critical you’ll discover a lot of people who are very good at breaking down projects and accurately estimating dates without relying on crunch time to get things done. It may sound impossible if you’ve never worked in an industry that requires such precision, but it makes sense after you’ve worked in such an environment for a while.</text></item></parent_chain></comment><story><title>Deadlines are pointless – what to do instead</title><url>https://lucasfcosta.com/2022/09/15/deadlines.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>0x20cowboy</author><text>It’s not that deadlines don’t exist (for some business reason), it’s just that trying to have both a deadline and a set of completed features is contradictory (if you want something that works well).&lt;p&gt;You can set out to have a set of features, and you can have a deadline, but thinking all the features will be completed (and completed well), on that day has never worked (in my experience). You just wind up with rush hacked garbage towards the end.&lt;p&gt;This is what I’ve done successfully for years now (when I am not forced by a PM to do agile): &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;concentric.works&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;concentric.works&amp;#x2F;&lt;/a&gt;</text><parent_chain><item><author>PragmaticPulp</author><text>It’s always fascinating to read these anti-deadline articles that assume deadlines are arbitrary things that exist for no reason.&lt;p&gt;That might be moderately true for, say, someone developing a new app feature that gets shipped to users who aren’t expecting it. However, it’s not true at all when the software development output is a gating feature for real-world contractual obligations and other such business drivers. In that case, target dates must be carefully forecasted and estimates must be performed with great care and detain. This doesn’t guarantee that a target date will be hit, of course, but it’s not impossible to produce estimates that are reasonable accurate a large percentage of the time.&lt;p&gt;Estimation, planning, and progress tracking are difficult skills that must be learned, but they’re not impossible. I suspect many of the developers who believe that target dates are always arbitrary, pointless, and impossible to estimate have mostly worked in big cash-rich environments where it didn’t really matter when a feature shipped. If you go to the other end of the spectrum and talk to engineers who work in industries where target dates are critical you’ll discover a lot of people who are very good at breaking down projects and accurately estimating dates without relying on crunch time to get things done. It may sound impossible if you’ve never worked in an industry that requires such precision, but it makes sense after you’ve worked in such an environment for a while.</text></item></parent_chain></comment><story><title>Deadlines are pointless – what to do instead</title><url>https://lucasfcosta.com/2022/09/15/deadlines.html</url></story>