![]() ![]() Responsibility is not only related to coding, though. Responsibility is something you actively agree to. The best way to make sure the code won’t fail is by testing it – having automated tests that you run each time you write new lines to be sure everything is still working. You must ensure that it not only works now but will do so in the best possible way for a long time (nothing lasts forever). Table of ContentsĪs a software developer, you are responsible for the code you create. I’ll share some lessons I learned from them in this article. These books focus not only on how to write code, but on teaching you best practices for developing software and even useful life lessons. Articles can sometimes fall short, and reading well-known books is the often best approach. The same thing happens when you want to understand the subject really deeply. You end up reaching for the official docs, or the source code of that technology to find the answer. When you are developing software, you may get stuck at a point where YouTube videos and StackOverflow answers don’t help. My goal was to learn, improve, and get the kind of knowledge that a teacher from mine used to say “ can’t be obtained from just reading articles.” You'll find these books on almost every “top 10 Software Development books” list out there. ![]() I recently finished reading The Pragmatic Programmer 20th Anniversary Edition (2019) and The Clean Coder (2011). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |