3 ms·

Later being codeword for never

• pjc50 6y ago
  Maybe the horse will learn to sing? https://en.wikibooks.org/wiki/Sufism/Nasrudin#Nasreddin_and_the_Sultan%27s_Horse https://en.wikibooks.org/wiki/Sufism/Nasrudin#Nasreddin_and_... Maybe putting the laptop in the data center lets you do the launch. Maybe the launch is a flop because you forgot to advertise it. Maybe you raise series A funding; maybe you don't and the site dies in three months, still happily running on the laptop. Maybe someone decides to re-write the product in a different stack. Maybe the product was wrong and needs to pivot. A lot of products have shipped and succeeded with absurd hacks in them. Hex-editing the binary to change "EMM386 Memory Error.." to "Thank you for playing Wing Commander", etc.
• bregma 6y ago
  I believe the correct translation is "in the fullness of time as we address technical debt."
  • nrclark 6y ago
    I know that I'm a small sample size - but in my career so far, "later" means "never" a lot more often than it actually means "later". Especially when it comes to paying down technical debt.
    • pc86 6y ago
      In my similarly limited experience, this is directly correlated with equal parts 1) how strong-willed the architects and technical leadership is; 2) how [dis]functional your non-technical leadership is. Most good developers want to pay down technical debt. Most good architects are able to balance business and technical needs enough to know when and how to pay down what debt without spending four sprints renaming variables. It's when you have either dis-functional leadership who refuses to listen to their employees (most likely IME), or architects weak in either skill or constitution who can't or won't stand up the bosses to try to explain to them why we need to spend some time renaming variables.