<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Travis Frisinger on Medium]]></title>
        <description><![CDATA[Stories by Travis Frisinger on Medium]]></description>
        <link>https://medium.com/@tmfrisinger?source=rss-92080147272a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*GYZ-UlzVQnwiOVZ3.jpg</url>
            <title>Stories by Travis Frisinger on Medium</title>
            <link>https://medium.com/@tmfrisinger?source=rss-92080147272a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:44:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tmfrisinger/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From farmer to programmer to manager]]></title>
            <link>https://medium.com/@tmfrisinger/from-farmer-to-programmer-to-manager-8f43af2dfadd?source=rss-92080147272a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f43af2dfadd</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Travis Frisinger]]></dc:creator>
            <pubDate>Sat, 26 Nov 2016 11:11:11 GMT</pubDate>
            <atom:updated>2016-11-26T11:11:11.598Z</atom:updated>
            <content:encoded><![CDATA[<p>I grew up in northern reaches of Wisconsin on a dairy farm. I spent my summers driving tractor, milking cows and helping out on the family farm. I first got into programming when I was about 12 years old. I had convinced my parent to sell the farm truck and get me a computer. I was fascinated with computers; I wanted to learn how to make it do things, aka write code.</p><p>It was after much begging my parents relented and purchased the family a computer for Christmas in 1993. I eventually got my hand on a set of tools to write code and I fell in love. The magic of struggling, breaking through and the proud moments of success make it all worthwhile.</p><p>Over the years I would stay up late after milking the cows and write code. I first started off writing software about herd management for the farm in C. I had grand visions of a computer in the barn with all the handwritten records being electronically accessed.</p><p>I admit, was a bit ambitious for our farm considering we still had a rotary dial telephone; never mind the vast amounts of moisture and other hazards. As a kid I seemed to have boundless vision of what agriculture should be. When I played with my farm toys the farmer character always had a PhD in some advanced science and could grow crops in one day and create genetically engineered cows to produce vast amounts of milk.</p><p>One night while milking cows with my Dad, I was rambling on about some neat idea I had to improve things when he turned to me and said the words that would later change the trajectory of my career, “Wish in one hand and shit in the other and see which fills up quicker.”</p><blockquote>“Wish in one hand and shit in the other and see which fills up quicker.”</blockquote><p>His point being ideas are great, but action is what matters. It is only through action that change can happen. On a farm there is too much work and not enough hands, staying practical is how a good farm operates. Obviously this did not appeal to me, hence my fascination with programming and not cows.</p><p>As the years rolled on I had forgotten this gem my father had dispensed. I worked a variety of jobs in software development. To-date, I have worked across four continents accruing a vast array of stories from the trenches. I have had a few great managers, but mostly average to poor managers. And some wild and crazy managers who’s antics are on par with Wolf of Wall Street.</p><p>It was while at one of the wild and crazy places, I was reminded of the phrase my Dad had told me all those years ago. I had spent so many years complaining about how management did not get it, it was time for me to stop wishing in my one hand.</p><p>At this same time I had started studying my MSc in Software Engineering from DePaul via their distance learning program. I was based in South Africa and could not make it back to America to study.</p><p>I had started off with a technically focused emphasis. At the time I was enthralled with technology. It was exciting and it would always be the core of my career path. I loved the abstract concepts of programming, management always seemed boring and hands-on.</p><p>It was while reflecting one night that I recalled that magical phase from all those years ago. It was then that I decided to start pursuing a management focused emphasis. I ended up taking 1/2 of my classes from the school of business. It was at this point I changed my career focus from being the best programming I could be, to figuring out how I could build an army of programmers better than me.</p><p>I truly believe that the future of the world is knowledge work. It will be the predominant employment paradigm one day. Figuring out how to create and manage high performing teams is a key challenge of today and tomorrow. There is too much dysfunction in the software development world and this needs to change. We need to drop the elitist rhetoric and focus on producing real value quickly.</p><blockquote>There is too much dysfunction in the software development world and this needs to change. We need to drop the elitist rhetoric and focus on producing real value quickly.</blockquote><p>Thus far the journey in management has been an interesting one. I have retained some technical skills, but mainly in a supporting role to the team. I have learnt that trying to be both a good manager and the best programmer will end with me not being very good at either.</p><p>I have learn the beauty of therapeutic code refactoring, that is refactoring snippets of code to that are not bugs, but surface as technical debt in Sonar. It is a great way to keep a pulse on the code base without making myself a key man dependency.</p><p>I have also learnt to kill my ego at least once a month by using reflective reporting. I attempt to park my ego and reflect upon how my team performed. I see it as my responsibility to design an environment in which they can excel. Often times the reason they did not do well is because my ego got in the way, not that they did not listen to me. I have learnt I need to avoid concrete action plans and focus on dispensing wisdom like my father did all those years ago.</p><p>By honestly reflecting upon everyone’s performance once a month, I can adjust and realign the current environment to better represent the core ethos of my team. My team’s ethos are open and honest communication, mentorship, craftsmanship, creating an environment of trust and loving our technical debt, thus ensuring it is taken care of each and everyday.</p><p>I attempt to adjust the environment though the use of experiment cards. An idea I have borrowed from Ash Maurya’s <a href="https://leanstack.com/how-we-use-lean-stack-for-innovation-accounting/">Innovation Accounting</a>. I prescribe to no single set of “Agile” practices; I believe in constant innovation. Find what works for you and then experiment to improve it. My environment is a mix of many practices and processes and has come about through many hours of discussion and experiments.</p><p>Even in an environment of trust, I still hold a architectural veto. I do this as part of my wisdom dispensing practice. If I feel there are hidden traps in the chosen path or things are not clear to me I will veto it until the team finds a better way to do it or explains their thought process in more detail. I see no reason to throw out all my years of deep technical experience only to have the team re-learn hard lessons. And because of the open and honest communication it is a discussion about the issues, not a command and control statement.</p><p>I hope to continue documenting the many lessons I have learnt in an effort to cut through the crud of this industry. Or at the very least better understand why what I have done works so well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f43af2dfadd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>