Last night I was talking about articulating your codebase's guiding principles, as a way to communicate your software design conventions.https://twitter.com/sarahmei/status/880952852033622016 …
-
-
Replying to @sarahmei
Sarah Mei Retweeted Sarah Mei
What I've been calling "your codebase's guiding principles" are things like this:https://twitter.com/sarahmei/status/880955463050842112 …
Sarah Mei added,
2 replies 2 retweets 13 likes -
Replying to @sarahmei
This morning I realized the phrase I've been using is not quite right. The guiding principles are not actually properties of the codebase.
1 reply 0 retweets 7 likes -
Replying to @sarahmei
The guiding principles do exist in the context of a particular codebase, but they arise from the team.
2 replies 2 retweets 6 likes -
Replying to @sarahmei
A different team would have a different set of guiding principles for the exact same codebase.
1 reply 2 retweets 6 likes -
Replying to @sarahmei
Even the same team under different circumstances would have different guiding principles. For example, what would they look like for:
1 reply 1 retweet 4 likes -
Replying to @sarahmei
- A team of all senior devs who have no plans to hire junior devs - The same team of all senior devs who want to start hiring junior devs ?
4 replies 2 retweets 7 likes -
Replying to @sarahmei
I guess I have to come up with a new name since they're not "codebase guiding principles" Naming things is the worst >_<
7 replies 0 retweets 15 likes
Sound like design goals?
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.