Dare Obasanjo aka Carnage4Life - The GOOG->MSFT Exodus: Worki...
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 9 people (2 private), first by anonymouse user on 2008-06-30
- Sausau on 2008-07-03 - Tags google , news
- Wibblefarmer on 2008-07-03 - Tags todo , reading , google , microsoft , career
- Mmarlatt on 2008-07-02 - Tags microsoft , google , stroud , tweet
- Kenyth on 2008-07-01 - Tags microsoft , google , trends , career , starred
- Mattkramer on 2008-07-01 - Tags no_tag
Public Sticky notes
Highlighted by kenyth
Highlighted by kenyth
Highlighted by alvint
When your code base is young, it isn’t a big deal to have developers checking in new features after an overnight coding fit powered by caffeine and pizza. For the most part, the code base shouldn’t be large enough or interdependent enough for one change to cause issues. However it is practically a law of software development that the older your code gets the more lines of code it accumulates and the more closely coupled your modules become. This means changing things in one part of the code can have adverse effects in another.
As all organizations mature they tend to add PROCESS. These processes exist to insulate the companies from the mistakes that occur after a company gets to a certain size and can no longer trust its employees to always do the right thing. Requiring code reviews, design specifications, black box & whitebox & unit testing, usability studies, threat models, etc are all the kinds of overhead that differentiate a mature software development shop from a “fly by the seat of your pants” startup. However once you’ve been through enough fire drills, some of those processes don’t sound as bad as they once did. This is why senior developers value them while junior developers don’t since the latter haven’t been around the block enough.
Highlighted by hkeziah
Public Comment