<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: John Best</title>
    <description>The latest articles on DEV Community by John Best (@wintermute21).</description>
    <link>https://dev.to/wintermute21</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F18937%2F7cb62334-b53c-4dd2-9a36-9be0347f3e70.jpg</url>
      <title>DEV Community: John Best</title>
      <link>https://dev.to/wintermute21</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/wintermute21"/>
    <language>en</language>
    <item>
      <title>On empathy (or lack thereof) in tech</title>
      <dc:creator>John Best</dc:creator>
      <pubDate>Sun, 15 Apr 2018 02:53:04 +0000</pubDate>
      <link>https://dev.to/wintermute21/on-empathy-or-lack-thereof-in-tech-346n</link>
      <guid>https://dev.to/wintermute21/on-empathy-or-lack-thereof-in-tech-346n</guid>
      <description>&lt;p&gt;Recently, I've noticed a disturbing pattern among companies I've worked at that seem to care very little for their employees professional development, unrealistic expectations, etc. I keep wondering, is it me? am I a bad developer? Bad at setting expectations? All this seems very soul crushing and I wonder if it might not be time to find a different career. &lt;/p&gt;

&lt;p&gt;How do you all deal with it?&lt;/p&gt;

&lt;p&gt;Should one just find another job, or should you work to improve the culture?&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>culture</category>
      <category>career</category>
    </item>
    <item>
      <title>What reference books should devs have handy on different CS subfields?</title>
      <dc:creator>John Best</dc:creator>
      <pubDate>Thu, 12 Oct 2017 04:05:21 +0000</pubDate>
      <link>https://dev.to/wintermute21/what-reference-books-should-devs-have-handy-on-different-cs-subfields-8km</link>
      <guid>https://dev.to/wintermute21/what-reference-books-should-devs-have-handy-on-different-cs-subfields-8km</guid>
      <description>&lt;p&gt;Say you were starting a new role soon, what CS books should you always have as a reference?&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>career</category>
      <category>compsci</category>
    </item>
    <item>
      <title>On coding challenges.</title>
      <dc:creator>John Best</dc:creator>
      <pubDate>Sat, 30 Sep 2017 21:14:02 +0000</pubDate>
      <link>https://dev.to/wintermute21/on-coding-challenges-bff</link>
      <guid>https://dev.to/wintermute21/on-coding-challenges-bff</guid>
      <description>&lt;p&gt;As a dev candidate who's been unemployed for a while now, I see a lot of companies wanting you to take these timed tests to implement some challenge or algorithm. These have been criticized for not meaning much.&lt;br&gt;
And I myself am not sure if I want to feed into a culture that perpetuates this kind of meaninglessness, however, should I bite the bullet for the sake of a job or hold out on principal?&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>interview</category>
      <category>careeradvice</category>
    </item>
    <item>
      <title>On recruiting contractors and developers</title>
      <dc:creator>John Best</dc:creator>
      <pubDate>Sun, 17 Sep 2017 22:19:21 +0000</pubDate>
      <link>https://dev.to/wintermute21/on-recruiting-contractors-and-developers</link>
      <guid>https://dev.to/wintermute21/on-recruiting-contractors-and-developers</guid>
      <description>&lt;p&gt;I wanted to share some thoughts on having been a contractor for the last few years and how what I've seen ties into how we as an industry recruit developers and how we can do better.&lt;/p&gt;

&lt;p&gt;I started my career as a contractor and was basically treated like a meat grinder. Not a lot of training and not a lot of cushion if you screw up. very little mentorship. No job security whatsoever, so if they don't like you or whatever, you can be out on your ass with no recourse. I wish I hadn't started out that way because of how difficult it was to learn good habits later.&lt;/p&gt;

&lt;p&gt;It definitely exacerbated my latent PTSD from adolescence.&lt;/p&gt;

&lt;p&gt;Had to take prevacid every day to deal with anxiety induced heartburn.&lt;/p&gt;

&lt;p&gt;Companies should be clearer about recruiting candidates.&lt;/p&gt;

&lt;p&gt;Companies should be willing to train people. &lt;br&gt;
It isn't hard.&lt;/p&gt;

&lt;p&gt;We're smart people.&lt;br&gt;
We just need a positive environment to grow in,&lt;br&gt;
like plants.&lt;/p&gt;

&lt;p&gt;I hope this is useful to someone.&lt;br&gt;
Because the way we recruit people right now doesn't work for companies or devs.&lt;/p&gt;

&lt;p&gt;I've been left to flounder and it's the worst feeling as a professional.&lt;br&gt;
No one should be made to feel that way by their bosses.&lt;/p&gt;

&lt;p&gt;We all have a responsibility to do better as an industry.&lt;/p&gt;

</description>
      <category>recruiting</category>
      <category>contracting</category>
      <category>it</category>
    </item>
    <item>
      <title>Building custom tooling with a new API, or, How I learned to stop worrying and love Sitecore</title>
      <dc:creator>John Best</dc:creator>
      <pubDate>Sun, 14 May 2017 17:23:46 +0000</pubDate>
      <link>https://dev.to/wintermute21/building-custom-tooling-with-a-new-api-or-how-i-learned-to-stop-worrying-and-love-sitecore</link>
      <guid>https://dev.to/wintermute21/building-custom-tooling-with-a-new-api-or-how-i-learned-to-stop-worrying-and-love-sitecore</guid>
      <description>&lt;p&gt;So, I was working for a large staffing company and we had a few legacy ASP.NET Web Forms based sites with a large amount of user data to migrate to our regular CMS system called Sitecore.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fi.imgur.com%2FCKF4z2d.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fi.imgur.com%2FCKF4z2d.png" title="Above is where users would add and edit content for different sites. And you created and derived templates for various types of content." alt="Sitecore"&gt;&lt;/a&gt;&lt;br&gt;
Sitecore is an ASP.NET based CMS that exists in both Web Forms and MVC flavors. We had mostly used the Web Forms version.&lt;/p&gt;

&lt;p&gt;Our project was a big redesign of a legacy site that we already had. We had some blog posts and other data that we had to dedupe and clean up. My code was maybe 500 lines, but the task was a sticking point for the rest of the team. I suggested the idea of the tool to my colleagues who let me run with it.&lt;/p&gt;

&lt;p&gt;We had a bunch of data and duplicate data we had to clean up and import to Sitecore, so I studied the Sitecore API to transform all the data we had into Sitecore’s traditional data structure called Items. And Items existed for different kinds of objects, depending on what template you derived from, Folder, Page, Layout, SubLayout, etc.&lt;/p&gt;

&lt;p&gt;So I wrote a tool that would strip out duplicates from the data that we already had, move it all into Sitecore items where it can be easily manipulated and stored using Sitecore’s .NET API from SQL Server.&lt;/p&gt;

&lt;p&gt;The tool took a while to run, but it worked the first time and it saved the other 3 people who were working on it a few weeks of effort. And it only took me a week or so to write the tool itself.&lt;/p&gt;

</description>
      <category>sitecore</category>
      <category>aspnet</category>
      <category>csharp</category>
    </item>
  </channel>
</rss>
