Deadline vs Good Quality Code

PayPal
JokesApt

Go to company page PayPal

JokesApt
Jun 9, 2018 9 Comments

I am facing a challenge to deliver within timeline .

I almost ended up writing a whole component to be deployed in production . The component works well in QA stages but am fixing alongside the PR review comments but my manager is like we need to ship the code as per deadline . I am totally not confident coz rather resolving bugs later do it beforehand is my approach . Any inputs on how to approach such situations . I am going to justify the code quality over timeline

One lesson learnt : always overestimate tasks during sprint planning

Require inputs .

Developer pains !

comments

Want to comment? LOG IN or SIGN UP
TOP 9 Comments
  • someone at a fucking payments company has to ask this question? should i delete my cc info from paypal?
    Jun 10, 2018 3
  • Have you told your manager this? Would more people help? Have you asked what is driving the deadline? Do you know your P0, P1 etc feature set to know correct priority? What are the possible reprocussions of shipping your code (in terms of $$$ business risk). Can you offer your manager different plans rather than hit or miss the deadline as a binary choice?

    Lesson learnt : learn to estimate better, not pad your estimates.
    Jun 9, 2018 0
  • Hubspot
    plrufly

    Go to company page Hubspot

    plrufly
    Why do Saas companies need deadlines anyway? No sprints, no deadlines, just deploy when we are ready. That's how we roll at Hubspot, mostly. Just don't mention GDPR ๐Ÿ˜‰.
    Jun 10, 2018 0
  • Depends on the product done, culture, there is not a one size fits all,
    Some of the products become worthless when its delayed. For example an app for Olympics, if you deliver the app after the Olympics there is 0 use whatever quality code you develop.

    If its involving payments or life quality should be of top concern
    Jun 9, 2018 0
  • Apple
    tuolumne

    Go to company page Apple

    tuolumne
    If thereโ€™s any doubt itโ€™ll cause a livesite, donโ€™t ship. Get it right. Ship when itโ€™s ready. You get better with estimations and properly sandbagging tasks because you understand the cone of uncertainty. Nothing sucks harder than shipping broken code and having to wake up at 3am to fix your mistake.

    If itโ€™s not a question about livesite quality and more about turd polishing, go ahead and ship and iterate on it.

    I have zero problem pushing back with my manager on deadlines if Iโ€™m in doubt. They typically respect it unless itโ€™s a hard deadline.
    Jun 9, 2018 0