Re: Advancing from Unix Sysadmin to Programmer
From: Otto Wyss (otto.wyss_at_orpatec.ch)
Date: 05/20/04
- Next message: Rich Teer: "Re: Advancing from Unix Sysadmin to Programmer"
- Previous message: Kevin Collins: "Re: "No Shell""
- In reply to: David Schwartz: "Re: Advancing from Unix Sysadmin to Programmer"
- Next in thread: Rich Teer: "Re: Advancing from Unix Sysadmin to Programmer"
- Reply: Rich Teer: "Re: Advancing from Unix Sysadmin to Programmer"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 20 May 2004 21:38:27 +0200
David Schwartz <davids@webmaster.com> wrote:
> Martin McMahon wrote:
>
> > I am a 33 year old Unix System Admin and am currently at a stage
> > in my career where I have identified a change is needed in my career.
> [snip]
> > Is it possible at this stage of my life to transfer (by whatever
> > means) to a purely programming role, considering my age,
> > experience and education?
>
> Yes, of course. You're young and fairly experienced, so it should not be
> all that difficult.
>
But don't expect to much, dull programming jobs aren't better then sys
admin jobs and good programming jobs are very rare. If you feel you can
do it go for it.
> Unfortunately, though, there's no substitute for experience. You'll have
> to make every programming mistake two or three times just like every other
> programmer. And other programmers will be familiar with algorithms you've
> never even heard of. And you can't read about these things and absorb them,
> you have to run into problems and solve them.
>
While there is no substitute for experience, experience can be aquired
through hard work. IMO the best way to aquire experience without being
fired by the boss is to participate in any OpenSource project. I'd
choose a medium size project since it probably is easier to look
through. The advantage of OpenSource project is your code is viewed by
others and if you make errors they will immediately be critisiced. And
the most important reason if you make valuable contributions any other
error will be forgiven.
So just look for a not to big project which is activly maintained. On
your way you will need help which only active maintainers will provide.
Important, before you request to join the project look through the bug
list and try to to fix any. If you have fixed enough bugs the
maintainers will ask you to join the project anyway since they know
you're a valuable contributor. BTW I know some developers who I'd love
if they would join my projects but they prefer to stay contributor.
Always think it's much better to be a good contributor than a bad member
of a project.
Don't give up when you can't fix a bug, it might be too difficult for
your current knowledge. Just leave it for later and try a simpler one.
Also don't give up when a fix is rejected, maybe a third of mine were
rejected. In case there aren't any bugs (yes that can happen) try to add
a missing feature and make a patch.
IMO the best way to get experience is looking through other's code. And
fixing bug is the best way to do it. And providing fixes makes you a
good contributor which will be rewarded with help, etc. when you need
it. Keep in mind everything what counts in OpenSource is code or
documentation, everything which brings a project ahead.
O. Wyss
-- See a huge pile of work at "http://wyodesktop.sourceforge.net/"
- Next message: Rich Teer: "Re: Advancing from Unix Sysadmin to Programmer"
- Previous message: Kevin Collins: "Re: "No Shell""
- In reply to: David Schwartz: "Re: Advancing from Unix Sysadmin to Programmer"
- Next in thread: Rich Teer: "Re: Advancing from Unix Sysadmin to Programmer"
- Reply: Rich Teer: "Re: Advancing from Unix Sysadmin to Programmer"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
