Software Developer Career Growth
41 thoughts to become a kick-ass software developer, part 2
A collection of thoughts, tips and statements from various software developers across the globe and my two cents. Based on the book “Living by the code”.
This story belongs to a four part series.
#11 If you are interested in certain technologies or certain fields, you can just basically ask Google Scholar
Google Scholar allows you to search on a more scientific level finding latest papers, publications, articles, books, resources. I don’t regularly use it since I have left university. It might be still a good source of information gaining knowledge as you can also save e.g. collections ordered/grouped by specific attributes. To learn how to use Google Scholar, find yourself help. https://scholar.google.com/intl/en/scholar/help.html
#12 Focus on a single technology. Once you have achieved a certain level of depth, start to branch out
Though I am interested in several technologies and also have already looked into many, I can strongly support this statement. Before you become that developer knowing little in 100 technologies, prefer to know very much of few and become an expert before digging into further new stuff.
#13 Wake up early in the morning. These hours of uninterrupted work can help to accomplish results
The essence of this nice advise by Hadi Hariri was already mentioned in a similar form in #6. But again, early morning hours especially in summer being energized by the soft morning sun are priceless and contribute to happiness, success and getting stuff done without being interrupted.
#14 Algorithms have been there for 50 years. Acquire it early, it is supposed to stay with you for the rest of the career
Roman Elizarov’s tip to concentrate on algorithms in the beginning of your developer journey. It is essential for every developer to know common algorithms by heart as they are required over and over again despite the technology or programming language you are using.
#15 If you do have something you want to share, a feature or a problem you have solved, try to do that in the simplest possible way
Sharing knowledge is key, also when keeping #2 in mind. Being able to share a feature or problem solved by you in an uncomplicated manner and in the simplest way, you know that you have fully understood what you are doing and how to break it down into the essential parts. You don’t need to think complicated but just simply know how to showcase and teach the essential, in order to share the knowledge.
#16 Some people constantly learn and learn, reading and reading books, but they never actually build something. It is important to build something
For me it is also very nice to read books, to catch with my twitter feed, to reach a million different articles on medium, to subscribe to newsletters etc. but all these information sources help you to start a topic on a very high fight level. In order to really dig down and learn the specifics you need to build something on your own. (See also #34)
#17 Honest feedback allows for the chance to grow
Do not be afraid to provide feedback or receive feedback. It is even better to actively ask for honest! feedback in order to grow. That helps you not only to grow in areas which you think are important but also in areas which might not be on your radar yet but which are seen by your coworkers or friends.
#18 The code you write doesn’t have to be perfect the first time you write it. Write it a few times, try various different approaches, throw away code, refactor until it feels good and then clean up
Don’t be afraid or sad to throw away code, even though the code you have written is your creation. Don’t become to emotional about your creations. Keep in mind what Ernest Hemmingway once said “The first draft of anything is shit”. It is great to refactor and improve step by step and see your code evolve over time. However once you have “thrown” away code, version control provides all power you need to store different approaches or revert changes.
#19 Focus on things you really like working on
Remember a situation when you were really enthusiastic about a use cases or a technology? I think if you bring in your enthusiasm on a topic, it empowers you and your team to achieve things quicker and in a higher quality because you are really willing to spend much time and dig really deep into something to reach your goal accordingly.
#20 When choosing a direction, it’s important to follow your passion
Don’t let someone push you into a (technical) direction you are uncomfortable with or don’t let someone force you to work with a technology you hate. Same as #19, if you do not fully like something and can’t bring up passion, you are not able to put 100% of your energy and power. Find out what your passion is and then you will also be happy and can add real value.
If you want to learn more about/from these awesome people follow them or read their interviews in the book. It is definitely worth reading (more than once) independent of whether you are a beginner, mid-level or top developer.
What is your most important advice you would like to share with people who are trying to evolve and raise as a software engineer? Let me know and write it down in the comments and don’t forget to clap :)
