{"id":286,"date":"2009-08-26T10:44:44","date_gmt":"2009-08-26T10:44:44","guid":{"rendered":"http:\/\/kubasek.com\/blog\/pragmatic_craftsman\/?p=286"},"modified":"2009-08-26T10:44:44","modified_gmt":"2009-08-26T10:44:44","slug":"what-makes-a-great-software-engineer","status":"publish","type":"post","link":"https:\/\/pragmaticcraftsman.kubasek.com\/?p=286","title":{"rendered":"What makes a great software engineer?"},"content":{"rendered":"<p>Nicholas Zakas, the author of what I consider the best JavaScript book out there, is becoming one of my favorite bloggers! (I should let him know about that. :)) In his <a href=\"http:\/\/www.nczonline.net\/blog\/2009\/08\/21\/what-makes-a-great-software-engineer\/\">recent blog post<\/a>, he talks about qualities of great software developers. It&#8217;s a great post. I highly recommend reading the whole post.<\/p>\n<p>Here&#8217;s my take on the qualities from the post.<\/p>\n<p><strong>Always do it the right way<\/strong>I cannot agree more. There are always people that will say that they&#8217;ll improve it later; that this is special and it needs a special condition. It&#8217;s a big bull&#8230; You do it the right way ALL THE TIME. Really no exceptions.<\/p>\n<blockquote><p>Good engineers know that the right way applies to all situations and circumstances. If there&#8217;s not enough time to do something the right way, then there&#8217;s really not enough time to do it. Don&#8217;t make compromises, the quality of your work is what ultimately defines you as an engineer. Make sure that all of the code you write is done the right way 100% of the time. Expect excellence from yourself.<\/p><\/blockquote>\n<p><strong>Be willing to suffer<\/strong>I never considered this as an asset before. On the contrary, I thought that it must be something wrong with me. I like to develop solutions in my head, thinking hard about them, then implementing. And later find a better solution. I rarely ask others for help. And I usually come up with good solutions. Hmm, maybe there&#8217;s hope in my software engineering skills. \ud83d\ude42<\/p>\n<blockquote><p>Great engineers first and foremost want to solve the problem on their own. Problem solving is a skill, a skill that great engineers take seriously.<\/p><\/blockquote>\n<p><strong>Never stop learning<\/strong>If you have been reading what I write on this blog, I don&#8217;t need to say anything else. This is an absolute must if you want to be considered a great software engineer.<\/p>\n<blockquote><p>In order to be a great engineer you must first admit that you don&#8217;t know everything, and then you must seek out more knowledge in every way you can.<\/p><\/blockquote>\n<p><strong>Share your knowledge<\/strong>I believe that&#8217;s what makes you valuable to the company you work for. That&#8217;s how you distinguish yourself from others. This is how you think &#8220;big picture&#8221;.<\/p>\n<blockquote><p>Great engineers want others to know what they know. They aren&#8217;t afraid of losing their position because someone else can do the same thing. Great engineers want to see their peers succeed and grow.<\/p><\/blockquote>\n<p><strong>Lend a helping hand<\/strong><\/p>\n<blockquote><p>Great engineers are team-focused and therefore are willing to do whatever it takes to help the team.<\/p><\/blockquote>\n<p> Do I need to argue with that?<\/p>\n<p><strong>Take your time<\/strong>It takes time to develop and improve on your skills. The only way to do that is by learning iteratively, practicing. It probably will take 5 to 10 years, or even more, for you to acquire great skills. To acquire that craftsman&#8217;s touch. \ud83d\ude42<\/p>\n<p><strong>Reference<\/strong><a href=\"http:\/\/www.nczonline.net\/blog\/2009\/08\/21\/what-makes-a-great-software-engineer\/\">What makes a great software engineer?<\/a>, Nicholas C. Zakas<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Nicholas Zakas, the author of what I consider the best JavaScript book out there, is becoming one of my favorite bloggers! (I should let him know about that. :)) In his recent blog post, he talks about qualities of great software developers. It&#8217;s a great post. I highly recommend reading the whole post. Here&#8217;s my [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,9],"tags":[],"class_list":["post-286","post","type-post","status-publish","format-standard","hentry","category-better-coder","category-craftsmanship"],"_links":{"self":[{"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=\/wp\/v2\/posts\/286","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=286"}],"version-history":[{"count":0,"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=\/wp\/v2\/posts\/286\/revisions"}],"wp:attachment":[{"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=286"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=286"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pragmaticcraftsman.kubasek.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}