4 ms·

The issue at discussion here seems to be if you can even truly evaluate software work chunks accurately enough for it to matter..

• Joel_Mckay 4y ago
  With enough experience it usually breaks down into the following temporal classifications: 1. 2 hours for trivial features 2. 2 days for normal features 3. 2 weeks for performant features 4. 2 months for known problems 5. 2 years for unknown problems 6. 2 decades for hard/currently-impossible problems 7. never (*note this is the default for people who can't tell the difference) Part of PERT, is placing redundancies with statistical upper bounds on estimated complexity. i.e. if the team or technology is unfeasible it is garbage collected. Many HR process people mistakenly assume every staff member is interchangeable/replaceable, as all tasks fall below class 4 in their mind. Cheers =)
  • djmips 4y ago
    Amazon believes all software developers are fungible.
    • Joel_Mckay 4y ago
      Agreed, the recruiter representing the hiring process at Amazon was/is very disrespectful indeed. Some like being unencumbered legally... so much so... a few more grand for the tax man make zero difference where you work. Amazon survives only as long as companies keep falling for the loss leader IT service models. Cloud-compatible is far wiser than a vendor lock-in that would make Oracle blush. Best of luck =)