|
Pollyanna posted:Oldies in this thread: what were your first two or three years as a developer like? What did you do that you suggest I should do? What missteps should I avoid? What would you do over again? Any advice for someone literally starting out? I spent my first few years learning, primarily, what and how not to do things. Mistakes, missteps, bad decisions, and bad designs will always occur. Avoiding them is impossible but education and experience can reduce their frequency. Most importantly is the ability to learn and apply that knowledge to future problems. Attitude, which was my largest obstacle as a younger developer, is a very important aspect of working in a professional environment. Being condescending and argumentative are counter-productive to both the development effort and work relationships. Understand that development occurs as a team, and it will be the team's decisions that drive design. Do not be offended or discouraged because you are the minority (or just told no) on a design decision. State your reasoning, learn from any discussion, and move forward. Always pursue continuing education. It is a fact that no matter how good you are, there is always someone better. Constant education on techniques, systems, languages, architectures, etc. will keep you and your skills relevant and assist you in advancing your career. Writing a lot of bad code and understanding why it is bad is a great way to achieve better code.
|
#
¿
Aug 1, 2014 19:02
|
|
|
|
| # ¿ May 7, 2024 01:34 |
|