<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: magnusekdahl</title><link>https://news.ycombinator.com/user?id=magnusekdahl</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 20 May 2026 18:49:29 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=magnusekdahl" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by magnusekdahl in "Ask HN: What tone to use in code review suggestions?"]]></title><description><![CDATA[
<p>When it comes to feedback, ensure that you give the engineer recieving the feedback the maximum potential to grow to ensure the engineer does a better job next time.<p>Its not the tone but rather the feedback style according that should be adapted to the knowledge/motivation of the engineer in the situation. For example by using the <a href="https://situational.com/blog/the-four-leadership-styles-of-situational-leadership/" rel="nofollow">https://situational.com/blog/the-four-leadership-styles-of-s...</a> herustic:<p>1: Engineer is junior in the context and insecure/unmotivated: Do X
2: Engineer is junior in the context and motivated/secure: Take the decision for the engineer and explain why
3: Engineer is senior in the context but insecure: Coach by open ended questions: how large of a function do you think is appropriate?
4: Engineer is senior and motivated/secure: From your perspective how should the function be and how should we do this in the future to reach our goals.</p>
]]></description><pubDate>Mon, 27 Jun 2022 18:20:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=31898508</link><dc:creator>magnusekdahl</dc:creator><comments>https://news.ycombinator.com/item?id=31898508</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31898508</guid></item></channel></rss>