Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • November 27, 2015, 11:19:37 AM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Working for the Man: Essay on Lessons for Young Software Developers  (Read 3226 times)


  • Super
  • Blogger
  • Joined in 2006
  • ***
  • Posts: 826
    • View Profile
    • Donate to Member
After I'd finished checking for obvious facial wrinkles in the bathroom I decided to go on a quest to find other engineers in the building who were at least as old as I was, and felt much better when I found some. But it set me thinking about what kind of advice I would give if I could meet myself at his age, in order to guide the young Allison into a promising engineering career. So in the best spirit of "The Screwtape Letters", here is some of what I've learned so far about making yourself a career in writing software.
If it's not what you love, don't do it
I've worked with many programmers during my career. Without a doubt, the only ones who are any good at it are those who see writing code as art, a creative process.

from www.slashdot.org
Kenneth P. Reeder, Ph.D.
Clinical Psychologist
Jacksonville, North Carolina  28546
« Last Edit: April 11, 2007, 04:15:39 PM by mouser »


  • Supporting Member
  • Joined in 2006
  • **
  • Posts: 1,927
    • View Profile
    • Read more about this member.
    • Donate to Member
Re: Working for the Man: Essay on Lessons for Young Software Developers
« Reply #1 on: April 11, 2007, 07:07:20 PM »
And my advice you young programmers to go along with this fine article [hint, hint] is to find the good blogs, the ones by veteran programmers AND THEN from those, find the ones that have comments from other veteran programmers. Now, you have a blog on programming that is worth reading. And that means from blog post to the last comment each day for a week, or more. Just because the original post is more than 24 hours old, it does not mean the discussion is over. And just because a blog post is a year old, does not mean that the advice is no longer valid. Good advice, real good advice, is timeless.

update: I added a comment to the blog. I am interested in your comments on my comment.  :) It is awaiting approval my the moderators. I signed it Chaim and it is titled Know The General and Learn the Specifics.
« Last Edit: April 11, 2007, 08:48:30 PM by tinjaw »