4 ms·

Can you explain 'unnecessary dependency nonsense'?

• austincheney 9y ago
  If I can write it faster myself and end up with lower maintenance overhead compared to the concerned dependency the concerned dependency isn't needed. This is a major concern of framework applications that intertwine with your logic since removing a framework from your application may mean a complete rewrite of your application. With production software each and every dependency you do not validate with your integration tests is a risk beyond your visibility. I frequently hear from JavaScript developers the excuse that a popular application is validated by the community. This is a false validation from somebody who has never worked operations. The community is irrelevant. The only thing that matters is the health of your application, which is something you must take ownership of very directly.
  • nenadg 9y ago
    How do you measure 'health' of your application, if you write from the scratch with community removed?
    • austincheney 9y ago
      Lots of validation tests. Prove your application does everything it says it does with as many known variants as possible.