<?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: Timo Hoyland</title>
    <description>The latest articles on DEV Community by Timo Hoyland (@timo_hoyland_b8cf7d8283f7).</description>
    <link>https://dev.to/timo_hoyland_b8cf7d8283f7</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3736123%2F17355b16-de35-4743-bf00-f07d1731f70f.png</url>
      <title>DEV Community: Timo Hoyland</title>
      <link>https://dev.to/timo_hoyland_b8cf7d8283f7</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/timo_hoyland_b8cf7d8283f7"/>
    <language>en</language>
    <item>
      <title>Payroll</title>
      <dc:creator>Timo Hoyland</dc:creator>
      <pubDate>Sun, 08 Nov 2026 16:20:31 +0000</pubDate>
      <link>https://dev.to/timo_hoyland_b8cf7d8283f7/payroll-4gl1</link>
      <guid>https://dev.to/timo_hoyland_b8cf7d8283f7/payroll-4gl1</guid>
      <description>&lt;p&gt;We all love getting paid.&lt;/p&gt;

&lt;p&gt;It's normal. It's expected. We're not there for the subsidised coffee. We work for money because we need to live.&lt;/p&gt;

&lt;p&gt;People need food, shelter, cars, and holidays. We tie our income to our financial security. Our financial security is tied to our mental health.&lt;/p&gt;

&lt;p&gt;Somewhat.&lt;/p&gt;

&lt;p&gt;We don't really think about payroll, but imagine it's late. We will then. We'll also think about it every month thereafter.&lt;/p&gt;

&lt;p&gt;It's reassuring to be paid on time, in full. It shows the work, and people are valued enough to warrant healthy processes.&lt;/p&gt;

&lt;p&gt;Late payments have no upside. Inconsistencies break trust and impact productivity.  Payment will be made anyway.&lt;/p&gt;

&lt;p&gt;Disputes and tribunals cost. Hiring and training cost. Lost capacity and context cost.&lt;/p&gt;

&lt;p&gt;Delayed payment means everyone nets less food, shelter, cars, and holidays.&lt;/p&gt;

</description>
      <category>career</category>
      <category>management</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Boring</title>
      <dc:creator>Timo Hoyland</dc:creator>
      <pubDate>Tue, 20 Oct 2026 04:26:33 +0000</pubDate>
      <link>https://dev.to/timo_hoyland_b8cf7d8283f7/boring-55md</link>
      <guid>https://dev.to/timo_hoyland_b8cf7d8283f7/boring-55md</guid>
      <description>&lt;p&gt;Operations.&lt;/p&gt;

&lt;p&gt;The day-to-day is mundane. Filled with many habits and processes. Many run on autopilot. And that's okay. Set and forget - better things to do.&lt;/p&gt;

&lt;p&gt;But if we know we'll be doing something for a long time, or many times, it might be worth tuning. To be more comfortable. Efficient.&lt;/p&gt;

&lt;p&gt;Sure. That's a change. A change in state. And which state is correct? Works fine now. An architect I know would say neither. Trade-offs.&lt;/p&gt;

&lt;p&gt;So what are the trade-offs of change itself? Change is novel, and new things get noticed, because nature says it might kill us.&lt;/p&gt;

&lt;p&gt;And changing something people have already accepted costs extra. We see increased awareness during routine. Tiredness. Irritation. Suspicion of the established.&lt;/p&gt;

&lt;p&gt;Every change has to deliver value greater than the disruption it brings. The ideal change is cheap to adopt and quickly becomes normal.&lt;/p&gt;

&lt;p&gt;Second nature.&lt;/p&gt;

&lt;p&gt;Boring.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>softwaredevelopment</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>Boundaries in client engagement</title>
      <dc:creator>Timo Hoyland</dc:creator>
      <pubDate>Thu, 27 Aug 2026 13:11:03 +0000</pubDate>
      <link>https://dev.to/timo_hoyland_b8cf7d8283f7/boundaries-in-client-engagement-1913</link>
      <guid>https://dev.to/timo_hoyland_b8cf7d8283f7/boundaries-in-client-engagement-1913</guid>
      <description>&lt;p&gt;Don’t let them.&lt;/p&gt;

&lt;p&gt;Boundaries are tantamount to strategy. Have you ever had a client say they know what they want?&lt;/p&gt;

&lt;p&gt;Clients hire you because you know what they want. What they want hasn’t been battle-tested. It hasn’t survived traffic or user experience at scale.&lt;/p&gt;

&lt;p&gt;Delivering value is the core of engagement. Saying yes to everything invites noise, and noise is messy. Messy for you, messy for the client, messy for users.&lt;/p&gt;

&lt;p&gt;If you’re confused, say no. If you’re unhappy, say no. It only makes your yeses louder.&lt;/p&gt;

&lt;p&gt;Footing the bill doesn’t mean we disregard our principles. We are paid because of them. Don’t let them own delivery. We do.&lt;/p&gt;

&lt;p&gt;Results.&lt;/p&gt;

&lt;p&gt;...&lt;/p&gt;

&lt;p&gt;Origininally posted on &lt;a href="https://timohoyland.co.uk" rel="noopener noreferrer"&gt;https://timohoyland.co.uk&lt;/a&gt;&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>leadership</category>
    </item>
  </channel>
</rss>
