3 ms·
The first example isn’t a software engineer. The code is a spaghetti mess because the system wasn’t engineered - there are no design documents, because the sys
by jwalton 5y ago
The first example isn’t a software engineer. The code is a spaghetti mess because the system wasn’t engineered - there are no design documents, because the system wasn’t designed it was just hacked together. There’s no memos describing why certain decisions were made.
The second is, ironically, usually the same, but instead of a lack of design there’s a lack of requirements, which is even worse.