<?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 Ian Bennett on Medium]]></title>
        <description><![CDATA[Stories by Ian Bennett on Medium]]></description>
        <link>https://medium.com/@enbnt?source=rss-50a82f709753------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yqZpE11Z7NpQpamI.jpg</url>
            <title>Stories by Ian Bennett on Medium</title>
            <link>https://medium.com/@enbnt?source=rss-50a82f709753------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:42:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@enbnt/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[Filtered Thoughts]]></title>
            <link>https://medium.com/@enbnt/filtered-thoughts-ebffd1ce4f0b?source=rss-50a82f709753------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebffd1ce4f0b</guid>
            <category><![CDATA[filters]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[software-design-patterns]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Ian Bennett]]></dc:creator>
            <pubDate>Tue, 28 Nov 2017 15:53:15 GMT</pubDate>
            <atom:updated>2017-11-28T15:53:15.284Z</atom:updated>
            <content:encoded><![CDATA[<p>In a previous <a href="https://medium.com/@enbnt/art-and-engineering-6a0cb96c8eeb">post</a>, I started to discuss the relationship between art and engineering in my life. In this post, I’m going to drill into a simple, but powerful concept: a filter. Whether you are a Software Engineer, Data Scientist, Musician, Photographer, Digital Artist, or <strong>Coffee Drinker</strong>; you’ve used filters. In this post, we will discuss</p><ul><li>Filter Basics</li><li>Digital Signal Processing: A Quick Intro</li><li>Pedal Board: A System of Filters</li><li>Pedal Board: A Distributed Systems Thought Experiment</li></ul><p>Warning: this will be music/audio heavy and will use my bass and a pedal board as a working example of building more complex textures using filters. Each section builds upon the other, but you can skip or sample as necessary.</p><h4>Filter Basics</h4><p>Let’s start with a simple example. Say we have a filter that expects numbers to pass through it and we want to filter out even numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*N-CJB5BLWFtVjAQYd3yc4Q.png" /><figcaption>numbers -&gt; remove even numbers-&gt; result</figcaption></figure><p>[1,2,3,5,7,9,12,13,16] -&gt; remove even filter -&gt; [1,3,5,7,9,13]</p><pre>//Example Scala Code<br><strong>import</strong> com.twitter.finagle.{Service, SimpleFilter}</pre><pre>object RemoveEvenFilter extends RemoveEvenFilter</pre><pre>class RemoveEvenFilter extends SimpleFilter[Array[Int], Array[Int]] {</pre><pre>  def apply(<br>    request: Array[Int], <br>    service: Service[Array[Int], Array[Int]]<br>  ): Future[Array[Int]] = service(request.filter(isOdd))</pre><pre>  def isOdd(x: Int): Boolean = x % 2 == 1</pre><pre>}</pre><p>Maybe we want to introduce a power of 2 filter, where the number gets multiplied by itself. We know that we have numbers in and numbers out of our filters, which means that we can chain them together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*x0UY5fWoRlKKxow6Y6XVPw.png" /><figcaption>numbers -&gt; remove even filter -&gt; power of 2 filter -&gt; result</figcaption></figure><p>[1,2,3,5,7,9,12,13,16] -&gt; remove even’s filter -&gt; [1,3,5,7,9,13] -&gt; power of 2 filter -&gt; [1,9,25,49,81,169]</p><pre>//Example Scala Code<br><strong>import</strong> com.twitter.finagle.{Service, SimpleFilter}</pre><pre>object PowerOf2Filter extends PowerOf2Filter</pre><pre>class PowerOf2Filter extends SimpleFilter[Array[Int], Array[Int]] {<br>  <br>  def apply(<br>    request: Array[Int],<br>    service: Service[Array[Int], Array[Int]]<br>  ): Future[Array[Int]] = service(request.map(pow2))</pre><pre>  def pow2(x: Int): Int = x * x</pre><pre>}</pre><pre>//Service Filter Chain<br>numbers.andThen(RemoveEvenFilter).andThen(PowerOf2Filter)</pre><p>Cool cool cool. We can build upon this concept to modify our data in a bunch of different ways. In what ways is this applicable outside of playing with some numbers? Let’s say you were editing a digital photo and you wanted to tone down the amount of red in the image, you could create a filter to detect and modify red pixels. If you’re editing some audio files, maybe there’s some high pitched noise that’s distracting, you could isolate the frequency range of the noise and remove it. If you were hosting a web server that required people to authenticate with some credentials, you could create a filter to handle that.</p><p>Filters can be destructive (mutable) or non-destructive (immutable). We tend to favor non-destructive transformations so that you always retain the original source, which allows for being able to undo, redo, or modify the parameters that generate an end result.</p><h4>Digital Signal Processing: A Quick Intro</h4><p>Caveat: I wouldn’t consider myself an expert on Digital Signal Processing and tons of great material covering this topic in greater depth exists. Instead, here is a quick intro to help tie some of the concepts we’re discussing together. The Digital part of DSP requires that we take an analog signal, for example an instrument or a microphone, then do what’s called an Analog to Digital conversion. This process takes physical waves and samples them at fine grained intervals — CD quality Audio is 44.1k samples per second (44.1 kHz). What is being sampled is the amplitude of the wave, where the bit depth represents the amplitude of the wave — CD quality audio uses a bit depth of 16. CD quality is based off of the frequency spectrum humans can perceive as sound. The lower the sample rate and bit depth, the less natural and human sounding the result will be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*6Hfc_VjDWTqqRZmoBTdw3g.png" /><figcaption>Sine Wave, Sampled</figcaption></figure><p>Given those details about our digital representation of audio, if we want to implement a volume knob, for example, we could simply create a filter that would adjust the amplitude of each or the samples up or down. Mixing multiple tracks together *can be* as simple as summing the amplitude across each of the tracks.</p><p>In order to get back to the physical realm, a Digital to Analog conversion happens that reverses the process. This pushes sound out of your speakers. If you ever talk to a digital assistant like Siri or Alexa, you’ll be going through a AD and DA conversion. That process probably looks something like Microphone -&gt; AD -&gt; Speech to Text -&gt; Command Recognition Processing -&gt; Response -&gt; Text to Speech -&gt; DA -&gt; Speaker.</p><p>One thing to keep in mind is that AD/DA conversion isn’t perfect and can impact the tonal quality of a recording and what you hear. This is why professional studios invest in expensive microphones, mic pres, and audio interfaces with high quality converters. When I start talking about my pedal board, I’ll mention my Whammy pedal, which requires AD/DA and it impacts the tone of my instrument, so it’s only on when it’s needed. The Whammy pedal changes the pitch of the input and supports chords (more than one note voiced at once — t<em>his is made possible by using </em><a href="https://en.wikipedia.org/wiki/Fourier_transform"><em>Fourier Transforms</em></a><em>)</em>.</p><p>There’s much more I’d like to delve into on this topic and how it relates to observing distributed systems, but will save that for a future post. This is enough info to get you thinking about DSP and how the result of a complex system can be broken down into smaller building blocks.</p><h4>Pedal Board: A System of Filters</h4><p>A pedal board is built from a combination of discrete pedals. You could consider this a pallette of textures — or in our case, a system of filters. Each pedal requires an input and output signal of the same type. Some pedals will do some pretty complex transformations of sound internally, but each pedal in the signal chain requires an analog audio input and produces an analog audio output (at minimum, there may be other inputs and output types). This is the common interface that each of the pedals share and conform to, much like our code examples in the section on Filter Basics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ho4KNzZ46RtV046s3TmKWQ.jpeg" /><figcaption>Pedal Board — Picture</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F244603798&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F244603798&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F669043335_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/d0f12bb79ce086503b28938a7f6c5a0c/href">https://medium.com/media/d0f12bb79ce086503b28938a7f6c5a0c/href</a></iframe><p>In the above video, I have purposely made a few things visible. The top of the frame shows the wave form of the four tracks that I used to record:</p><ol><li>Speaking Mic (Vocal)</li><li>Direct Input (DI)</li><li>Tuner Pedal Bypass Output</li><li>Pedal Board Output</li></ol><p>You can see the impact of enabling different effects on the waves amplitude and form. The frame in the lower-left shows the frequency response of the overall mix, which also changes depending on what is enabled. The lower-right is the live view of the pedal board during the recording. There are physical and visual indicators for the state of each pedal (light is on when pedal is enabled, knobs change parameters, stomp switches enable/disable, etc). There’s a pretty rich visual language that’s been built up over decades, which I hope to dive into a bit more in a future post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*P4gGqe8O_m7E9n25cFDEmA.png" /><figcaption>Pedal Board Signal Flow Diagram</figcaption></figure><h4>Pedal Board: Text Description</h4><p>For accessibility purposes, here is a description of what you would see in the video and diagrams above. Feel free to skip this section or use it as a reference if you’ve observed the video and diagrams.</p><p>I have a clean signal from my bass into a DI (direct input) box, which feeds directly into my Audio Interface (a physical device that does AD/DA that lets me record on my computer) as a single input. This signal is untouched and clean — it’s a non-destructive signal that I can keep or blend if something is off with what goes through my pedal board. I then go into an MXR analog octave pedal, which allows me to drop the pitch of my instrument without running through AD/DA at the beginning of the signal chain. This pedal goes to my tuner pedal, which sends another signal out to my audio interface and to the other pedals on my board. The reason for this is that it’s really nice to have a clean sub-octave sound to blend into things, these are frequencies that go to a subwoofer and give the sound “boom” and the tuner pedal can turn on/off the rest of the pedal board with a single push. This then goes to a Whammy pedal (digital pitch shifter), which due to the AD/DA will change the tone of my instrument and is only turned on when absolutely necessary. The function of this pedal is made possible via Fourier Transforms — transformations between the time domain and frequency domain — another neat topic to investigate. This part of my signal chain makes up my “pitch shifting” portion, where the remainder adds color or character.</p><p>Next is an Xotix SP compressor. The compressor brings different frequencies in the signal closer to the same volume (compresses them). Next is an Ibanez Tube Screamer Mini, which boosts the volume of the input to the point of some minor distortion. Next is a TurboRat (probably my favorite pedal) that is a more aggressive distortion, with filtering of its own to color and add character to how the distortion reacts. Next is the Devi Ever Big Distortion Sound Machine, which is an even crazier distortion that has an almost synth like effect, because the distortion compresses the signal closer to a square wave. These 3 pedals make up the gain stage of my signal chain and boost and/or distort the clean sound.</p><p>Next up is the Walrus Audio Julia chorus pedal, which starts to make things sound like they’re under water a little bit. Finally I have a TC Electronics T2, which creates more ambient delay to the sound. I also have a Wah pedal that will sometimes come before or after the Chorus, but pretty much always before the delay. <em>Chorus, Reverb, and Delay serve similar functions by repeating the input signal, but at larger/varying time intervals. Despite that similarity, they sound and serve very different purposes from each other. Note: this section of my pedal board is not complete.</em></p><p>I have spent YEARS building this pedal board. I had started out buying a single multi-effets pedal in 2007, but eventually started to hit limitations in what I could do with it and the sound I wanted to get. I have been slowly adding a pedal at a time. I have taken the time to understand the function that each pedal plays in my system and what impact each has on the end result of my sound. If I had just gone out and bought every pedal at once, I wouldn’t even know where to begin with shaping my sound. When building up more complex systems, whether in sound or code, it’s easier to start simple and add complexity where necessary.</p><p>If you’re feeling up to the task, try to model the pedal board as a filter chain in code. Once you’ve got that in place, start to think about the different knobs, switches, and settings for each of the pedals and how that might change your code. Here’s a quick example snippet to think about:</p><pre><strong>import</strong> com.twitter.finagle.{Service, SimpleFilter}</pre><pre>/**<br> * Trait that allows a pedal to only modify the input<br> * signal when the pedal is not being bypassed<br> */<br>trait BypassablePedal[In, Out] extends SimpleFilter[In,Out] {</pre><pre>  val bypass: AtomicBoolean = new AtomicBoolean(true)</pre><pre>  override def apply(<br>    in: In,<br>    service: Service[In, Out]<br>  ): Future[Out] = bypass.get() match {<br>    case true =&gt; service(in)<br>    case false =&gt; service(modifySignal(in))<br>  }</pre><pre>  /** <br>   * Method that will modify the input when pedal isn&#39;t bypassed<br>   */<br>  def modifySignal(in: In): In<br>}</pre><pre>class SubOctavePedal(<br>  dry: Knob,<br>  growl: Knob,<br>  girth: Knob,<br>  midPlus: TwoWaySwitch<br>) extends BypassablePedal[Signal, Signal] {<br>  <br>  override def modifySignal(in: Signal): Signal = dropOctave(in)</pre><pre>  /** Modify input signal based on pedal&#39;s knob settings */<br>  def dropOctave(in: Signal): Signal = ???</pre><pre>}</pre><h4>Pedal Board: A Distributed Systems Thought Experiment</h4><p>Now let’s try a thought experiment and treat the pedal board like a set of <a href="https://en.wikipedia.org/wiki/Microservices">microservices</a>. Start by asking a few questions:</p><ul><li>How many services do you need? One? One per ‘section’? One per pedal?</li><li>What drives a change in the number of services?</li><li>What do you measure to know when that should change?</li><li>What problems are introduced by adding more services or pedals?</li></ul><p>Observability: The way that I have my signal routed to my audio interface allows me to observe the input and output of my system at a few key places. I can technically intercept the output of every pedal, but being able to do this is beyond my budget and having too many knobs/levers to mix introduces overwhelming complexity. I have the ability to trace and debug when something goes wrong by re-wiring the system. I can isolate individual pedals/cables to determine if something is causing a problem and I can dynamically enable/disable each feature in the signal path. My setup gracefully degrades — as long as my instrument is making a sound, the clean signal should be making it to a speaker somewhere, even if the rest of the pedal board is busted.</p><p>Let’s assume that every pedal is a service. Suddenly, we’re having issues with the output and we have over 10 different points of failure to look at. What steps would you follow to find the culprit?</p><ul><li>What was the most recent thing that changed when the issue started?</li><li>Can we get back to a previous good state by working backwards (turn features on/off)</li><li>Isolate where the problem is by measuring the input and output of each individual system</li><li>Remove pieces of the system that aren’t needed or in use</li><li>Test the cables!</li><li>Test the audio interface</li><li>Test the input/instrument</li><li>soooooooo much more</li></ul><p>Now, what if I told you that you’re only recording a single song at a time and that running the software equivalent of this pedal board should run easily on a single machine, with much lower latency, and less chance of failure? Was it worth the effort and the hassle? You need to reach a certain level of scale or have certain requirements to make the investment worth it.</p><p>The more complicated the setup, the more you need to understand. This requires having the ability measure the behavior of the full system, subsystems, individual components, connections to those components, and how each component impacts each other. The more knobs there are to turn, the more complex understanding the problem and getting the intended result becomes.</p><p>If you start to think of this in terms of software and distributed systems, there are some striking parallels.</p><ol><li>Keep it simple! Don’t introduce complexity if you don’t need it, it only makes solving problems more difficult</li><li>Make small, incremental changes</li><li>Test individual components — Unit and Functional Tests</li><li>Test how components interact with each other — Integration Tests</li><li>Reproducing an issue may be difficult — having the input that caused the issue to replay through the system can help make debugging easier</li><li>Don’t trust anything — a bad cable, loss of power, operator error, etc can all cause unexpected issues and shouldn’t be ruled out</li><li>Prepare for failure — expect that something won’t work and have a backup plan in place</li><li>Tracing, collecting, and understanding everything all of the time can be expensive and overwhelming —context is key, figure out how to collect and surface the MOST relevant information</li><li>Known and standardized interfaces make it easier to build more complex systems from simple, re-usablecomponents (see TCP, HTTP, JSON, thrift)</li></ol><h4>Closing Thoughts</h4><p>My hope in writing this is to get you thinking about how you might find inspiration in your hobbies and everyday things. Tech is an industry that loves to make problems sound really complicated. Most of the job is spending time breaking down complex issues into simple, modular, re-usable solutions. Also, understand that most situations don’t call for the added complexity of a pedal board OR distributed systems (I truly hope never both). It’s best to figure out what fills your requirements. If you don’t need them to solve your problem, you‘ll just have a really expensive, flashy thing, that’s going to cause you more pain and headache than starting simple and expanding as the need arises.</p><p>I hope that this was enjoyable and maybe a little informative. Thank you for giving this a read and would love to hear feedback. I look forward to continuing this theme in future posts, as time allows. <em>Special thanks to @herval and @chickenbellyfin for volunteering comments and feedback to make this post even better!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebffd1ce4f0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Art and Engineering]]></title>
            <link>https://medium.com/@enbnt/art-and-engineering-6a0cb96c8eeb?source=rss-50a82f709753------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a0cb96c8eeb</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[theory]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ian Bennett]]></dc:creator>
            <pubDate>Sat, 16 Sep 2017 03:40:12 GMT</pubDate>
            <atom:updated>2017-09-16T03:40:12.048Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently wrote a Twitter thread that started off as a joke about my abysmal earnings from a music album I released a few years ago. As I took the time to crunch some numbers, I realized it’s highly unlikely that someone can make a living off of streaming music sales. In fact, you will probably be in debt and never recoup the time or energy put into crafting that piece of art. The problem is that art is undervalued and I wanted to shed some light on how my hobbies actually make me better at my job.</p><h3>Ian Bennett on Twitter</h3><p>Always fun checking on my music album sales. I&#39;ve finally surpassed making $1 on streaming listens. Probably starting a new album soon.</p><p>I’m going to focus on experience with music, but I could easily write this about photography (maybe in another series) and the content should translate to other art forms or even sports. Midway through writing this, I realized that there’s way too much to discuss in a single blog post and I’m going to break this up into a multi-part series. This post will focus on some of the basics and how they translate to my day job and subsequent posts will go a little more into the collaborative, physics, DSP, and business aspects that correlate more directly with being an engineer on Twitter’s Observability Team.</p><h4>Practice and Basics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/204/1*LLd3UbaL7-eOb5bxmdBN9Q.png" /></figure><p>Western music theory has existed for thousands of years, amongst other world music theories. Western foundations were influenced and studied by some familiar names: Pythagoras, Plato, and Aristotle. Due to having such a rich history, there are systems and methods in place to aid in the understanding and communication of musical concepts. I was lucky enough to attend a public school with a music program to gather the basics of music theory in classical and jazz music. Outside of a few private lessons, which were of tremendous value, I was self taught at playing bass in the pre-YouTube era.</p><p>There are a few key concepts that lay the foundations and help speed learning. The structure of a (basic) song is made up of a key, time signature, and tempo, where the chord changes, rhythm, and melody live within these boundaries. Some of the big take aways from learning to play and honing my craft are:</p><ul><li>Go slow to go fast</li><li>Find common patterns to simplify the complex</li><li>Push yourself outside of your comfort zone to grow</li><li>Analyze the work of others you admire</li></ul><p>Taking the time to apply myself to art and learn these concepts has helped me excel at being a Software Engineer. Let’s take a look at why that’s true.</p><h4>Go Slow to Go Fast</h4><p>In music, this is building muscle memory and making your movements and mind more efficient. This is playing scales, arpeggios, trying to break down sections or difficult transitions by literally slowing down what you’re doing. You can slow down the tempo to isolate and analyze inefficiencies, then slowly push yourself to go faster until you are where you need to be.</p><p>As an engineer, this is like trying to write code before you understand what the code is actually supposed to do. You have to slow down and take a step back to understand the intent or edge cases of a problem. You can write tests (maybe you do some TDD or BDD) to get a grasp of what the expected behavior is. You need to understand the scope or impact of your changes in the grand scheme of a project. You should assess</p><blockquote><em>Where are things going? Does this way work? Is this physically possible?</em></blockquote><p>If you don’t take the time, you are bound to stumble and faulter. You need to slow down and re-adjust (i.e. debug, refactor, add coverage, instrument metrics, add logging, try distributed tracing, profile) to get to where you expect to be. You can’t go fast or gain velocity until you understand the areas of weakness. Once they are addressed, you will be on track to attain your goals.</p><p>However, even when taking time to work on improving, it is possible to push too hard and hit a wall. Progress will stop. Sometimes stepping away for a while, clearing your head, and picking things back up later is the best way to move forward. This is true in any problem solving endeavor. If I get stuck on a difficult problem at work, if I have the opportunity to pick up a bass and fiddle for a little bit or maybe hit the gym, I can usually get past a mental block or have a fresh perspective on an issue. Other times just grabbing some sleep is best. Everyone is different, find something that works for you.</p><h4>Find Common Patterns to Simplify</h4><p>Most music follows a common form and structure. There are exceptions to the rule, but knowing the rules and when to break them is part of the creativity and fun of art. A song will have a key and time signature that the entire band will follow. Within that key, you will have different modes or chord changes that can move the song along. Scales and arpeggios can help build a melody on top of that structure. Every key is built from tones made out of a common pattern of half and whole steps — if you learn this pattern and how to shift it, you can unlock every key. With string instruments, it’s really easy to see the “shape” of chords, scales, etc and see how to shift them to different keys.</p><p>That’s just the basics, as we go deeper, other patterns emerge. There are common and frequent chord progressions within a scale that convey movement or “tension and release” within a song. I-vi-ii-V and I-IV-V chord progressions are littered throughout western music. The entire Blues style of music has the same set of chord changes in EVERY song, but humans have been connecting to those sounds for YEARS.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpmwQ_WNTwXE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpmwQ_WNTwXE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpmwQ_WNTwXE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4593356c5ad0880ab4051cdc408e5b99/href">https://medium.com/media/4593356c5ad0880ab4051cdc408e5b99/href</a></iframe><p>With programming, you will see common patterns. You will find common themes between programming languages, libraries, etc that will help you understand and access new information. Design Patterns in Software are an obvious comparison; a set of reusable solutions that reoccur in common application problems. You will also see patterns in the design of distributed systems for handling stateful or stateless systems. We will learn from our mistakes and update “best practices”, but in general over time you will see common themes in how systems get built. Even when the new hotness comes along, seeing how your existing knowledge relates to unfamiliar technology can help make new information more accessible.</p><h4>Get Out of Your Comfort Zone to Grow</h4><p>Of course, there will be times when you can’t or shouldn’t try to draw parallels between different things. You will need to try to learn something new that isn’t in your comfort zone. This will help you grow and will help reveal other areas that you might not have been as strong as you thought you were. You need confidence to be successful, but sometimes you need to be knocked on your ass to raise your ceiling of success.</p><p>When I started out learning music, I really picked up playing simple parts quickly. I needed to keep pushing myself. I would spend 3 hours a day, every day, just trying to improve what I was capable of doing. I distinctly remember hearing Jaco Pastorius’ “Portrait of Tracy” and thinking that there was no way that one person could play that on a bass on a single track in a single take. I thought it was just a recording trick, but still beautiful. Then I saw that it was just him and his bass, making sounds that I had never heard come out of the natural range of the instrument. I HAD to learn this song, so I went to work and challenged myself.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=http%3A%2F%2Fwww.dailymotion.com%2Fembed%2Fvideo%2Fx4nq8g&amp;src_secure=1&amp;url=https%3A%2F%2Fwww.dailymotion.com%2Fvideo%2Fx4nq8g&amp;image=http%3A%2F%2Fs1.dmcdn.net%2FVS3e%2Fx240-o3g.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dailymotion" width="480" height="360" frameborder="0" scrolling="no"><a href="https://medium.com/media/a12fc7ae111428d0a536743df4e7b754/href">https://medium.com/media/a12fc7ae111428d0a536743df4e7b754/href</a></iframe><p>Sometimes you need to be inspired. Other times you just need to be in a vulnerable place where you’re willing to grow — expand the realm of the possible. I know that I’m not always right and can occasionally underestimate the creativity and capability of others. Knowing that I have to put myself in a place where I can learn and accept that I was wrong or that I never would have tried to approach something a certain way without some external influence is how I grow. This is what diversity and inclusion is all about to me, getting the best ideas and best results to put forward something greater than the individual.</p><p>This is also a reminder to stretch your skills from time to time. Pick up a new library, service, methodology, or language and try it. See if there is something that you can learn or incorporate into what works for you and your team. Taking on grand challenges might not be reasonable to do all the time if you’re a professional, but the key is to try to make time for it somewhere. You will never stop growing or being challenged, embrace it.</p><h4>Analyze Other’s Work</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*-MLCIDkpC6fQQoLe-HCHow.png" /><figcaption>Autumn Leaves — Lead Sheet</figcaption></figure><p>As part of learning to play, you have to learn some songs. Some times you’ll have things notated and written out for you, maybe you’ll only have chord changes and a melody (lead sheets are common in Jazz Ensembles). Other times, you’ll have nothing. It will be up to you to transcribe the parts you are hearing. Learning the techniques used by people you admire, for example understanding which chord progressions evoke certain feelings, will help you grow.</p><p>I learned how to break down a song before really delving into programming and getting a formal education in Computer Science. I think that this skill has helped me immensely in my day to day. I’m frequently faced with improving or understanding code that someone else has written, without comment or context. I’ll have to make tweaks to Open Source libraries that I’m not familiar with. My brain follows a similar process in trying to understand the intent, motivation, and how all of the pieces fit together. Being exposed to this kind of abstract analysis and problem solving from a young age has been invaluable.</p><p>My career arc has followed a similar path to how I started analyzing and transposing compositions. I was initially <strong>given</strong> tasks and tried to pull as much information as I could from those more senior to me. I would see how they approached problems and try to incorporate what works and learn lessons from what didn’t. Gradually, you gain more autonomy and ownership with fewer clearly defined tasks. Then you need to <strong>discover</strong>. Understanding what has come before you will help you find where to go — build on the shoulders of giants.</p><h4>Closing</h4><p>The moral of the story is, there is value in learning and experiencing new and different things. Dismissing arts and humanities is a mistake. The perceived value is much lower than it should be. There are intangible benefits that have improved my quality of life and helped me cope with hard times. Music has afforded me opportunities that I wouldn’t have had from a low income household (and a low ranked school system)— I had the chance to go to Italy and play Jazz in Pompei. I sang Bach in German to a French mass at St Peter’s Basilica in Vatican City. I wouldn’t have achieved the success I’ve had in my career or heightened my analytical skills without music. Maybe, instead of focusing strictly on the technical, take some time to pick up a new hobby or dabble with the arts — it might teach you more than you were expecting.</p><p>Keep on the lookout for the following parts of this series 😁.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a0cb96c8eeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monitorama PDX 2017]]></title>
            <link>https://medium.com/hackernoon/monitorama-pdx-2017-447de3c815e7?source=rss-50a82f709753------2</link>
            <guid isPermaLink="false">https://medium.com/p/447de3c815e7</guid>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[monitorama]]></category>
            <dc:creator><![CDATA[Ian Bennett]]></dc:creator>
            <pubDate>Sun, 28 May 2017 05:23:07 GMT</pubDate>
            <atom:updated>2019-05-24T11:42:10.945Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ian Bennett on Twitter</h3><p>I&#39;m in Portland for the first time! Can&#39;t wait for @Monitorama</p><p>Hi everyone, getting through a lot of firsts this week:</p><ul><li>First time in Portland</li><li>First time at <a href="https://hackernoon.com/tagged/monitorama">Monitorama</a></li><li>First time speaking at Monitorama</li><li>First time speaking at a conference</li><li>First time I was solo on stage since my high school talent show (a bass solo featuring Jimi Hendrix’s “Purple Haze”)</li><li>First blog on Medium</li><li>First time publicly sharing details of things I’ve worked on</li></ul><p>That last bullet point is something I have really wanted to change. The reason I haven’t so far is partly due to my career being comprised of projects that I couldn’t publicly talk about and partly because I wasn’t sure I had much to contribute to the conversation. If I’m going to say something, I’d rather there be a high signal to noise ratio. Given the quality of speakers and content at Monitorama this year, it was an honor and a joy to be able to get out there and share some of my/our experiences.</p><p>As a little background, I wasn’t one of the initially chosen speakers. I had already purchased tickets and was really looking forward to attending. Jason reached out to me a little over a month before the event because a speaker slot had opened up and my CFP was highly ranked. I jumped at the opportunity, but also knew that I needed to get to work pulling a talk together.</p><p>I had been meaning to setup an internal class on JVM profiling for a while, so I gathered some content on some of the issues we had seen within the <a href="https://hackernoon.com/tagged/observability">Observability</a> Team. I highlighted how to use our stack to find where problems were and how drilling deeper using profiling tools allowed us to resolve those issues. I went a bit deeper on what each of the features of the tools allowed you to do and how it made the discovery process a little simpler. I also wanted to highlight some of the issues that I’ve run into in my ~10 years of doing this kind of work. That was the basis for my Monitorama talk and I tried to distill things to the more interesting pieces for public consumption. I hope to work with my team to write up a tech blog where we can go a little more in depth in those areas. My teammates were incredibly supportive and really helped improve the quality of my presentation, I couldn’t have done this without them. This post will focus more on my thoughts and experiences, less on the technical side.</p><h3>The Conference</h3><p>I’m not sure I could have enjoyed the talks more. It was also great getting to connect with the other speakers and attendees. The speakers dinner and treatment by the organizers is worth the nerves of submitting a CFP. It was really cool being able to catch up with people, talk openly about some of the issues we are facing, and consider where things are going.</p><p>I left feedback for all of the speakers and others have left some great notes on highlights. I could spend all day listing out what I pulled from each talk — and there was something that should have sparked some thought from every speaker — so I’ll stick to some high level things.</p><ul><li>People are important, be good to them and be good to each other</li><li>Context and discoverability are important and there is a massive gap in our existing tools</li><li>User experience is paramount to success</li><li>Big players invest in infrastructure and Observability, but all have a different take on a solution</li></ul><p>If you weren’t in attendance, you might not be aware that the second day of the conference was majorly impacted by a power outage. There was an underground electrical fire that took power out for a day to multiple blocks surrounding the venue (including my hotel room). This was following Alice Goldfuss’s talk, which referenced Centralia, PA (a town that contains an underground coal mine fire that has been burning since 1962). The event organizers pulled some miracles and everything continued on schedule, despite a venue swap on Tuesday.</p><h3>Ian Bennett on Twitter</h3><p>Glad I don&#39;t have to follow @alicegoldfuss at @Monitorama. Talk was 🔥 and full of truth</p><h3>Speaking</h3><h3>Ian Bennett on Twitter</h3><p>Waiting back stage</p><p>Prior to speaking, I felt confident enough in myself, as I had done a few practice sessions in my hotel room. Unfortunately, I also had less than five hours of sleep pretty much every night for the week leading up to my talk. There were a few things I intended to touch on but missed, along with some mistakes. Once I was on stage, there wasn’t much thinking going on. Pretty much everything out of my mouth was adrenaline or instinct, so I’m glad I left the few speaker notes that I did. I know with experience this will get better, more comfortable. I had the benefit of being in a “lower pressure” spot, given that I was the first speaker after lunch on the last day. I also knew that I could just put everyone into a lull for the rest of the conference, so some pressure back up lol.</p><h3>Jeff Schroeder on Twitter</h3><p>Peeling the onion to observe applications&quot; @enbnt #monitorama</p><p>I said “umm” and “uhh” way too many times. When I referenced Julia’s presentation, I could have used a better transition (what I meant was to “build on top of”, in the moment “complex” was what popped out of my mouth). My font size was a little too small in some slides — I’m working on getting those slides out. I should prefer more bold text and speak to fill in the details, as opposed to filling pages with text.</p><h3>amy nguyen (in PDX) on Twitter</h3><p>I had to remove a bunch of this for legal reasons, so here&#39;s a picture of my cat.&quot; -@enbnt #monitorama 😹</p><p>Fml, I said “you guys” when asking about the poll to Open Source our stack 😣. Unfortunately there’s no edit button on a live performance. No one pointed this out to me, but I noticed while re-watching my talk for critique. This was completely unintentional and something I was consciously trying to avoid prior to the talk. I wanted this to be inclusive and it’s something I have to work out of my vocabulary. I’m certainly not perfect and will continue to work to try to better myself. I can only hope to have the opportunity to continue to build on these mistakes.</p><h3>Brant, tho on Twitter</h3><p>Here&#39;s @enbnt showing #monitorama how they introspect on G(ood) C(at) pauses at Twitter</p><p>I also meant to touch on the fact that my talk actually branches out from previous Twitter talks at Monitorama.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F173704290&amp;url=https%3A%2F%2Fvimeo.com%2F173704290&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F580187021_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/f110651405e46e25177e9833b2dfa226/href">https://medium.com/media/f110651405e46e25177e9833b2dfa226/href</a></iframe><p>Caitie’s presentation last year was discussing on call burnout and how to address those problems. At the end, she touched on our indexing service as starting to result in more pages. That was the same service I discussed during the final case study.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F173607647&amp;url=https%3A%2F%2Fvimeo.com%2F173607647&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F580158115_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/39e0f0d3274937e87843b5390fed1ae1/href">https://medium.com/media/39e0f0d3274937e87843b5390fed1ae1/href</a></iframe><p>In my first example, the service that’s diving is part of our Mon 2.0 stack, which Megan, Justin, and Dan talked about last year. The lingering hosts that were falling over less frequently are caused by a lack of balance in how expensive rules/queries are evaluated. This is something Dan discusses in that talk as keeping the solution simple. Which is how you SHOULD approach the problem — introduce complexity as necessary and to solve a known issue.</p><h3>Jeff Schroeder on Twitter</h3><p>Your bitmap xor bit shifting super efficient string dedup object pooling concurrent set is awesome!&quot; @enbnt #monitorama</p><p>My hope when sharing my presentation was to give a more realistic view of what issues we encounter. It wasn’t meant to be a sales pitch or to sell a specific tool, as these issues should cross cut and the approach should be generally applicable. It was also meant to show just how much is missing from getting from a dashboard or alert to resolving an issue. These problems take expertise and experience to diagnose (or prevent from entering your systems in the first place). I work with some extremely intelligent people, we all still make mistakes. My days aren’t filled with profiling — I spend most of my time working on architecting solutions, delivering new features, researching new ideas, clearing out tech debt, refactoring cruft, code reviews, documentation, on-call, support chat, communications, etc, etc. Profiling and performance analysis is an invaluable tool that everyone should have in their toolbox.</p><h3>Vistara on Twitter</h3><p>Avoid the urge to make too many changes at once. You need to measure the positive and negative impact of each change&quot; @enbnt #monitorama</p><p>I want the experience of all of our consumers to improve time to resolution, which is difficult to quantify accurately. I would also prefer that others don’t have to repeat some of the same mistakes or issues we’ve resolved.</p><p>This leads me to the Open Source poll. I was thrilled with the response. It wouldn’t be worth trying to do if a community wasn’t willing to build around it. We will see where things go from here and I’m looking forward to discussing with everyone who has reached out.</p><h3>Ian Bennett on Twitter</h3><p>Hey @Monitorama, should Twitter Observability</p><p>If you missed it, you can watch my talk here:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fo_8EsyFWal0%3Fstart%3D19742%26feature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Do_8EsyFWal0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fo_8EsyFWal0%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/65e3867ac2d3eb09d3aa0713ce4f7827/href">https://medium.com/media/65e3867ac2d3eb09d3aa0713ce4f7827/href</a></iframe><p>Thanks for reading and thanks to Monitorama for such a fantastic experience. See everyone at Monitorama 2018? Now back to packing to move and catching up on rest 😎.</p><h3>Ian Bennett on Twitter</h3><p>When you get sat next to a fellow @Monitorama speaker on your flight home #SpeakerSelfie</p><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a>family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>To learn more, <a href="https://goo.gl/4ofytp">read our about page</a>, <a href="http://bit.ly/HackernoonFB">like/message us on Facebook</a>, or simply, <a href="https://goo.gl/k7XYbx">tweet/DM @HackerNoon.</a></blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=447de3c815e7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/monitorama-pdx-2017-447de3c815e7">Monitorama PDX 2017</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>