Tip #1: Don't rush projects. Take time and think about where the end goal is and keep a steady, consistent pace during development. It'll get done. Also keep a list of bite-sized one to two day mini-tasks for the project handy. Little continual victories add up to a complete, production-ready project even if it takes months to complete the project.
Tip #2: Be proactive and positive. Most people wait for work to come to them. The best developers are the ones who ask around if there are any internal pet projects or issues they can work on at the company they work for. That approach gets noticed very fast. Just be careful to not get overwhelmed or sidetracked from primary responsibilities. Take on an extra project from other departments here or there just for fun as time permits and be everyone's hero.
Tip #3: Document, document, document. Good, current, non-automated documentation written by the original developer is rare to come by. Documentation written by users of the software will inevitably miss important edge cases.
Tip #4: Bug fixing is more important than new features. Buggy software makes life more complicated. Fix the bugs first and if there is time, then add a feature or two. Make it a goal to get to zero open issues on the issue tracker.
Here are some more tips:
Tip #1: Don't rush projects. Take time and think about where the end goal is and keep a steady, consistent pace during development. It'll get done. Also keep a list of bite-sized one to two day mini-tasks for the project handy. Little continual victories add up to a complete, production-ready project even if it takes months to complete the project.
Tip #2: Be proactive and positive. Most people wait for work to come to them. The best developers are the ones who ask around if there are any internal pet projects or issues they can work on at the company they work for. That approach gets noticed very fast. Just be careful to not get overwhelmed or sidetracked from primary responsibilities. Take on an extra project from other departments here or there just for fun as time permits and be everyone's hero.
Tip #3: Document, document, document. Good, current, non-automated documentation written by the original developer is rare to come by. Documentation written by users of the software will inevitably miss important edge cases.
Tip #4: Bug fixing is more important than new features. Buggy software makes life more complicated. Fix the bugs first and if there is time, then add a feature or two. Make it a goal to get to zero open issues on the issue tracker.
They are all good tips.
Bugs are definitely annoying and rushing will create more bugs.