<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Soft-Skills on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/soft-skills/</link>
    <description>Recent content in Soft-Skills on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 16:51:00 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/soft-skills/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Developer Burnout: 9 Tips to Help</title>
      <link>https://www.bradcypert.com/developer-burnout-9-tips-to-help/</link>
      <pubDate>Fri, 29 Mar 2019 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/developer-burnout-9-tips-to-help/</guid>
      <description>&lt;p&gt;Burnout happens — especially developer burnout. It’s unfortunate, but a fact of life. However, it seems to happen to developers (and maybe Doctors, but you’re not my target audience) far more often than other professions. It may manifest in the emotion of dread, knowing you have to go in to work tomorrow. Or it may manifest in sadness, just thinking about staring at code. Or it may possibly manifest as anger, thinking about the project that won’t seem to work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
