<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Josh Meek</title>
    <link>https://joshmeek.com/</link>
    <description>Recent content on Josh Meek</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Sep 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://joshmeek.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Now</title>
      <link>https://joshmeek.com/now/</link>
      <pubDate>Thu, 29 Apr 2021 00:00:00 +0000</pubDate>
      
      <guid>https://joshmeek.com/now/</guid>
      <description>(This is a now page, and if you have your own site, you should make one, too.)
 Life  My daughter Hattie is now 18 months old. She&amp;rsquo;s funny, adventurous, loves being a helper. Playing with Hattie is the highlight of each day. We sold our current house and bought a new house, and will be moving in July. We&amp;rsquo;re extremely excited, as the new house will give us separate offices and a yard for Hattie to play.</description>
    </item>
    
    <item>
      <title>Making Better Estimates by Refusing to Estimate</title>
      <link>https://joshmeek.com/posts/making-better-estimates/</link>
      <pubDate>Tue, 01 Oct 2019 00:00:00 +0000</pubDate>
      
      <guid>https://joshmeek.com/posts/making-better-estimates/</guid>
      <description>Humans are inherently bad at estimating how long things will take. Seriously, just ask my wife: &amp;ldquo;I&amp;rsquo;ll be there in 15 minutes&amp;rdquo; can easily become two hours if I get distracted by some new idea or project along the way. Moreover, humans always estimate for the best-case scenario &amp;ldquo;happy path&amp;rdquo;, typically failing to account for additional time should issues arise, even if those issues are incredibly likely. We&amp;rsquo;re overly optimistic in our estimations.</description>
    </item>
    
    <item>
      <title>Dead-Simple Websites with Hugo and Netlify</title>
      <link>https://joshmeek.com/posts/building-this-website/</link>
      <pubDate>Sat, 07 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://joshmeek.com/posts/building-this-website/</guid>
      <description>This is a quick explanation of how this website is built, which will serve as a &amp;ldquo;living document&amp;rdquo; that will be updated as changes and additions are made.
I&amp;rsquo;ve been making websites for years. I used to be a fan of self-hosted Wordpress blogs, however Wordpress sites are increasingly the target of malicious attacks. A nefarious party can gain access to the backend of your site, deleting files, changing content, and even locking you out.</description>
    </item>
    
    <item>
      <title>About</title>
      <link>https://joshmeek.com/about/</link>
      <pubDate>Thu, 05 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://joshmeek.com/about/</guid>
      <description>I&amp;rsquo;m a development team lead at Orchard Software, a dual job that lets me guide the direction of my team and our products while still taking a hands-on approach as a developer.
I got my B.A. in Computer Science from Hanover College and my Masters of Computer Science from Ball State. While in grad school, I worked as a research assistant in S2ERC. After grad school, I taught an introductory CS course at Ball State.</description>
    </item>
    
    <item>
      <title>How to Write a Killer Resume</title>
      <link>https://joshmeek.com/posts/resumes/</link>
      <pubDate>Sun, 01 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://joshmeek.com/posts/resumes/</guid>
      <description>Writing a good resume, much like software development itself, is often more art than science. Most people use the limited space in their resume to simply hit the required bullet points of contact information, education history, work experience, and a generic list of skills they purport to possess. This, however, does nothing to make you stand out from the sea of other potential jobseekers who have crafted shockingly similar resumes to your own, and doesn&amp;rsquo;t get anyone excited about calling you for an interview.</description>
    </item>
    
    <item>
      <title>Lessons Learned from Deep Work</title>
      <link>https://joshmeek.com/posts/deep-work/</link>
      <pubDate>Sat, 31 Aug 2019 00:00:00 +0000</pubDate>
      
      <guid>https://joshmeek.com/posts/deep-work/</guid>
      <description>I recently read Deep Work by Cal Newport, after becoming increasingly frustrated with how often I&amp;rsquo;m pulled out of my deep development work for other &amp;ldquo;shallow&amp;rdquo; work tasks.
At Orchard, development team leads are both developers and managers, so I need to balance both completing development work with attending meetings, performing administrative tasks, fielding questions, and mentoring employees. So while these tasks might be &amp;ldquo;shallow&amp;rdquo; compared to diving into a development problem, they are still an important part of my daily work and can&amp;rsquo;t simply be ignored.</description>
    </item>
    
  </channel>
</rss>
