<?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 Greg on Medium]]></title>
        <description><![CDATA[Stories by Greg on Medium]]></description>
        <link>https://medium.com/@glsignal?source=rss-1fff94497a70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*OrekXvAFTLlRNqvJ.jpeg</url>
            <title>Stories by Greg on Medium</title>
            <link>https://medium.com/@glsignal?source=rss-1fff94497a70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:57:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@glsignal/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[First international hire, 1 year on]]></title>
            <link>https://medium.com/alasco-tech/first-international-hire-1-year-on-67b63193def5?source=rss-1fff94497a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/67b63193def5</guid>
            <category><![CDATA[proptech]]></category>
            <category><![CDATA[relocation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup-life]]></category>
            <dc:creator><![CDATA[Greg]]></dc:creator>
            <pubDate>Thu, 11 Mar 2021 00:00:00 GMT</pubDate>
            <atom:updated>2021-03-17T08:52:40.432Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo of a passenger aeroplane landing at an airport at sunset, tinting the scene in warm light" src="https://cdn-images-1.medium.com/max/1024/1*_Be4yER3mb7s6CisyUF2Xg.jpeg" /></figure><h3>A year ago I moved to Germany, and joined Alasco</h3><p>My partner and I decided that we would move overseas to work and travel. This would be the first time living overseas for me, as well as my first time in Europe. Naturally we picked 2020 as the year to do this, and so we also faced the wrath of a pandemic along with the rest of the world. It has been a difficult and surprising first year in a new country, and in a new company as their first international hire. Surprisingly, given the circumstances, it has gone much better than you might think.</p><p>In late 2019 I signed the contract for my new job with Alasco. This was a big deal for me, as I had previously only ever lived and worked in my home country, New Zealand. This would be an opportunity to live and work in Europe at a growing company, and be able to travel with my partner in our vacation time. Come January, with visas and plane tickets in hand, we farewelled our families and began our journey to Germany.</p><p>On the 29th of January, we disembarked the plane and were in Munich, our new home. It was cold and early in the morning, we were tired, didn’t understand much German, and we’d never visited Germany or even Europe before. Even so, Munich was friendly so far and we made it to our accommodation easily and stumbled through the process of setting up SIM cards with the extremely patient ALDI employee. Then it was time to get rested and try to kick the jet lag, because tomorrow I’d be having a welcome dinner with the Alasco team.</p><p>I didn’t really know what to expect. I’d interviewed for a few different companies in Munich and Alasco had stood out as different even at that point. The people I’d spoken with so far had left an impression of warmth and support, so I was excited to meet everyone else! Through that first dinner, the first day at work, the first week, that impression never faded and is one of the defining characteristics of the team I’m now happy to be a part of. In the Product &amp; Engineering team, there’s a strong culture of openness and constructive honesty when it comes to feedback. Everyone is here to do good work, and continuously improve how they go about it. When the fortnightly retro comes around (we run scrum teams), there’s often an action or experiment to try something differently afterwards.</p><p>The experience of the founders and leadership team shows, too. One thing that surprised me when I first joined was how well organised the company is, especially given that it’s still young and fast growing. There’s just enough structure here, while still managing to strike a good balance with organisational flatness and flexibility. Roles are established as they are needed, or even slightly ahead, and people are given opportunities to move into these with plenty of support.</p><p>There has also been a good balance of work, and having good bonding time outside of a work context. I was lucky enough to join right before the annual ski trip: we all bussed down to the Austrian alps, donned our choice of snow gear, and hit the slopes. I was quickly brought up to speed about Après-ski during this weekend. Despite a minor accident and snowmobile ride down the mountain, it’s one of my fondest memories so far since moving here.</p><p>Then the realities of the pandemic became clearer and we went into the first lock down. About a month after I started, the company made the call that it was safest to stay away from the office, and we all became a remote team practically overnight.</p><p>We couldn’t just leave our accommodation without a good reason, and suddenly we were stuck in a box. This kind of situation makes integrating into a new place difficult, and it was disheartening to say the least. It’s difficult to reflect on the time after that, being in isolation for so long meant everything has blurred together. There were plenty of personal challenges along the way (hospital trips, booked-then-cancelled flights home) and we still had to navigate the bureaucracy to convert our visas into longer term work permits. It has been a difficult time since then, and continues to be. My partner and I have been isolating since the first lockdown, which is almost an entire year now.</p><p>At work, the culture adjusted to the new constraints. For context, the work culture I’d experienced then is one where we’d have a quick conversation in person and talk something through, then move on. That became a little different in a remote setting, as we now leaned heavily on chat tools and video calling. That meant we all started to learn about Zoom fatigue the hard way. At the same time, asynchronous communication started to happen more regularly to counteract the fatigue. It wasn’t a radical shift, but instead async communication started to appear as a way to support the existing communication styles and keep it sustainable.</p><p>Even though we were all remote and physically isolated, there were still good parts! We’ve been able to continue growing the team of frontend engineers at Alasco throughout this time. Helping develop an identity for “frontend at Alasco” has been rewarding. So far we’ve taken on initiatives to figure out how we want to work as frontend engineers, what processes we have, what standards we hold, and how we will keep in sync as we grow. We kicked off “forums”, our name for the group of engineers who practice a certain discipline within the engineering team. With that discipline-focused group formed, we’ve been able to coordinate and take on larger changes to Alasco’s frontend, even as we split into multiple product teams.</p><p>The team spirit didn’t fade either, but instead adapted to the new remote lifestyle. We have had plenty of team events, including a remote beer tasting, some lovely virtual dinners together, and a team cooking class to name a few. At the end of the year the whole company gathered for a Christmas party in the (Zoom) north pole, complete with gifts and Glühwein. I’d hoped to visit the Christmas markets and try, but doing this remotely with friendly faces is a good compromise.</p><p>Looking back, the past year has both felt like an eternity and vanished so quickly. It has been humbling, I’ve learned a lot about myself, and will continue to do so over the next years too. I’m endlessly grateful to the people around us who have helped with these difficult times. Though we’re not done with the pandemic yet, and life won’t return to normal for a long time, I’m hopeful about 2021 being better.</p><p>Maybe we’ll even see each other in the Biergarten some time, if at a distance.</p><p><em>Originally published at </em><a href="https://alasco.tech/2021/03/11/first-international-hire-1-year-on.html"><em>https://alasco.tech</em></a><em> on March 11, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67b63193def5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alasco-tech/first-international-hire-1-year-on-67b63193def5">First international hire, 1 year on</a> was originally published in <a href="https://medium.com/alasco-tech">Alasco Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Save your Trailblazer data]]></title>
            <link>https://medium.com/trailblazing-diaries/save-your-trailblazer-data-88972f145ab4?source=rss-1fff94497a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/88972f145ab4</guid>
            <dc:creator><![CDATA[Greg]]></dc:creator>
            <pubDate>Sat, 08 Jul 2017 20:41:21 GMT</pubDate>
            <atom:updated>2017-07-08T20:41:21.021Z</atom:updated>
            <content:encoded><![CDATA[<p>On July 31st, Trailblazer’s services will be taken offline permanently, and our Chrome extension will no longer back up your trail data.</p><p>We’ve recently issued an update to the extension which gives you an option to download and preserve your trail data.</p><h4>Downloading your trails</h4><p>When you’ve received the update, the popup menu will include a link to a new interface within the extension.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/207/1*YHXSCNRg_9150DUTjwIWag.png" /><figcaption>Screenshot of opening the Trailblazer extension menu.</figcaption></figure><p>Click this, and you’ll see instructions on how to export your data.</p><p>You’ll also see on this page that you can load these backups back into the extension and keep viewing this data even after our servers go down.</p><p>To be on the safe side, we suggest the following:</p><ol><li><strong>We recommend you first</strong> <strong>export “Your restored trails” </strong>(which is the 3rd option in the list). This saves the trail data currently in your Trailblazer extension to your Downloads folder .</li><li>Next, using the first option in the list, force your Trailblazer extension to load all the trail data we have for your account from our servers. There’s a risk it might overwrite some of your local data, which is why we recommend doing this step second.</li><li>Finally, with all your trail data loaded into Trailblazer, <strong>repeat step one</strong>. This time you might find the file is slightly larger than before as it contains all your trail data from our servers.</li></ol><h4>Developers</h4><p>The trail data files are JSON files containing an unmodified copy of the data from the extension’s IndexedDB stores. They are exactly what is used by the extension, so it should be friendly if you want to do anything with it. It contains two keys, which are lists of:</p><ul><li>Assignments (our internal name for trails)</li><li>Nodes (the pages you visit)</li></ul><p>They’re not linked up or nested in anyway in the backup, however the ID references should (assuming everything is synced correctly) be intact and usable if you wish to reconstruct the graph.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88972f145ab4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trailblazing-diaries/save-your-trailblazer-data-88972f145ab4">Save your Trailblazer data</a> was originally published in <a href="https://medium.com/trailblazing-diaries">The Trailblazing Diaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Nice Things, and the Baggage they bring]]></title>
            <link>https://medium.com/@glsignal/npm-install-headache-6fbe16541077?source=rss-1fff94497a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fbe16541077</guid>
            <dc:creator><![CDATA[Greg]]></dc:creator>
            <pubDate>Thu, 04 Dec 2014 01:09:05 GMT</pubDate>
            <atom:updated>2014-12-04T07:23:13.974Z</atom:updated>
            <content:encoded><![CDATA[<h2>$ npm install headache</h2><h3>Make sure you know what you’re getting</h3><p>It’s a simple process. Install a package, add it to a manifest, and hey — you’ve got the magic powers of open source at your finger tips.</p><p>I’ve been doing this a lot recently, with a <a href="http://trailblazer.io/">project</a> that has been undergoing a significant rewrite. As we move to a newer implementation, we’ve pulled in plenty of external dependencies, each with a specific purpose and value.</p><p>Suddenly I was having bad feelings every time a new dependency was introduced. Each one bringing with it additional baggage, and each time it left me wondering</p><blockquote>Do we really need that?</blockquote><p>I started to think about how all of these little, but compounding decisions were being made. How could we approach them without having the gut reactions?</p><p><em>This is clearly written in the context of programming, but it can pretty much apply to anything. Things have Baggage. Here are some thoughts on dealing with it.</em></p><p>Let me prefix this by saying there’s nothing inherently wrong with the situation — a Nice Thing was introduced, and made it easier to work with our data storage layer. This is okay. Happiness is an important part of a successful team. If you’re dealing with shitty APIs every day, it wears you down.</p><p>It raises a different issue, which is the maintenance overhead in keeping the Nice Things up to date.</p><p>What happens when one of the Nice Things is abandoned by its author or the community? We’re then left with a difficult decision on whether to clean up a bunch of stuff that relied on the Nice Thing, or maintain the Nice Thing. You might be saying to yourself, “just lock the version.” That’s fine — but to me it’s only a short term solution while you figure out how to rid your project of the necrotic mass.</p><h3>This doesn’t mean reinventing the wheel.</h3><p><em>And it certainly isn’t </em><a href="http://en.wikipedia.org/wiki/Not_invented_here#In_computing"><em>NIH</em></a></p><p>I’m usually against that school of thought. I feel as though it’s short-sighted when used as a justification for managing certain kinds of risk in technical projects.</p><p>It’s very easy to start building a Nice Thing and have everything Going Well while you’re in the moment. That breaks down as soon as someone else has to figure out what the hell is going on, and why Nice Thing was created instead of using Popular Well Maintained Thing.</p><h3>Ask yourself, “why?”</h3><p>Take some time to think about the benefits and the costs of using the Nice Thing. Ask yourself why you need it, and whether it really is the best tool for the job. I tend to ask myself</p><ul><li><em>Is it well maintained?</em></li><li><em>Is it widely used?</em></li><li><em>When was it last updated?</em></li><li><em>Does its owner have a vested interest in its existence?</em></li><li><em>What baggage does it bring with it?</em></li><li><em>Is it solving my problem directly, or am I using just a small part of it?</em></li><li><em>Does it need to be brought in right now, or can it wait?</em></li><li><em>How much effort is it going to take to get it working?</em></li><li><em>What happens if it disappears?</em></li></ul><p>Your criteria will inevitably change depending on the stage your project is at, too. If it’s early in the prototyping phase, you might be much more flexible about what can be used; speed is often the goal at this stage in a project’s life. Using the Nice Thing will get you to point B much faster.</p><p>If you’re working on a large, long-lived project the opposite is probably true. Speed doesn’t matter <em>as much,</em> whereas the maintenance cost of Nice Thing is more of an issue.</p><h3>Pick a good bed to sleep in, Goldilocks</h3><p><strong>But don’t be afraid to switch if it isn’t comfortable.</strong></p><p>Ultimately it’s you and your team that is going to be looking after the project. You should take the time to analyse and justify (even if only to yourself) why you’re bringing in moving parts, and what you’re really getting. Take time to critique these decisions further down the track, too.</p><p>Avoiding change because you’re past the point of no return (even though you probably aren’t) is bound to cause trouble in the long run. There’s a <a href="http://hbswk.hbs.edu/item/7007.html?wknews=05092012">great excerpt on the dangers of marginal thinking</a> which captures this, as well as the oft-cited <a href="http://en.wikipedia.org/wiki/Sunk_costs#Loss_aversion_and_the_sunk_cost_fallacy">sunk cost fallacy</a>.</p><p>You’re the best person to be critiquing these decisions, making sure they’re well-informed, and speaking up if something isn’t working. Just remember to be constructive when you do¹.</p><p>I’ve written this using Nice Things as a placeholder for code dependencies. This kind of decision making extends well beyond just code, though. Such things as communication methods, workflow tools, how you coordinate your team, and many other things are all fair game.</p><p>Things have Baggage. Just be mindful of whose baggage you’re dragging around the airport.</p><p>This is my thinking process. Feel free to get meta, critique, question, and improve on it. I’d like this to be a learning experience.</p><p><strong>[1]</strong> The <a href="http://www.mccarthyshow.com/online/">Core Protocols</a> (which hold some excellent ideas) have a protocol for decision making.</p><blockquote>Use Decider anytime you want to move a group immediately and unanimously towards results.</blockquote><p>Part of the Decider protocol states that if you absolutely oppose a proposed change, you may speak up immediately in opposition and should expect to be asked to suggest a better idea. The latter is, in my opinion, the most important part here. If you’re not able to give a better idea immediately, you can support it and propose the change later.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fbe16541077" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chicken Soup]]></title>
            <link>https://medium.com/@glsignal/chicken-soup-da3b9f942c25?source=rss-1fff94497a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/da3b9f942c25</guid>
            <dc:creator><![CDATA[Greg]]></dc:creator>
            <pubDate>Fri, 19 Jul 2013 02:31:22 GMT</pubDate>
            <atom:updated>2013-07-19T02:31:47.234Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z0OWQKscY2yjXrun.jpeg" /><figcaption>Many thanks to stray_croc over on Flickr — http://www.flickr.com/photos/stray_croc/</figcaption></figure><h4>Because you’re sick and #yolo</h4><p>Today I am what you would call sick.</p><p>This means I can’t really think quite properly, and hence, can’t do any meaningful work. Why I decided to turn this situation into fuel for writing this piece of literary genius is beyond me, but here we are.</p><p>Anyway, let us get back to the issue at hand.</p><h3>Chicken Soup</h3><p>This is part recipe, part ramble, and is directed at anyone who happens to be sick (or, for those model citizens out there, knows someone who is sick) and requires nourishment in the form of delicious Chicken Soup, who simply will not settle for tinned or pouched posers.</p><p>I suppose it would be prudent to start off with some ingredients. For this particular concoction, you’ll need the following</p><ul><li>Water — 250ml</li><li>Chicken Stock — 500ml</li><li>Chicken — around 150g, cooked &amp; shredded</li><li>A large flat mushroom — cut to your desired size</li><li>An abnormally large carrot (or two regular ones) — cut as above</li><li>One tin of creamed corn — 440g</li><li>Dried herbs to suit your tastes — I used sage, oregano and thyme</li><li>A <em>little </em>butter, for softening the carrot/mushroom</li></ul><p>Of course this is <em>your</em> soup, so chop and change the components as you see fit — be a bit of a rebel. The above is just what I happened to put into mine.</p><p>Start off by combining and heating up the stock and water in a pot. Make sure it’s not a small pot as, like me, you will end up transferring the soup to a larger pot and feeling like a goose due to your poor judgement skills. Once the stock is beginning to simmer, add the chicken and set the heat such that it remains at a simmer without requiring too much attention.</p><p>While this is warming up (which may take a while if your stove is as terrible as mine), acquire a chopping board and sharp knife and deal to the mushroom and carrot. When you’re satisfied with the amount of cutting you have just achieved (with your superior knife handling skills), heat up a skillet with the butter and herbs.</p><p>When this is melted and smelling <strong><em>amazing</em></strong>, add in your mushroom and carrot and soften these. You might be tempted to add more butter as mushrooms do tend to drink it up, but be forewarned: doing this will submit you to a buttery deluge once the mushrooms submit to your relentless heating, which is less than ideal.</p><p>Add the softened vegetable mix as well as the creamed corn to the pot containing the stock and chicken. From here it’s smooth sailing, as you just need to wait until the soup is hot enough and the ingredients are cooked enough for you to enjoy it.</p><p>Dead simple, and it sure beats any tinned soup that I have had recently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/0*MLdUP5vf3DJ2SWB4.png" /><figcaption>It should be noted that I am by no means any kind of photographer. This is simply the best that my phone and collection of knobs and vignettes could produce at the time.</figcaption></figure><p>Now I am about due to go to bed, eat my soup and rest up (that is, watch Breaking Bad until I fall asleep.)</p><p>Until next time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da3b9f942c25" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>