5 ms·

> Make undebuggable programs. Plaster layers of abstraction over everything. Write spaghetti code. Make everything sensitive to initial conditions. Avoid pure f

by mkl95 4y ago

> Make undebuggable programs. Plaster layers of abstraction over everything. Write spaghetti code. Make everything sensitive to initial conditions. Avoid pure functions. Use dependencies liberally. Say “it works on my machine” whenever possible. A lot of legacy software is like this. I wonder how many billions it costs the economy per year.

perceptronas 4y ago
Its extremely hard to argue for debuggability. I always try to prioritize how easy is it to test the said feature and understand it. However, during reviews of other engineers PR, I am always met with criticism that there is no need. "Instead of localhost, this can be tested on staging" and etc.
- solarkraft 4y ago
  Debuggability is a top factor for how long development will take. How is it hard to argue for?
  - quickthrower2 4y ago
    Only for developers who want to thoroughly test and check their work.
- edgyquant 4y ago
  >Instead of localhost, this can be tested on stagin No, it must pass a preview before being merged into staging
bdcravens 4y ago
The more difficult situation is the legacy software with all of those problems that actually makes money.