controversially: why can’t software be good?
14 replies
@zachleat as slop-coded garbage continues to infiltrate every product category, I expect more people will start asking this question.
@zachleat My suspicion: Most programmers like creating new things but not maintaining them (cleaning up small bugs, etc.).
@rauschma incentives are usually not aligned with maintenance, unfortunately
@zachleat An academic research topic since at leasts the 1970s. The most profound thing I read about it was about safety and liveness properties of software.
· Lamport, L. (1977): "Proving the correctness of multiprocess programs"
· Lamport, L. (1980): "On interprocess communication"
· Alpern & Schneider (1985): "Defining liveness"@zachleat Because senior leadership wants it yesterday, and they want it cheap. 😉
@stegrainer we need more junior leadership, apparently
@zachleat Because software in this context usually means a highly complex system and as such it needs to fulfill a lot of requirements at once. Only a single purpose thing can be done exceptionaly good. With each additional requirement rises the probability of inevitable trade-offs that make the overal appearance "not good". Note that we often don't realize or acknowledge all the requirements on software that it needs to fulfill because they seem secondary or non-functional.