<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>bpyne</author><text>All the advice is well-worth reading. Number 16 (&amp;quot;Rubber Ducking&amp;quot;) is my particular favorite. It kills my ego every time, but the thought process involved in explaining the goal, attempted solution, and the problem seems to make the problem clearer. Explaining it in writing does not seem to have the same effect for me. It has to be audible.</text><parent_chain></parent_chain></comment><story><title>Lessons Learned in Software Development</title><url>http://henrikwarne.com/2015/04/16/lessons-learned-in-software-development/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>paco3346</author><text>I wish I would have had something like this when I first started developing. 90% of what&amp;#x27;s in here are things I learned over time (and some at great cost).&lt;p&gt;One I would add is to not throw a fellow dev under the bus when talking with a user. Give praise to specific team members but take the hits as a team. It helps build comradery when you see a colleague take the hit for you and builds a certain trust amongst the team knowing that others have your back.</text><parent_chain></parent_chain></comment><story><title>Lessons Learned in Software Development</title><url>http://henrikwarne.com/2015/04/16/lessons-learned-in-software-development/</url></story>