> Year 3 : By this stage your either stale and been working in the same place > for 3 years doing the same stuff and havent really developed your skills > much more than you had last year, worked for a hand full of people expanding > your skills or given up.
I'm on two minds about the 3rd point. Its easy to start a project, but its hard to finish and then support that project post its completion. In that i'd respect a developer more so who's completed 3 projects, but spent a year+ supporting those projects then someone who's completed 5 projects and has never supported thine projects. I say this as when you think on it some more, its probably some much needed skillset that gets overlooked, as it would not only test the developers discipline in terms of code hacking, but also gives them experience in terms of "what to be mindful of" when next approached for a new project. An interesting concept appeared locally here, where we built an application and rolled it out, it works but now we have to slide in a few features (needed to be scaled ) but also adhere to some Sax (Sarbanes-Oxley) audit requirements which meant it needed a closer look. Point: There is more to a an application then just coding. But I agree with your other points, well done steve *pats steve on the head, and feeds him a biscuit*... - Regards, Scott Barnes http://www.mossyblog.com --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
