<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>programming on Tom Hickerson's Site</title><link>https://tomhickerson.com/en/tags/programming/</link><description>Recent content in programming on Tom Hickerson's Site</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Copyright 2023-2026</copyright><lastBuildDate>Wed, 15 Aug 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://tomhickerson.com/en/tags/programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Software Development Requires Servant Leaders</title><link>https://tomhickerson.com/en/archives/en/2018/2018-08-15-aaron-longwell-why-software-development-requires-servant-leaders-culture-foundry/</link><pubDate>Wed, 15 Aug 2018 00:00:00 +0000</pubDate><guid>https://tomhickerson.com/en/archives/en/2018/2018-08-15-aaron-longwell-why-software-development-requires-servant-leaders-culture-foundry/</guid><description>&amp;ldquo;When the business side “wins”, the developers end up in a death march. When development concerns outweigh business ones, you end up blowing the budget and deadline. Either way you’re broken. Successful software managers find ways to be flexible; to bend without breaking and to resolve the tension gradually. Servant leadership can be a guide to finding this flexibility.&amp;rdquo;
tags: programming
Aaron Longwell | Why Software Development Requires Servant Leaders | Culture Foundry</description></item><item><title>Software Testing Anti-patterns · Codepipes Blog</title><link>https://tomhickerson.com/en/archives/en/2018/2018-04-22-software-testing-anti-patterns--codepipes-blog/</link><pubDate>Sun, 22 Apr 2018 00:00:00 +0000</pubDate><guid>https://tomhickerson.com/en/archives/en/2018/2018-04-22-software-testing-anti-patterns--codepipes-blog/</guid><description>&amp;ldquo;There are several articles out there that talk about testing anti-patterns in the software development process. Most of them however deal with the low level details of the programming code, and almost always they focus on a specific technology or programming language.
In this article I wanted to take a step back and catalog some high-level testing anti-patterns that are technology agnostic. Hopefully you will recognize some of these patterns regardless of your favorite programming language.</description></item><item><title>A tale of two programmers: the Rock Star and the Ditchdigger</title><link>https://tomhickerson.com/en/archives/en/2010/2010-10-15-a-tale-of-two-programmers-the-rock-star-and-the-ditchdigger-2/</link><pubDate>Fri, 15 Oct 2010 00:00:00 +0000</pubDate><guid>https://tomhickerson.com/en/archives/en/2010/2010-10-15-a-tale-of-two-programmers-the-rock-star-and-the-ditchdigger-2/</guid><description>Recently, I&amp;rsquo;ve seen some true words about the term &amp;ldquo;Rock Star&amp;rdquo; developer. That is, the company tarts up a job description by calling their programmers &amp;lsquo;rock star&amp;rsquo; and think they&amp;rsquo;ll get a higher quality of candidate for open positions. The truth is: bullshit.
Let&amp;rsquo;s say you&amp;rsquo;re hiring for a startup. Resources are limited. Your office space, if you can call it that, is five square meters of closet space that you rented from your aunt because it was the Decent Thing To Do.</description></item></channel></rss>