This link has been bookmarked by 33 people . It was first bookmarked on 13 Jun 2008, by Eddie Osh.
-
04 Mar 10
-
13 May 09
-
13 Mar 09
Comment on commit granularity and level of detail, public versus private commits, compressing several commits into a single commit.
version-control vcs dvcs scm collaboration sharing programming
-
12 Oct 08
-
Be transparent. Share your work constantly. Solicit feedback. Appreciate critiques. Let other people point out your mistakes. You are not your code. Do not be afraid of day-to-day failures — learn from them. (As they say at
Google , “don’t run from failure — fail often, fail quickly, and learn.”) Cherish your history, both the successes and mistakes. All of these behaviors are the way to get better at programming. If you don’t follow them, you’re cheating your own personal development.
-
-
14 Jul 08
dalehagglundCollins-Sussman observes that many programmers will go to great lengths to avoid showing other developers their work-in-progress which works against common best-practices in software development.
programming psychology article collins sussman ben sharing source code programmers version control best practices
-
29 Jun 08
-
I’ve got a lot to say today!
I want to chat about something that I’ve never noticed before, but probably should have. There’s always been a stereotype out there of programmers being nerdy, anti-social people (Q: How do you know when an engineer is outgoing? A: He looks at your shoes!). But my revelation of the week is that most programmers seem to be really insecure about their work. I mean: really, really insecure.
-
-
25 Jun 08
-
23 Jun 08
-
16 Jun 08
-
15 Jun 08
Geekgirl 397Be transparent. Share your work constantly. Solicit feedback. Appreciate critiques. Let other people point out your mistakes. You are not your code. Do not be afraid of day-to-day failures — learn from them.
delicious programming development opensource versioncontrol code bestpractices psychology collaboration career for:jill_ol
-
Be transparent. Share your work constantly. Solicit feedback. Appreciate critiques. Let other people point out your mistakes. You are not your code. Do not be afraid of day-to-day failures — learn from them. (As they say at Google, “don’t run from f
programming review peer article blog collaboration SVN hiding
-
14 Jun 08
-
13 Jun 08
Norman KabirCode-reviews taken as personal attacks. Fitz tells a funny anecdote about a friend of his who went from the open source world to a corporate software job. Vastly paraphrased:
-
sdagueReally good points. While I'm not sure I agree with all his distributed version control issues, they are some valid points worth considering.
programming development versioncontrol bestpractices opensource
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.