Feature: Applying Unix Philosophy to Personal Productivity
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
- productivity
- , GTD
- , unix
- , programming
- , lifehacks
- , advice
- , philosophy
- , self
- , agile
- , followup
- , lifehack
- , linux
- , howto
- , development
- , software
- , delimp
- , checklater
- , lang_en
Bookmark History
Saved by 11 people (-7 private), first by anonymouse user on 2008-01-29
- Dharan on 2008-08-03 - Tags self , development , linux
- Javabeanboy on 2008-05-30 - Tags no_tag
- Cpelletier on 2008-03-26 - Tags followup , productivity
- Laurenpressley on 2008-02-04 - Tags Productivity , lifehacks , GTD , Unix , programming , philosophy
- Gibarian on 2008-02-04 - Tags philosophy , productivity , unix
Public Sticky notes
The only way to write complex software that won't fall on its face is to hold its global complexity down—to build it out of simple parts connected by well-defined interfaces, so that most problems are local and you can have some hope of upgrading a part without breaking the whole.
Highlighted by gibarian
Code that is graceful and clear is less likely to break—and more likely to be instantly comprehended by the next person to have to change it. This is important, especially when that next person might be yourself some years down the road.
Highlighted by gibarian
Public Comment