There are definitely principles -- at least strategies -- that can help you design for change. But every project is unique, existing in its own context. There is no exact formula.
Show this thread
One of the biggest challenges of large software projects is designing for change. Supporting fast-evolving new use cases. Being able to sustainably expand the project over long periods of time. This is why simplicity, modularity, and disentanglement are of the utmost importance.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
%100 agree
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
agree 1000000%. I also try to use less external plugins.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Unfortunately, in some business oriented “profit-first” projects, the general design theme is: getting it done in any “crappy” way!
-
Sadly I think you're right though I'd caveat it with shiny-shiny done work deemed done
- Show replies
New conversation -
-
-
For large-scale long-term artistic projects the opposite is true?!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@fchollet I heard your conversion with Lex Friedman on AI podcast. Very interesting thoughts
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@TechSysN8v and@ruthmalan will enjoy this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That's the beauty of modular design
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.