<?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 Breki Tomasson on Medium]]></title>
        <description><![CDATA[Stories by Breki Tomasson on Medium]]></description>
        <link>https://medium.com/@BrekiT?source=rss-691afdcf3f06------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*WSwE2OebgXKeZL6e.jpeg</url>
            <title>Stories by Breki Tomasson on Medium</title>
            <link>https://medium.com/@BrekiT?source=rss-691afdcf3f06------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:24:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@BrekiT/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[Sorting Your Output Files Using iFlicks]]></title>
            <link>https://medium.com/@BrekiT/sorting-your-output-files-using-iflicks-49147eafb86d?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/49147eafb86d</guid>
            <category><![CDATA[file-server]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[iflicks]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Sat, 17 Sep 2022 10:07:39 GMT</pubDate>
            <atom:updated>2022-09-17T10:09:28.344Z</atom:updated>
            <content:encoded><![CDATA[<p>Here’s a quick little post about something that’s helped me a lot when it comes to organizing my fairly massive collection of movies and television series using a handful of <a href="https://iflicks.app/">iFlicks</a> rules. If you’re not already familiar with iFlicks, and if you’re using macOS as your default operating system, you owe it to yourself to familiarize yourself with iFlicks — it’s without a doubt the best application in its category.</p><p>The problem I had was that the root directories of my movie and television collections was quickly growing larger than was manageable, and I wanted to subcategorize them somehow. I first thought about using genres, but there are so many ambiguous cases where a movie or television series spans multiple genres, so that wasn’t a good option. A second idea was to sort movies by studio and shows by broadcasting network; but that still didn’t quite solve the problem — now I just had a small handful of directories that grew very large. The final answer was as simple as it was obvious — just create 27 new folders; one for each letter of the alphabet and one for “0–9”, then sort the movies and series into the corresponding folder based on the first letter of the first word of its title.</p><p>I quickly realized, however, that this would lead to two folders in particular becoming disproportionately large. “A” and “T” would be filled with titles starting in “A”, “An” and “The”, so my new rule was “The first letter of the first word of the title unless that word is ‘A’, ‘An’ or ‘The’, in which case we use the first letter of the second word of the title”. This proved far more useful, so I wrote a series of rules for it in iFlicks to save me from having to sort things manually. I’ll use the version for movies as an example, as the version for television series looks very similar. It looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1w1aUli5TDx1j7xKCN7-pA.png" /></figure><p>The first two lines make sense to anybody, but that last one requires you to understand something called RegEx, or <a href="https://en.wikipedia.org/wiki/Regular_expression">Regular Expressions</a>, something we developers use quite often — but usually not often enough that we still need to head on over to <a href="https://regex101.com/">regex101.com</a> when designing new rules just to make sure they work as intended. Basically, what this rule is saying is the following:</p><ul><li>^ Start looking at the name from the very beginning.</li><li>((The|A|An)\s)?) Look for the word “The”, “A” or the word “An” followed by a space (represented in RegEx by \s), but don’t require this to be there (represented in RegEx by ?)</li><li>(‘first_letter’\w) Look for any word-related character and remember it as first_letter …</li><li>{1} … but only grab the first one you see.</li></ul><p>What this means is that if the movie was <em>The Shining</em>, the rules would start at the beginning, then match “The” and the space after it, and then remember the first letter of “Shining” as first_letter. If, however, the movie was <em>Fletch</em>, the rule would start at the beginning, notice that the optional ((The|A|An)\s) rule did not get a match, and move ahead to the second part of the regular expression, storing the F into first_letter.</p><p>The second part to this rule is fairly simple, you just have to use first_letter when defining where to store the output file. For me, the rule looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxovPR5-mMia7Z_0jqSnAQ.png" /></figure><p>Note that each of the blue fields (which iFlicks calls <a href="https://support.iflicksapp.com/hc/en-us/articles/201113447-Using-Tags">tags</a>) can have their own settings, and I’ve set them as follows:</p><ul><li>first_letter: Uppercase</li><li>Name: Clean</li><li>Release Date: Year</li></ul><p>The first setting means that a television series like <em>iZombie</em> would correctly be sorted under a folder I rather than get its own folder named i. The second setting ensures that characters that are usually not handled well by various file systems are stripped from the file and directory name. The final setting ensures that the output file ends up in a folder that contains the year the movie or series was released.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49147eafb86d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fixing That Pesky “Method Not Found” in your Laravel Models]]></title>
            <link>https://medium.com/@BrekiT/fixing-that-pesky-method-not-found-in-your-laravel-models-d6a47a14aeea?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6a47a14aeea</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Thu, 25 Aug 2022 15:26:01 GMT</pubDate>
            <atom:updated>2022-08-25T15:30:25.983Z</atom:updated>
            <content:encoded><![CDATA[<p>We’ve all been there, right? You’re in your IDE, writing a Controller method or something like that, and you’ve hardly finished writing your where() statement when that dreaded yellow line pops up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*t_x9SFO3AA9Na_P8AieNKQ.png" /></figure><p>As with most things in life, there are more than just one solution to this, and it all boils down to your personal preferences. Let me go through the three most common ones and the pros and cons with each; then you can pick for yourself.</p><h4>Install the Laravel IDE Helper Package</h4><p>This is most likely going to be the first suggestion you come across when looking around for the answer, and it’s not a bad one. Barry’s done an amazing job on the <a href="https://github.com/barryvdh/laravel-ide-helper">Laravel IDE Helper</a> package, and it’s not surprising to see that it has close to 50 million installations at the time of writing.</p><p>What this package does is essentially scan through your codebase, focusing on things like Models and Facades where there’s a bunch of “magic” going on, and generates a separate file for your IDE to index.</p><p>I like the simplicity of this solution, which is why I have it listed first. For most people, this will likely be the best way to solve things. It does the job, it does it well, and — for the most part — it gets out of your way and lets you focus on the code.</p><p>However; it might be argued that you’re essentially “tricking” the IDE by creating this file, and that it shouldn’t be necessary to do so if everything was set up properly, and these are definitely good arguments to make. Personally, I don’t like having a package generating a huge file for me that I don’t have insight into. I’ve also had issues in the past where Cmd-clicking a method in my IDE didn’t bring me to the method’s “actual” definition, but instead brought me to the method’s location in the IDE Helper file. This can likely be confusing for some developers.</p><h4>Using PHP DocBlocks</h4><p>Now; this method is definitely a little bit more “hacky” than installing the Laravel IDE Helper package, but it has a couple of additional benefits you might appreciate — as well as some downsides, as we’ll see.</p><p>Essentially, what you can do is create a new model called App\Models\Model and have it look something like this:</p><pre>&lt;?php<br><br>namespace App\Models;<br><br>use Illuminate\Database\Eloquent\Builder as EloquentBuilder;<br>use Illuminate\Database\Eloquent\Model as EloquentModel;</pre><pre>/**<br> * @mixin EloquentBuilder<br> */<br>class Model extends EloquentModel<br>{<br>    // Nothing here.<br>}</pre><p>Then, whenever you create a new Model, you simply extend this class instead of the base class. That little @mixin line in the DocBlock tells your IDE that whenever it’s checking what methods are made available by this class, it should automatically include all the methods made available by Illuminate\Database\Eloquent\Builder as well.</p><p>Creating your own custom Model class like this has some other benefits too, of course. For example, you can add methods here that you want to be available in all of your own models, and the IDE will automatically pick up on them, which is something that can’t be said when you take advantage of the Macroable trait. One such method that I’ve created is this one:</p><pre>public static function findAndCache(int $id, string $value = &#39;name&#39;) : mixed<br>{<br>    $tag = str(static::class)-&gt;lower()-&gt;afterLast(&#39;\\&#39;)-&gt;toString();<br><br>    return Cache::tags(&#39;model_cache&#39;)-&gt;remember(<br>        &quot;${tag}.${id}.${value}&quot;,<br>        now()-&gt;addWeek(),<br>        static fn () =&gt; self::find($id)?-&gt;{$value},<br>    );<br>}</pre><p>This then allows me to do things like User::findAndCache($userId, &#39;email&#39;) or BlogEntry::findAndCache($entryId, ‘title’) for any one of my models, knowing that the results are stored in the cache the next time I need them.</p><p>The biggest problem, however, is that any Model that is added by a third party will be extending Laravel’s own Model class and not your own, so this @mixin DocBlock won’t do you any good there. It’s also a fairly “hacky” way of getting around the core problem and doesn’t play nice with the way Laravel wants you to do things.</p><p><a href="https://github.com/laravel/framework/discussions/43858">I’ve posted the idea to add this DocBlock</a> to the Laravel Framework’s own Model class, so let’s keep our fingers crossed that future versions of Laravel take care of this “out of the box”.</p><p>Until then, one way you could work around this issue inside your IDE is …</p><h4>Taking advantage of the query() method.</h4><p>Whenever you’re creating a query against one of your models, instead of writing User::where(&#39;country_id&#39;, 23)-&gt;get(), you can can squeeze in the query() method, making it User::query()-&gt;where(&#39;country_id&#39;, 23)-&gt;get() .</p><p>Under the hood, the query() method does little more than return a Builder instance for the given Model, meaning everything that comes after query() will be correctly interpreted by your IDE to be a method inside of Builder rather than Model .</p><p>While this may feel a little clunky at first, it quickly becomes second nature and makes your code that much more clear. Also, when you’ve got a long block of chained methods in your queries, having User::query() as your first line, with all the -&gt;where() lines stacked neatly below it actually makes things a lot easier to read.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6a47a14aeea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2020 – The Year of Utility]]></title>
            <link>https://medium.com/@BrekiT/2020-the-year-of-utility-89828a917b2c?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/89828a917b2c</guid>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[yearly-theme]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Mon, 13 Jan 2020 17:18:53 GMT</pubDate>
            <atom:updated>2020-01-13T17:18:53.054Z</atom:updated>
            <content:encoded><![CDATA[<p>For more than a decade now, I’ve maintained a habit of assigning myself short, time-constrained challenges. I’d follow a vegan diet for a month, do no fewer than fifty push-ups per day for 50 days, avoid the words ”is”, ”am”, and ”be” (The ”Is of Identity”) for a week, etc. It’s basically a system for trying out new habits and routines to find what has the most positive effect on my mental and physical health. Some things stick, others don’t, but either way I’ve given myself the opportunity to try something new.</p><p>For the past two years, I’ve also followed the advice of Myke Hurley and CGP Grey on the Cortex Podcast and implemented a yearly theme into my routine as well. Unlike New Year’s Resolutions, which tend to have several problems, a yearly theme tends to be just a single word which then becomes a cornerstone in any major decision-making during that year.</p><p>Let’s take a look back at 2019 to explore the theme I picked for that year and how it turned out.</p><h3>2019 – The Year of Fewer</h3><p>I defined 2019 as ”The Year of Fewer”. Both 2017 and 2018 had been very stressful years for me, so the overarching theme of 2019 was going to have to be something to help me find more calm in my life. I had already identified – to my surprise – that the stress i experienced had little to do with the actual amount of work being done, but was more closely tied to the amount of different responsibilities and expectations that I had. Knowing that I had to perform a dozen simple tasks, none of which would take more than 10–15 minutes, seemed far more daunting than having the single task of preparing a presentation to be held in front of a hundred people.</p><p>2019, then, would be the year where I eliminated as much as possible from my life that wasn’t directly connected to the small handful of areas that I designated as core to my being. In most areas of our lives, the hardest questions have to do with whether to leave or to try harder. In 2019, I decided, I would default to leaving.</p><p>Some things were easy to implement and gave immediate results. Before 2019, I could spend hours of my day browsing social media and keeping up to date with political news, tech news and the two-dozen-or-so TV series I followed. That’s all changed now. I have next to no presence on social media any more, and no longer feel that pressing need to stay on top of everything happening in the world.</p><p>My relationship to Apple’s Worldwide Developer Conference, WWDC, is a great example. June 4th to June 8th, 2018, saw me glued to three screens, following the live broadcasts, various live-bloggers and a number of Twitter hashtags in real time. I was absorbing pure data, obsessing to the point where I even adjusted my sleep schedule to be in sync with California.</p><p>A year later, half way through my Year of Fewer, a friend asked me what I thought about the preview images of Dark Mode on iOS, and I honestly didn’t know what he was talking about. His ”They announced it at WWDC last week!” could only be met with a ”… there was a WWDC last week?”</p><p>While social media and gluttonous news consumption were both relatively easy to eliminate, there were other things that proved far harder to drop. I announced the closing of CSICON, the podcasting network that I had managed and been the chief contributor to since 2011. I dropped a number of extremely interesting programming projects that were all in the category where another 200+ hours of work might have made them a marketable product or provided use and enjoyment for hundreds or thousands of people. But I knew I had to drop them – my ambition has always been greater than my ability, and 2019 taught me that sometimes the best response to a great idea is just to share it and hope somebody else has the ability to run with it.</p><p>But The Year of Fewer wasn’t just a good thing, and I’ve been able to identity a couple of areas where I think the pain of the loss outweighs the reduction of stress. I don’t like being reminded of all the people I lost touch with in 2019. I still feel very guilty over how rarely I met my sister and her family during 2019 - and how often my visits were cut short because I had to hurry home to the dogs or to put in my hours on one of the small amount of projects that made the cut.</p><p>I also hate the state of my apartment. I had started a couple of renovation projects between 2016 and 2018, and anything that was unfinished at the start of 2019 was just left in that state.</p><p>Another bad habit that I’ve developed as a result of adopting the mindset of the Year of Fewer has to do with my attitude towards the small inconveniences that pop up every so often. For example, my personal identity card was set to expire in the end of September, and I kept putting off scheduling an appointment with the tax agency to have it renewed. When I finally got around to it, they had a waiting period of several weeks, so I would have to go three weeks without a valid ID before the meeting, and then whatever extra time it would take for them to actually provide me with the card.</p><p>But when the day came for me to go to my meeting, I had a horrible migraine and had to stay at home. It’s been more than three months since my ID expired and I still haven’t gotten around to scheduling a new appointment. My mind has so firmly embraced the perspective that if it isn’t both important and urgent, just drop it and never think about it again, even if it’s just a question of taking a few minutes out of my day and just doing it. The same kind of thinking has punished me on several occasions, where the smallest of mundane things fall to the side and disappear when it would be so easy to just getting it done.</p><h3>New Year, New Meme</h3><p>All of this brings us to the present day. I spent a lot of time during my winter holiday thinking about the Year of Fewer and where it’s brought me. More importantly, I’ve spent a lot of time thinking about what comes next, finally landing in the somewhat unclear theme of ”The Year of Utility”. I’ve had a hard time putting it in words, even to myself, but I have a strong and distinct feeling associated with the word. Here’s the best way I’ve found to describe the feeling.</p><p>Most of the things we do in our lives can be divided into two categories based on what it is that motivates us to do those things. We thus have intrinsically motivated actions and extrinsically motivated actions. An intrinsically motivated task is done for its own sake, it is somehow rewarding in and of itself.</p><p>When I come home from work late in the evening and find myself sitting down for what turns out to be an eight-hour session of Minecraft, I’m doing it with the most intrinsic of motivations. I’m not creating anything of value, but I’m enjoying my time spent in a universe of blocks, challenging myself to build clever redstone contraptions and more and more intricate mob or resource farms.</p><p>Conversely, when I sit down to work on the codebase of TankerTrackers.com, I’m doing so for the most extrinsic of motivations. This is the category of tasks we perform in order to get some kind of future reward or avoid some kind of punishment.</p><p>Obviously, some activities find themselves being in both categories, sometimes more of one that the other, but sometimes right there in the middle. A person who loves running might be able to rationalize the cardiovascular benefits, the extended lifespan, the improvement in metabolism, etc. – and these things might have been the reason they started in the first place. But they also know that none of these things are on their mind when they strap on their running shoes at half past five in the morning – they do it because they derive joy from the act itself.</p><p>As with most typologies, this is a great oversimplification. Upon any analysis, it becomes obvious that there are several things in our lives that we do in order to facilitate other tasks that, in turn, are intrinsically or extrinsically motivated. Now, it can <em>absolutely</em> be argued that these tasks are extrinsically motivated; we do them for the reward of being able to something else later, but it’s hard to deny that there is a categorical difference here. It’s from this perspective that I posit a third category; in addition to intrinsically and extrinsically motivated actions, I suggest actions motivated by their utility.</p><h3>Putting the Pieces Together</h3><p>This is what the entire post has been leading up to. The Year of Utility, interpreted with all the information that we’ve gathered so far, is going to be a year when I focus not on doing the actual work, but on <em>making the work easy</em>.</p><p>It’s an often-quoted phrase in programming; ”For each desired change, make the change easy (warning: this may be hard), then make the easy change” (originally by Kent Beck). This, in essence, is what I am going to be attempting to implement into my entire life this year.</p><p>For example, if my goal were to have a more consistent habit when it comes to eating meals, the difficult change would be to try to force myself to eat on schedule. Making that change easy could include things like ensuring that I’m not randomly scheduled to do things that collide with the time set aside for eating, ensuring I have food available, making sure that I’m not snacking and losing my appetite, etc. With those smaller ”utility” changes in place, the real change becomes that much easier.</p><p>Wish me luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89828a917b2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[That’s a Wrap!]]></title>
            <link>https://medium.com/@BrekiT/thats-a-wrap-9565b6804bc4?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/9565b6804bc4</guid>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Thu, 03 Oct 2019 09:27:54 GMT</pubDate>
            <atom:updated>2019-10-03T09:27:54.489Z</atom:updated>
            <content:encoded><![CDATA[<p>As many people have noticed and pointed out in the past few weeks and months, the CSICON podcasting network never really came back after its summer lull. People have been asking about when their favorite podcasts will be coming back, despite it becoming increasingly obvious that they won’t be.</p><p>For reasons as diverse as they are many, we have decided to wind down CSICON as of the end of the year. The podcast archive will remain available until New Year’s Eve, with services like Patreon and our public Slack being gradually closed between now and then.</p><p>The cast and crew of CSICON are all creative types and will continue to create content on the Internet. After New Year’s Eve has come and gone; the contents of the CSICON website will change to contain links to the various projects that we undertake online, so that you can continue to follow the people you’ve grown to know over the years.</p><p>Finally; on behalf of myself, the other podcast hosts, the writers and the crew, I would like to extend our sincerest gratitude to our audience of this past decade. Your feedback, comments and questions throughout the years have made this journey into so much more than just a hobby.</p><p>Thank you for everything.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9565b6804bc4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Broadening My Horizons]]></title>
            <link>https://medium.com/@BrekiT/broadening-my-horizons-6eb5fcef85b7?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/6eb5fcef85b7</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Thu, 16 Nov 2017 18:41:02 GMT</pubDate>
            <atom:updated>2017-11-16T18:41:02.298Z</atom:updated>
            <content:encoded><![CDATA[<p>I wouldn’t call myself a coder.</p><p>Don’t get me wrong, I spend more waking time writing computer programming code than any other activity, but I don’t identify as a coder. If anything, I would probably identify more as a <em>developer</em>, since what I spend the most amount of time on is figuring out the best systematic approach to solving a problem or automating a task. The coding is just a way to realize that part of it.</p><h3>The Old</h3><p>During my childhood, I played around with BASIC on the Commodore-64, batch scripting in DOS, some Pascal and some Visual Basic. This is all in the 80s and 90s, and none of it ever stuck. It wasn’t until I was playing around with web design and web pages that I found myself learning PHP, more or less by accident. I’d set up a Wordpress installation — this must have been back in 2005 or 2006 — and wanted to change a couple of things. I didn’t even know what PHP was at the time, I just played around with the code and slowly started figuring things out.</p><p>And that’s where I was for the longest time. About a year ago, I decided I should probably focus on programming a bit more, since it was going to be a very useful skill for me to have. There were just too many situations where I was reliant on friends for developing things that I’d thought up, and I figured it would be far more efficient to just learn to do it myself. I set myself the task of solving last year’s Advent of Code — and did so using PHP.</p><p>Obviously, PHP is not the language of choice for anybody who wants to do this sort of thing, unless they’re doing it as a way to give themselves a self-imposed challenge of sorts. It’s a little like giving yourself the challenge of building a table, but only allowing yourself to use a saw and a screwdriver as tools — no hammer, no water level, no glue, no ruler. You can probably get it done, but you<em> know</em> there would be better ways to do it.</p><p>At the time, I didn’t know this. I mean — I understood that there were people out there writing their solutions in Python, Ruby, Go, C, NodeJS, and all the rest of them, but I didn’t quite have the perspective to understand what it all meant.</p><p>Earlier this year, I got involved in a project that had me diving deep into PHP, and I’ve got to say that my skill in that language has grown by leaps and bounds. I don’t furrow my brow any longer when I read PHP, and I’m writing lines like PortCallHandler::setObjectOlderThanTwo($object-&gt;portcallscan_at-&gt;addDays(2)-&gt;gt(Carbon::now()); regularly enough for it to feel like second nature.</p><p>But the more I worked with it, the more I felt hampered by the limitations of the language. There is no native way of working with JSON in PHP. Defining the return type and input type for a function feels like an afterthought hacked onto the language after the fact. Even the === operator, which is supposed to compare two things to see if they are identical, still compares strings as if they were integers. There’s even a `mysql_real_escape_string()` function in there, since the original `mysql_escape_string()` function was buggy… The language is case sensitive in some places, case insensitive in others. It just goes on and on, and the amount of small hacks that I’ve had to write just to handle the weirdness of PHP is larger than I had hoped it would ever be.</p><h3>The New</h3><p>As serendipidy would have it, I was exposed to NodeJS in two different places at almost the same time. One was for a thing I’m developing at work, and one was for a thing I’m developing for a personal project. The language felt pretty foreign initially, and the asynchronous nature was confusing to me at first, but there was just something that … clicked, for lack of a better word.</p><p>My PHP brain would have iterated through an array to extract all array items which had a ‘value’ set to ‘true’ in a way that looked something like:</p><pre>$result = [];<br>for ($i = 0; $i &lt;= count($array); $i++) {<br>  if ($array[$i].value === true) {<br>    $result[] = $array[$i];<br>  }<br>}</pre><p>My new NodeJS brain approaches the problem differently, and I see the answer to the solution in a way that more resembles:</p><pre>let result = array.filter(function (item) {<br>  return item.value === true<br>})</pre><p>… There’s just something to be said about the elegance when comparing the two. And while I understand that callbacks exist in PHP as well, they’ve always felt like an afterthought — not the native way of doing PHP. In NodeJS, however, they’re there because they have to be. The asynchronous nature of the system demands it.</p><p>I still have a long way to go with NodeJS, but it feels like I’ve reached beyond my skills in PHP in about a month of playing with it. I keep looking for new and interesting things to do with it, and am building all kinds of exciting small modules to teach myself more.</p><p>I’m sure the world can’t wait for my Sean Connery module, which translates any string you insert into Sean Connery’s pronounciation of that same string. It’s going to be <em>huge</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6eb5fcef85b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Conflict in Politics]]></title>
            <link>https://medium.com/@BrekiT/my-conflict-in-politics-8c4e062a6553?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c4e062a6553</guid>
            <category><![CDATA[taxes]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Tue, 14 Nov 2017 16:37:10 GMT</pubDate>
            <atom:updated>2017-11-14T16:37:10.402Z</atom:updated>
            <content:encoded><![CDATA[<p>For as long as I can remember, I’ve identified with classical liberalism as my political perspective of choice. For those not familiar with the idea, think “life, liberty and property”, rather than “life, liberty and the pursuit of happiness”. Think small government, freedom of choice and minimal government intervention. It’s a political perspective that has always worked for me, and I’ve been able to defend it, both to myself and others, in any political discussion that I’ve ever found myself in.</p><p>Now; I understand that there is no “being correct” in politics, and that it’s all a question of preference. Just like no person can have the “correct” taste in music, movies, clothing or hobby, there are no correct choices in politics. The closest we come to being correct comes down to looking at historic examples of your politics being realized and making a judgment based on whether or not it works. This is why we keep getting the “But that’s wasn’t <em>real</em> communism!” from people who espouse a left-wing political perspective but can’t point to historical examples where it actually worked. That’s why we get “That’s because of external factors that she had no control over!” when people point to Thatcher’s England as proof that Conservatism doesn’t work.</p><p>So since I’ve accepted that my political standpoint is opinion, not fact, I’ve always been open to being swayed by other standpoints, and I’ve never been the kind of person that mocks people of different perspectives just because I don’t agree with them.</p><p>And today was one of those times. For various reasons, I’ve had to restrict my budget slightly for the past month or two, and expect to have to do so for another month or two. It all boils down to one unexpected large expense, and I just haven’t caught up with myself yet.</p><p>So when I went to the pharmacy today, to renew three of my prescriptions, I was understandably worried. I’m sitting on about $250 until I get paid in just under two weeks, and I’m running out of dog food. That’s gonna be about $80 just there, and I have to watch every penny.</p><p>I left the pharmacy with a plastic bag containing sixty tablets of Amphetamine and ninety tablets of Modafinil — well over a month’s worth of medication for my ADHD and my hypersomnia. I paid less than $15 for all of it.</p><p>Imagine that. Fifteen dollars. I regularly buy dinner for more than that. I’ve spent more than that on energy drinks in a single day. My medication cost me the equivalent of <strong>one day’s worth of doggy daycare for just one of my two dogs</strong>.</p><p>Now; I understand that had I not been taxed as heavily and had to pay full price for my medication, I would probably have had more money in my bank account at the end of every month. I would probably have been able to deal with the unexpected large expense a bit better. In total, my personal benefit from the taxes that I pay is probably smaller than the actual sum that I pay every month.</p><p>But I realized something today. The taxes that I pay give me more than just the direct benefits of the things that the government steps in and pays for. The taxes offer me an intangible which is so much larger and more important, something which is worth <em>more</em> to me than the money that I’m paying.</p><p>The taxes that we pay here in Sweden mean that <strong>there are so many things that I don’t have to worry about any longer</strong>. I don’t have to stress about what might happen if I lose my job, because I know there are safety nets. I don’t have to worry about what might happen if I fall ill, because I know that the healthcare will be taken care of for me. I don’t have to worry about my dodgy shoulder/neck situation getting worse, because I’m getting physical therapy twice a week for free. I don’t have to worry about running out of medication for my ADHD or hypersomnia, because it’s all taken care of for me. It means my friends with sick children or sick parents don’t have to worry about the cost of healthcare.</p><p>That peace of mind that taxes affords is an invisible force multiplier that I’ve discovered is so much larger than the cost of the actual products and services that I get in exchange for being a heavily taxed citizen. It doesn’t mean that I’m suddenly loving taxes and want to pay more — quite the contrary, there are several things that my tax money go to that I don’t feel are defensible, and I still believe that taxes could be reduced and that certain things could be done far better by the private sector … but it’s hard to ignore the benefits.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c4e062a6553" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Back Into It]]></title>
            <link>https://medium.com/@BrekiT/getting-back-into-it-e015e2f4b4d4?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/e015e2f4b4d4</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Thu, 06 Jul 2017 08:54:58 GMT</pubDate>
            <atom:updated>2017-07-06T08:54:58.825Z</atom:updated>
            <content:encoded><![CDATA[<p>For as long as I’ve remembered, I’ve been a fairly novice PHP programmer. You know the type — skilled enough to make some modifications to a Wordpress theme and build some fairly basic things, but not good enough to really make a difference. You don’t have to go back further than a year and a half to get to a point where the most impressive code I was writing was something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/649ccde0d3293a152203ccb5506f472f/href">https://medium.com/media/649ccde0d3293a152203ccb5506f472f/href</a></iframe><p>… Yeah; not very impressive at all; I know.</p><p>This all changed just three months ago, when an old friend of mine brought me on board a project that he was working on. You see; he was operating a website with a friend of his that was gaining some serious traction, and the design and interface was solidly stuck in the 90s. He brought me on board mainly to clean things up and make it a little bit more presentable — but it turns out that rabbit hole goes a lot deeper than I expected it to.</p><p>So even though I’m writing this site in PHP instead of one of the other more powerful — and probably more suitable — languages, I’ve ended up in a situation where I’ve been able to embrace the language in brand new ways. I’ve learned dependency injections, I’m instantiating objects. I’m building models, factories and interfaces. It’s at the point now where every single function in the entire codebase — which now spans a total of 3500 lines of code across around 50 files — has been rewritten at least once as I get back to it a few weeks down the line, having learned so many new things along the way.</p><p>What used to be a simple if/elseif/else morphed into an if/elseif/else with return trueand return false attached to them. They then changed to more legible and more optimized ternary operations. Who wants to read if ((isset($variable)) &amp;&amp; $variable ≥ 41) { $variable = $variable + $AnotherValue; } when we have the alternative $variable += $variable ≥ 41 ? $AnotherValue : 0; ? Who wants to manually craft SQL queries which &quot;SELECT * FROM TableName WHERE &quot; . $inputVariable . &quot; = &quot; . $inputCriterion . &quot; LIMIT 20&quot; when they could be using an ORM which allows them to database::table(&#39;TableName&#39;)-&gt;where($inputVariable,$inputCriterion)-&gt;limit(20) instead?</p><p>I still feel like I’m scratching the surface here, and I have so much left to learn — but the progress I’ve made in the past three months alone are so much larger than the three years that came before it. I’m having so much fun working on this project that I just <em>know</em> that I’ll be jumping right into the next one once crunch time is sover.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e015e2f4b4d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Apple Great Again]]></title>
            <link>https://medium.com/@BrekiT/making-apple-great-again-38b55dc1b021?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/38b55dc1b021</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[future]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Sun, 09 Apr 2017 22:49:53 GMT</pubDate>
            <atom:updated>2017-04-09T22:49:53.205Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past week, more than half of the podcasts that I listen to have talked about the recent news that Apple is rethinking their Mac Pro line and will be coming out with new hardware in 2018, effectively ending the line of Mac Pro they introduced a few years ago. In the words of Craig Federighi, Apple had ”painted themselves into a thermal corner” and the interesting black ”trashcan”-design just isn’t feasible moving forward.</p><p>The entire thing has had me wondering about Apple’s line of products, where everything fits and how things belong. And I keep coming back to one of the things Steve Jobs did when he came back to Apple in 1997.</p><p>At the time, he – like so many – felt there was too much choice and too little to differentiate the various choices. So, what he did was to scale everything back to four products, arranged neatly on a grid. In a simple two-rows-two-columns table, he had laptops on one row and desktop computers on the other. In the columns, he had standard and professional. It made so much sense – you want a laptop, so you pick the standard or pro version. If you want a desktop computer, the same question applies. Simple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*dKPXT1XHq18n0ARvkKgOrA@2x.png" /></figure><p>Today, the situation is a little bit different. There are more products than just a desktop and laptop. The iPhone comes in two sizes, and a third if you’re okay with slightly older hardware. There are multiple types of iPad, and the Macbook line is as confusing as ever. People need to juggle concepts like Air, Mini, Pro – all in addition to various sizes. It just won’t do in the long run, and I think they know this too.</p><p>What I suggest is that Apple go back to their roots and simplify every line to follow a common naming and grouping standard – and here’s how I think that should work:</p><h4>The Mac</h4><p>This one is simple, since it requires the least amount of real change. The Mac should be brought into – or kept in – the following categories:</p><ul><li><strong>Mac Mini</strong>: Keep it more or less as-is, but put it on a more regular update cycle. Nothing major, just a yearly refresh of CPU and other relevant innards.</li><li><strong>Mac</strong>: Rename the iMac to being just ”The Mac”, and offer it in 21, 24 and 27-inch versions. SSD only, with maybe three separate Drive space, GPU, CPU and RAM choices each, bringing us to 243 different combinations. For simplicity, keep the same setup of ports on all.</li><li><strong>Mac Pro</strong>: Whatever it is they’re making now, I suppose.</li></ul><h4>Macbook</h4><p>The Macbook line wouldn’t change much either, but it would be consolidated into three separate and clearly defined product lines:</p><ul><li><strong>Macbook Mini</strong>: 13 and 15 inch models, lightweight and available in three metallic colors. Two USB-C ports for charging and extension. Fairly limited selection of choices in terms of drive space, CPU, RAM, etc.</li><li><strong>Macbook</strong>: Like the Mini, but with more ports and a slight bump up in terms of available choices and customization. This should be your run-of-the-mill laptop for everyday users who just want a laptop that <em>works</em>. More ports, more extensibility, but nothing out of the ordinary.</li><li><strong>Macbook Pro</strong>: More powerful than the above, but now also available in 17-inch versions. No low-end CPU/GPU choices available. For the professional on the run.</li></ul><p>There shouldn’t be any difference in terms of features, functionality or specs within the different models, so a 13-inch Macbook Pro and the 17-inch Macbook Pro should be identical in <em>all</em> ways but size. The different models can be on their own update cycles, but should get at least a yearly spec refresh without a price bump.</p><h4>iPad</h4><p>I’m sure you see where we’re going here. The iPad would also get three separate lines, and we would get rid of all version numbering. In the future, one would only talk about ”the 2018 iPad”, not anything like ”iPad 5&quot; or the like. Each of these would be available in either WiFi-only or WiFi/Cellular models.</p><ul><li><strong>iPad Mini</strong>: Available in 7.9 and 9.7 inch versions that are <em>not</em> retina screens, this should be the lightweight option for schools, children, or for simpler tasks like browsing the web, e-mail and reading &amp; writing. Only available in one color, one RAM/CPU setup, etc. Only customizing should be three different levels of storage. No Bluetooth, just WiFi or WiFi/Cellular. No 3D Touch.</li><li><strong>iPad</strong>: The standard model; still just available in 7.9 and 9.7 inch versions, but the screen is now retina and the tablet is available in four different color choices – grey, silver, gold and rose gold. Still no CPU/RAM customization, just three storage options – but the lowest of these should be equivalent to the ”middle” option on the Mini. Not Pencil compatible. Has 3D Touch and Bluetooth.</li><li><strong>iPad Pro</strong>: Not available in 7.9 inches, just 9.7 and 12.9 inches models, retina screen and compatible with the Pencil. USB-C port added next to Lightning port for extension. High-end in terms of CPU and RAM, but no choices other than storage, which should start higher than the base model again.</li></ul><p>An important thing about the iPad, too, should be that there should never be a difference in terms of features, functionality or specs between different sizes of the same model. The different sizes of a model should always be revised at the same time – but the different models can be on their own update cycles. Spec bumps at least every 18 months.</p><h4>iPhone</h4><p>Okay, here’s the big one. The iPhone would lose all version numbering, so no more ”7s Plus” or the like. Instead, we get the following:</p><ul><li><strong>iPhone Mini</strong>: This would be a good old 4-inch model, similar to the iPhone SE. Not a retina screen, but it <em>would</em> be 3D Touch-enabled. The specs don’t have to be amazing, but good enough to be expected to be able run the most recent versions of iOS for the next three years.</li><li><strong>iPhone</strong>: This is the base model; essentially the same phone as is available now. No version numbering or ”Plus”, just ”The iPhone”, in either a 4.7 or 5.5 inch model that are <em>otherwise identical.</em> None of this ”Feature X is only available on the Plus version”. Which brings us to our final thing, and the only really <strong>new</strong> thing on the entire list…</li><li><strong>iPhone Pro</strong>: The iPhone Pro would only be available in 5.5 inch models, and have a considerably larger area of the front covered by screen. The bezel would be made smaller and the ”chin” on the phone would be reduced to the absolute minimum, even if that means reducing the home button to a small rectangle instead. This would be the phone to get the amazing new features that would previously be ”Plus only”. Like the iPad and other iPhone models, no choices in specs other than storage.</li></ul><p>Moving all of Apple’s products to this kind of setup would drastically reduce the complexity of choice and give the product series more focus. Since there would be no change in specs between sizes, you would be able to pick the device size from personal preference, not on which features you want. It would also allow Apple to maintain each of these lines independently of each other, putting them on their own refresh cycles and maintaining them as independent products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38b55dc1b021" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving Todoist]]></title>
            <link>https://medium.com/@BrekiT/improving-todoist-a9d48d52b12e?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9d48d52b12e</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[todoist]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Mon, 03 Apr 2017 11:48:14 GMT</pubDate>
            <atom:updated>2017-04-03T11:48:14.176Z</atom:updated>
            <content:encoded><![CDATA[<p>One of my favorite podcasts is <a href="https://www.relay.fm/cortex"><em>Cortex</em></a>, featuring Myke Hurley and CGP Grey talking about the methods and tools they employ to be productive and creative. It’s a subject that is near and dear to my own heart, since I also do a lot of thinking and talking about the very same subjects. It’s always interesting to hear other angles and perspectives on the same things.</p><p>As of <a href="https://www.relay.fm/cortex/46">a little over a month ago</a>, Myke began talking about making the move to <a href="https://todoist.com/">Todoist</a> as his new task manager of choice, having worked with Wunderlist and OmniFocus before that. This was especially interesting to me since I had made the same journey only about half a year earlier, from Wunderlist to Todoist.</p><p>A lot of the frustration that Myke started talking about on the show during the weeks and episodes that followed were pretty much the same kinds of things that had been on my own mind, so I would like to use this week’s podcast-inspired post to talk about the single biggest things that I think Todoist could do to improve their service — to the point that I would most likely never even test any of the alternatives that pop up in my quest for the <strong>perfect</strong> todo-application. I call it …</p><h4>Custom Repeat Rules!</h4><p>This is <em>hugely</em> important to me, and would be amazing if Todoist could implement. It works like this:</p><p>Some recurring tasks need to be done <em>before a due date</em>, whereas others need to be done at some point <em>after a given time period has passed</em>. Having the ability to separate between the two is often extremely relevant. It’s often not relevant to know the due date if it’s not something that can be crammed into a last-minute job — knowing the Start Date as well could give you a reasonable timeframe or when the task is “active”.</p><p>Let me give you some examples.</p><p><strong>Example one</strong>: Before the last Sunday of every month, I want my bills to be paid and any surplus salary to be moved into my savings account. To do this, I have two separate recurring tasks that both have a due date of the last Sunday of every month. It doesn’t matter if I finish them three days early — or even one day late! — they will still pop up with a new due date for the last Sunday of next month, because that’s how they’re configured.</p><p>Let’s call this type of recurring task a ”simple recurring task”. Todoist is great at this kind of thing. In fact, it’s kind of the only type of recurrence rule you can set up (with some modification, but more on that later). It’s the second type that I’m missing:</p><p><strong>Type two</strong>: I believe dental hygiene is an easy thing to maintain as long as you ensure a couple of habits and routines are in place. One of these is replacing your toothbrush every so often. I try to do so every three months, but I’m not strict about it. I don’t need a due date, really, but more of a <strong>start date</strong>. Every three months, I would like to be reminded that I should probably replace my toothbrush soon. Here’s how I magine it would work in Todoist:</p><p>After completing the task ”replace toothbrush”, a new task would appear with a <strong>start date</strong> (not a due date) that is 90 days after the current date. It wouldn’t appear on any of my lists unless I specifically request to ”display unstarted tasks” in my filter. Then, once the ninety days have passed, it just magically appears in my inbox and waits for me to complete it. Once I’ve completed it, it disappears again, for another ninety days after I completed it — not ninety days after it started.</p><blockquote>… Yes, I know about the <strong>Every!</strong> syntax, but that’s still just for due dates. This kind of thing needs to support start dates as well.</blockquote><p>Now, obviously this kind of functionality would require Todoist to make two separate changes to their software. One of them would be to give tasks an optional “start date” in addition to the already optional “due date”. The other would be to give us a selection for the criteria that recurring tasks center on; due dates or start dates. This will increase the complexity of recurring tasks, of course, but as long as they would default to the current mode and this be kept as an alternative for specific scenarios, that’s fine. It could even be baked into the task to be “start or end-focused”. That way, the <strong>Every!</strong> syntax could be used to recur based on completion based on either start or end, based on the task setting.</p><p>Here are a couple of ways that this could be used in practice:</p><p><strong>Example 1: </strong>My sister’s birthday is August 26th, and I would love to give her something great every year. Unfortunately, this often means that I’m cramming things last minute or feeling uninspired. Why not set up a recurring task that is due on August 24th every year with a “start date” 21 days earlier? That way, I wouldn’t see any indication that her birthday is coming up for most of the year, but as soon as August 3rd rolls around, the “Buy a birthday present for my sister” task magically appears. Once I’ve finished the task, it disappears from my life until August 3rd rolls around the year after.</p><p><strong>Example 2: </strong>I have a tendency to forget to do my laundry, and it piles up over time and leaves me wearing the most uninspired outfits until I can find it in my calendar to do the laundry. Using a system like this, I could simply set up a task called “Book laundry room, if needed” to repeat every fifteen days after the last instance of that task was completed. That way, it might appear in my list, I realize that it needs to be done, but am unable to schedule it at that moment — so I keep it in my “active tasks”. Two days later, I schedule my laundry, put the booking in my calendar, and complete this task — and I won’t see it again for another fifteen days.</p><p><strong>Example 3: </strong>I’m meeting a friend next Saturday evening, and I just <strong>know</strong> he wants to talk to me about the latest episode of some TV series we both follow. Problem is, the episode airs on Wednesday, and today is Monday. Why not set up a task with due date Saturday afternoon but with a start date of Thursday morning, since there’s no way I could see the episode before it even airs? That way, the event will appear in my list on the start date and not bother me until then.</p><p><strong>Example 4: </strong>I’m going to a business trip to London between May 11th and May 19th, and there are a couple of things that I’d like to see, buy or do when I’m there. Since it’s more than a month away, I know that I’d probably just forget it, so I add these things to Todoist. I put a start date of May 11th and a due date of May 19th, which means these tasks will be “active” during my trip to London and invisible to me before then.</p><p>All things considered, for Todoist to simply add the ability to assign “start dates” to tasks in addition to “due dates”, and then allowing recurring tasks to recur based on either the start date, end date or completion date, the product would go from Great to Never-Being-Replaced-Ever.</p><blockquote>This story is the first of my weekly podcast-inspired blog project, to be published every Sunday or the foreseeable future. <a href="https://medium.com/@BrekiT/writing-about-talking-3d32bea0f074">Please read more here</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9d48d52b12e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Growing Smaller]]></title>
            <link>https://medium.com/@BrekiT/growing-smaller-48378f0a6626?source=rss-691afdcf3f06------2</link>
            <guid isPermaLink="false">https://medium.com/p/48378f0a6626</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Breki Tomasson]]></dc:creator>
            <pubDate>Mon, 20 Jun 2016 00:51:35 GMT</pubDate>
            <atom:updated>2016-06-20T00:51:35.140Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the biggest problems that startups face is growing too big. It sounds strange, I know; everybody who launches a new product or service wants their thing to hit the ground running and just grow massive beyond everybody’s expectations, right? We all want to be an overnight success, quit our jobs and ascend to the heights of Internet stardom, right?</p><p>Let’s stop and think about it.</p><p>Think about your own day job, assuming you’re at a nine-to-five. Odds are you’re in a company that builds a product or a service. How many people in your company are there who <em>actually</em> build the product or service? We’re talking programmers, product managers and other kinds of developers. Then compare that to the list of people who work sales, marketing, human resources, management, finance, support, and so on. I’m guessing the first group is <em>far</em> smaller. This is going to be more true the longer the company has been around and the more successful it has been.</p><p>Compare that to a small startup. They’re hungry to get going. They’ve got maybe one or two people with a vision and some development skill among them. Their vision attracts a couple of other developers who want to tag along, and before they know it they have a product that attracts attention. They’ve been running on vision, pure and simple. Now, assuming they suddenly explode in popularity and find themselves attracting enormous amounts of attention, it all becomes a little bit more complicated.</p><p>When I founded the <a href="http://csicon.fm/">CSICON Podcasting Network</a> with my friend Petter, we had fairly small plans for where we were going with it. We enjoyed podcasts and podcasting, and wanted a place of our own on the web to put them. Only after a lot more people started joining our ranks and our listener numbers creeping past the hundreds, the thousands — the ten thousands! — did we begin to realize we had a success story on our hands.</p><p>CSICON has been fortunate to grow slowly, being able to meet every challenge that growth brings with it as we go, building new systems, implementing new architecture and expanding to new areas at a pace that matched our abilities. When we saw that we were growing out of the servers that hosted us, we were able to migrate to a new set of servers in a calm and orderly fashion. When we recognized the need for a way of simplifying the publication process, we didn’t have to jump through any hoops but just talked it through and found a new method that worked for us.</p><p>You see, the problem that growth brings with it is that you stop focusing on what it is you’re actually building — that thing that made you grow in the first place. Instead, you shift focus towards systems and structures whose only purpose is to coordinate the thing that you’re building. You stop building <em>products</em> and start building <em>processes</em>. You stop recruiting great <em>makers</em> and start recruiting great <em>managers</em>.</p><p>That imaginary small startup from a couple of paragraphs ago, the one with the overnight success; they’re going to have to make changes to cope with everything. From three or four bug reports a day before their explosion in popularity, they now get five hundred a day — they need to recruit support staff. From having a backlog of three or four feature requests, they now have fifty — they need to recruit more developers and people to manage them and organize who does what. From barely breaking even, they’re now pulling in tens of thousands of dollars a month — they need to recruit somebody for finance to make sure things stay above board. All of a sudden, this small, tight, lean startup isn’t following their vision any more — they’re following process, and that kills the vision.</p><p>So what’s the solution to this? Well; we could all try to chase slower growth. We could try to learn that there’s no such thing as an overnight success that lasts. For every single lottery winner out there, there are hundreds of people who grew their fortune slowly and securely. For every one-hit-wonder out there, there are hundreds of artists who grew their back catalogue slowly and securely. For every <a href="https://techcrunch.com/2014/08/08/anonymous-emailing-service-leak-shuts-down/">Leak</a>, the anonymous e-mail service that exploded in popularity and had to shut down due to the servers being unable to manage the load, there are dozens of other services that grow into their clothes over time.</p><p><em>Angry Birds </em>was Rovio’s 52nd game to be published. WD-40 is so named because they tried 39 other chemical compositions before they landed on WD-40. It literally stands for “Water Displacement — 40th Attempt”.</p><p>Grow slow, build a stable ground to stand on and never rush something just for the sake of growth. These are lessons that are difficult to learn as you hunger for the success you so desire. It’s so tempting, but it’s important to resist this one temptation.</p><p>I’m glad that <a href="http://csicon.fm/">CSICON</a> is growing slowly. I hope it continues to do so.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48378f0a6626" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>