<?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 Tommy Pyatt on Medium]]></title>
        <description><![CDATA[Stories by Tommy Pyatt on Medium]]></description>
        <link>https://medium.com/@tommypyatt?source=rss-b670bd4e7de1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lh_7twFJWzkyb4ex.jpg</url>
            <title>Stories by Tommy Pyatt on Medium</title>
            <link>https://medium.com/@tommypyatt?source=rss-b670bd4e7de1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:12:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tommypyatt/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[Can code be art? Sure it can]]></title>
            <link>https://medium.com/@tommypyatt/can-code-be-art-sure-it-can-dd827d02a867?source=rss-b670bd4e7de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd827d02a867</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tommy Pyatt]]></dc:creator>
            <pubDate>Thu, 25 Aug 2022 13:27:38 GMT</pubDate>
            <atom:updated>2023-11-01T13:56:57.845Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a topic that I’ve given quite a bit of thought to over my time as a software engineer. At school, I used to be considered ‘good’ at art class, even though I never really considered myself good at it and I was too young to really understand what it would mean to be good at art in the first place. I never went on to study art at college or university though, so perhaps I’m not really qualified to say whether code is art or not. But I’m going to give you my argument anyway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZOYeqx6STkOgK4ifPMXcUA.jpeg" /></figure><p>I suppose I need to start with a definition of sorts of what I consider art to be, without getting too Leo Tolstoy about it. Words are all just labels but I think it’s safe to say that this particular word-label is a particularly troublesome one to define. In my view though, art is anything that communicates something. Be that an idea, a concept, a pleasant feeling or, in its most powerful form, an emotion.</p><p>Whenever I mention what I do for a living to people I’m sometimes told that whoever I’m speaking to wouldn’t be able to do what I do, because they’re not very good at logical thinking or maths. And on the face of it I can understand this perception, because that’s what coding seems to be. Communicating with a machine. Well, to some degree, it is. The machine needs to be able to understand the instructions you’re giving it in order to turn particular inputs into desired outputs based on algorithmic calculations. Code that fails to do this correctly is useless. But there’s a second dimension to coding that I think is much more important than this one that’s frequently overlooked, and that’s the necessity to communicate not only with the machine but with the other humans who might work with the code you are writing.</p><p>This could be the moment you submit a pull request to have your code integrated into a repository, or it could be communicating with someone in the future who wants to reuse or extend the functionality it provides. In a sense, whenever you’re writing code you’re also writing an API, or application programming interface, no matter how big or small the feature is that you’re implementing.</p><p>Although there’s some controversy in the software engineering industry about the term, I think it’s safe to say that good code should be to some extent at least self-documenting. That’s sometimes taken to the extreme and excuse by developers to never write any documentation at all. Sometimes time pressures mean that documentation is overlooked. But good documentation, and self-documenting code, can be considered by the aspiring code artist as part of his or her craft.</p><p>Creating good art always involves effort. In order to communicate something, you need to first conceptualise and comprehend the idea yourself. At an art auction, the effort of doing this and realising your idea into physical form would be reflected in the price that the viewer would be willing to pay for the finished product. Personally I can’t see value at all <a href="https://www.gq.com/story/suddenly-the-koons-is-this-100k-banana">in duct-taping a banana to a wall</a>, but someone felt that the concept was worth $120,000 of money, so who am I to argue?</p><p>This is where communication with the end-user reveals its importance. A good software engineer can understand a problem or a requirement in technical terms but actualise it and communicate the solution in non-technical terms. This is where an engineer can really shine as a code artist. My favourite part of my job is getting positive feedback from the people who use the things I create and seeing them being used. Sometimes they make use of it in creative ways that I didn’t expect, which feels to me like a sort of feedback loop where the user and I create something together. Twitter did this with hashtags and @ mentions if I remember rightly, responding to how their users were using their software and developing new features from those ideas.</p><p>Effort spent refactoring code, chatting with QA testers and prospective users, writing succinct but descriptive commit messages and pull requests, is not wasted effort. The time taken is necessary to create something beautiful. Good, well-thought-out, code can bring immense value, whereas bad code introduces problems that can reduce the net value of the finished product to zero or thereabouts.</p><p>Although I let creating art for art’s sake fall by the wayside after leaving school, I still partake in a few creative endeavours. I like to draw and paint occasionally because I find the process relaxing. I play musical instruments for much the same reason, and also because I enjoy playing songs for my friends, along with my terrible singing. I feel in these moments that I’m creating joy and having fun.</p><p>But I consider my work in coding and collaborating with others to be an expression of something, and coding to be one of my most creative outlets. There are countless solutions to the sorts of problems one encounters as a software developer, and the process of choosing what one feels is the most elegant solution within the constraints given involves imagination, experimentation and curiosity. Admittedly it’s no wall-banana and rarely elicits an emotional response, but I consider it to be art. And since art is subjective anyway, I shan’t let anyone tell me otherwise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd827d02a867" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>