<?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 Alan Williams on Medium]]></title>
        <description><![CDATA[Stories by Alan Williams on Medium]]></description>
        <link>https://medium.com/@alanwill?source=rss-fdf947cbca4e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*liMThiMH8u4pQZgevShAQQ.jpeg</url>
            <title>Stories by Alan Williams on Medium</title>
            <link>https://medium.com/@alanwill?source=rss-fdf947cbca4e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:49:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alanwill/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[Learning, the journey of fascination]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://alanwill.medium.com/learning-the-journey-of-fascination-c23e9cf34af9?source=rss-fdf947cbca4e------2"><img src="https://cdn-images-1.medium.com/max/2600/0*gsYBLmy07oxdOOFG" width="5026"></a></p><p class="medium-feed-snippet">Learning is fascinating. Lately, I&#x2019;ve been reflecting on my career path and precisely the various skills I&#x2019;ve had over the years and how&#x2026;</p><p class="medium-feed-link"><a href="https://alanwill.medium.com/learning-the-journey-of-fascination-c23e9cf34af9?source=rss-fdf947cbca4e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://alanwill.medium.com/learning-the-journey-of-fascination-c23e9cf34af9?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c23e9cf34af9</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 18:08:07 GMT</pubDate>
            <atom:updated>2023-09-06T18:08:07.060Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Age of Convenience]]></title>
            <link>https://medium.com/simple-thoughts-amplified/age-of-convenience-48eb0f63b703?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/48eb0f63b703</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[convenience]]></category>
            <category><![CDATA[subscription]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Sun, 26 Feb 2017 04:16:37 GMT</pubDate>
            <atom:updated>2017-02-26T04:16:37.287Z</atom:updated>
            <content:encoded><![CDATA[<p>My car is 12 years old with almost 200K miles and I’ve been thinking that soon it will be time to replace it once it starts breaking down. I also realized that I very rarely ever drive the car, maybe a couple times a month. How come? Well I use Instacart, Google Express and Amazon Fresh to deliver groceries and household items. Green Chef delivers meals once a week. Amazon for pretty much every other shopping need. To get to work, I walk to the bus stop that’s right across the street and it drops me off a couple blocks from the office. There are also a few restaurants in walking distance. In other words, most everything I need I can get conveniently without having to drive and I live in the suburbs which makes it an even more interesting realization.</p><p>So do I really need to purchase a new car once this one dies? That’s really my quandary. The decision would be a lot easier if there was a Zipcar but I’m sure in time that’ll change. The bigger thought here isn’t about me but more of the age of convenience that we’re in. Subscriptions to just about any service imaginable are available today to free up our time to be used for things we really love. Speaking of cars, we even have autonomous cars today to remove the mundane of driving as a whole, yet another convenience.</p><p>I’m happy to be alive and living in such interesting times where technology and automation are quite literally changing our lives for the better every day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48eb0f63b703" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/age-of-convenience-48eb0f63b703">Age of Convenience</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Gateway, the API gateway for everyone]]></title>
            <link>https://medium.com/simple-thoughts-amplified/api-gateway-the-api-gateway-for-everyone-eed106e0a22b?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/eed106e0a22b</guid>
            <category><![CDATA[aws-api-gateway]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Sun, 15 Jan 2017 07:18:45 GMT</pubDate>
            <atom:updated>2017-01-15T07:41:53.902Z</atom:updated>
            <content:encoded><![CDATA[<p>AWS API Gateway ended 2016 with the addition of documentation support. I recently started playing around with it trying to put the service through it’s paces again to objectively compare it to it’s competition. My evaluation was from an enterprise lens, i.e. the features that would make the service compelling for large companies with many APIs, many being complex in nature as well as the operationalizing of said APIs.</p><p>The TL;DR version of this is that I think this service has come a long way from a year ago and in just the past 3–4 months they’ve released a number of attractive features for all companies even enterprises.</p><p><strong>Swagger Support</strong></p><p>API Gateway treats Swagger like a first class citizen. You can import Swagger that’s fully interpreted and the same applies to <a href="https://docs.aws.amazon.com/apigateway/latest/developerguide/create-api-using-import-export-api.html">exporting</a>. So much so that I sometimes find it easier to use the console to describe my API, add documentation etc then export it to Swagger (JSON or YAML) where a full spec compliant file is created. The exported Swagger files contain the API Gateway extensions as well as native Swagger components.</p><p><strong>Documentation Support</strong></p><p>This was one of the new features released in late 2016 and with it the ability to expose your API in a <a href="https://aws.amazon.com/blogs/compute/generate-your-own-api-gateway-developer-portal/">Developer Portal</a>. Documentation in API Gateway is treated in parts, where a part is a discrete piece of documentation for a specific component of the API. For example, the method, resource, headers, parameters, status code responses, requests/response body each are their own discrete documentation part which when exported in Swagger includes both the Swagger recognized documentation as well as the API Gateway specific swagger extensions. The translation provides full Swagger support. This is a big deal because you can take that Swagger spec then import into another provider with little to no modifications required.</p><p><strong>Monetization</strong></p><p>This feature I haven’t personally used so can’t speak too much to it but like it’s name suggests allows you to monetize your API by publishing it to the AWS Marketplace. Coupled with the Usage Plans feature that enable the ability to set things like number of requests per time period for a given type of consumer. For example, you can create a Usage Plan for paying customers vs non-paying (free) customers. The paying customers could get a high request per minute rate and quota where as the non-paying customers could get lower limits.</p><p><strong>Request/Response Mapping</strong></p><p>You have a Lambda function as your API backend but Lambda only returns status code 200 for all it’s responses, this makes it difficult the return an appropriate response from your API if you’re using a passthrough integration with Lambda so that’s where API Gateway’s Request/Response mappings help. Using the Apache Velocity template language you can describe a mapping that translates a request to a payload that Lambda can understand and vice versa with a Lambda response to a more meaningful API response. Additionally each defined mapping can be associated with a unique status code enabling a level of granularity to specify status code for example a 404 response vs a 409 response or a 200 vs a 202 response.</p><p>These are only some of the interesting features of API Gateway and I really only barely touched the surface of this service.</p><p>There’s 1 gap that I still see that needs to be addressed, hopefully in 2017 to really make API Gateway an Enterprise ready gateway and that is, OAuth2 support. OAuth is an industry standard authentication framework that most companies use in their APIs. Today you can use AWS’s Sigv4 framework as a close replacement but that’s AWS specific and not industry standard so it’s use case is really mostly applicable to internal APIs, not APIs that you then expose to your customers.</p><p>The <a href="https://docs.aws.amazon.com/apigateway/latest/developerguide/">API Gateway documentation</a> is a good read to learn more about the service and well worth the time and if you were thinking that API Gateway wasn’t yet ready, take a look again, you might be pleasantly surprised with what those guys have been releasing over the past 4 months or so.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eed106e0a22b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/api-gateway-the-api-gateway-for-everyone-eed106e0a22b">API Gateway, the API gateway for everyone</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with asynchronous APIs]]></title>
            <link>https://medium.com/simple-thoughts-amplified/working-with-asynchronous-apis-3fb02fc105e6?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fb02fc105e6</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Thu, 22 Dec 2016 07:29:45 GMT</pubDate>
            <atom:updated>2016-12-22T09:25:17.324Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever made a POST request to an API, followed immediately by a GET for the same resource only to receive a “resource not found” error or similar message?</p><p>In AWS a scenario like the above would happen when making calls to create a Kinesis Firehouse stream or Config configuration recorder or EC2 instance for example where the resource takes a few seconds or more to create. AWS does provide <em>waiters</em> on some (possibly all) of it’s SDKs as a way for consumers to test that a resource is ready before interrogating it. My experience is with Boto (Python SDK) so the rest of this article will be from that context. Waiters are great but unfortunately they aren’t available for every resource. What I’ve been doing is using a <em>retry</em> decorator.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/51663e83a9bb3e8f685d07ab532d3c5d/href">https://medium.com/media/51663e83a9bb3e8f685d07ab532d3c5d/href</a></iframe><p>In the example above, I’m creating the Cloudwatch Log Group for VPC Flow Logs.</p><p>In lines 3–10 I create the Log Group and set a retention window.</p><p>Line 13 is the decorator which says if the function returns a ValueError, then retry up to 60 times with the specified delay, backoff and jitter which provides an exponential backoff retry logic.</p><p>Lines 14–22 are the function which is being decorated. This particular function invokes the describe_log_group API searching to see if the log group created in lines 4–6 exists, if not it’ll keep retrying up to 60 times.</p><p>In a world where asynchronous calls are the norm, and where API performance is variable, as a developer, wrapping your API calls with retry logic is an efficient way to build in resiliency into your application so that it doesn’t fail immediately if the calling API happens to not return the expected result in a short enough time. Of course if a waiter exists in the SDK then by all means use that but otherwise, <a href="https://pypi.python.org/pypi/retry/">retry</a> is a quick and dirty yet effective alternative.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fb02fc105e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/working-with-asynchronous-apis-3fb02fc105e6">Working with asynchronous APIs</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leader in Cloud]]></title>
            <link>https://medium.com/simple-thoughts-amplified/leader-in-cloud-4822dab869be?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4822dab869be</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Thu, 08 Dec 2016 06:55:35 GMT</pubDate>
            <atom:updated>2016-12-08T06:55:35.899Z</atom:updated>
            <content:encoded><![CDATA[<p>Leader in Cloud</p><p>On the heels of a really dense yet hugely productive AWS re:invent week it’s clear why these guys are the leader. I don’t think it’s the kool-aid high when I say these guys are torching the path to greatness and this year just underscored that even more. With a mind blowing 70+ portfolio of services ranging from raw compute to AI to gaming to video processing and everything in between it begs the question what’s left yet year over year there always seems to be the “there’s more” effect. This year my highlight services were Step Functions, Lex and Polly.</p><p>Step Functions takes Lambda based systems to another level with the ability to orchestrate and more easily design completely distributed systems. Not that you couldn’t do this before with SNS and a little bit of code but now it’s that much easier and arguably more reliable.</p><p>Lex, with the potential to democratize conversational bots using both voice and text think of the possibilities that provides lowering the barrier to entry for bot developers. It solves many of the limitations that were previously part of building Alexa skills especially when paired with Polly.</p><p>Polly (want a cracker) is text to speech technology for the masses.</p><p>These were my favorite announcements but there were other features announced that were pretty interesting as well like API Gateway’s Developer Portal, WAF for ELB, CodeBuild and SAM to name a few.</p><p>Needless to say I’ll be busy the next few weeks figuring out ways and areas where we can benefit from these services and features. Might even blog a post or 2 on those…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4822dab869be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/leader-in-cloud-4822dab869be">Leader in Cloud</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MigTest]]></title>
            <link>https://medium.com/simple-thoughts-amplified/migtest-bafd8d78de22?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bafd8d78de22</guid>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Thu, 17 Nov 2016 06:09:48 GMT</pubDate>
            <atom:updated>2016-11-17T06:09:48.678Z</atom:updated>
            <content:encoded><![CDATA[<p>Migtest((</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bafd8d78de22" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/migtest-bafd8d78de22">MigTest</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automation Isn’t for the Faint of Heart]]></title>
            <link>https://medium.com/simple-thoughts-amplified/automation-isnt-for-the-faint-of-heart-e837dd32a46f?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e837dd32a46f</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 03:02:06 GMT</pubDate>
            <atom:updated>2016-11-03T03:02:06.380Z</atom:updated>
            <content:encoded><![CDATA[<p>You hear about automation all the time, making things faster and more autonomous and the benefits are everything from plain cool to improving customer engagement and delivering better value to your customers. The little less known fact though is that automation isn’t easy. I’m not saying this to reduce any of the benefits or cast any doubt on the practice, more instead to set expectations. Personally I’m a big proponent of automation and I don’t see that changing any time soon.</p><p>I’ve recently been involved in a few projects where I made automation a fundamental tenet of our deliverable. I specifically wanted to change the often habit of making automation a feature; something that can come in the next version as an enhancement. Fundamentally that’s a wrong way of thinking because delaying automation means accruing technical debt, it means having to do the same thing twice, it means having to re-write that functionality or feature that you just developed which is expensive.</p><p>Like many things though automation gets easier over time because you build that muscle experience, it also gets more complex over time which may not necessarily be easier but the outcome typically has more value. We’re in a time where there’s so much technology out there that there’s virtually nothing that can’t be automated. With the democratization of cloud computing and the proliferation of APIs we have a tremendous amount of opportunity to automate. Someone I once worked with said, “If I have to do anything more than twice, I automate it”…good words to live by.</p><p>Great, automation is everything we get it, now what? Plan. Be ready to think differently, don’t give up. Look at the big picture not just the problem directly in front of you. Automation can lead to complexity but that’s not a bad thing, manage the complexity, it’s inevitable but try to simplify it anywhere you can. I was on a project where we were tasked to build a reverse proxy platform which seemed fairly simple…get a few servers, install NGINX, backups, monitoring, we’re done! We however went even further and we built a system that took care of itself. It patched itself, it monitored itself, it scaled itself, it failed over itself, it deployed itself. All that automation resulted in a fairly complex system, however it was well documented so that it didn’t seem like black magic to someone else not involved in the design. The net benefits was a system that required very little hand holding once in Production, was highly available and reliable so both Ops and our Customers were happy (Customers are happy if your service is always up and never goes down and performs well but they don’t care how the sausage is made, just make sure it tastes good).</p><p>There’s always a balance for everything, I’m not a big believer in black and white and think that binary is only good for computers. There’s trade offs and considerations that effect each project, team and organization differently so again, plan, but don’t let the complexity of automation turn you off. Face it head on, it’ll get easier and harder as you gain experience and the problems become even more interesting but don’t give up until you’ve met your automation goals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e837dd32a46f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/automation-isnt-for-the-faint-of-heart-e837dd32a46f">Automation Isn’t for the Faint of Heart</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitHub Universe: Conference Report]]></title>
            <link>https://medium.com/simple-thoughts-amplified/github-universe-conference-report-846eb6d9b9cf?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/846eb6d9b9cf</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Wed, 21 Sep 2016 01:42:01 GMT</pubDate>
            <atom:updated>2016-09-21T01:42:01.070Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r4MoVyzvExlOk0Xx4EEDwg.jpeg" /><figcaption>GitHub Universe 2016 container welcome attendees and doubling as a coat check stall.</figcaption></figure><p>Last week I attended GitHub Universe for the second year and once again it was time well spent. It continues to blow my mind the fascinating job they do of putting on the event, specifically the venue transformation (wow), high quality of food (yum), nicest Porta Potties I’ve ever seen or used (thanks), and high quality sessions (yay) all at a very reasonable price.</p><p>This year the sessions seemed a bit less technical but nonetheless still very interesting and relevant. The theme was mostly around community and driving culture change both topics which I could immediately relate as they areas I’m personally involved with at work. As to be expected at any conference there were a few <a href="https://github.com/blog/2256-a-whole-new-github-universe-announcing-new-tools-forums-and-features">product announcements</a> and the ones that I found most notable were Projects and GraphQL access and the addition of SAML to github.com next year.</p><h3>Projects</h3><p>We use GitHub Enterprise at my job as a code repository and JIRA for project management. A couple of my projects use JIRA mostly for our daily standups and just for that 30–60 minute period per day, otherwise for the most part it’s not used. Most of the time the tasks in JIRA are a reflection of work needing to be done with code that’s in GitHub. I’m not hinting that Projects should replace JIRA per se but for small projects that don’t need the heavy reporting capabilities in JIRA or any of it’s deep project management functionality, Projects seems like a good fit. It’s 1 less tool for an engineer to have to learn and figure out. One stop shop for your code and status tracking; simple and functional. I also like that it enables the use of Issues for more than just code specific tasks but things like follow ups, planning, requirements gathering etc. That’s another thing that I found interesting about the conference is hearing all the ways that people are using GitHub, many of which have absolutely nothing to do with code. So even though Projects is not yet in GHE, I’m hoping that happens in the next couple months so I can start giving it more practical use.</p><h3>GraphQL</h3><p>Prior to the conference I had heard of GraphQL in passing but couldn’t really tell you exactly what it was. I attended GitHub’s session “Implementing and Using GraphQL at GitHub” co-presented by Dan Schafer @ Facebook, who not only explained what it is but highlighted the reasons why they’re using it now and I finally had my aha moment. It also made me realize just how graph-esque most of the data we work with really is and how thinking that way, in the sense of your data is a large graph, makes you realize just all the various permutations of relationships and connections that exist. The search versatility and granularity that GraphQL provides seems quite useful. I’m still trying to think of one or two real-use cases for it at work that I could immediately tackle in order to get more hands on with it because the one potential drawback that I could see is that it could lead to potentially bloated services. Bloated in the sense of having a lot more functionality built into a service which would have otherwise been a few disparate small microservices. Balance is likely the answer here but regardless this looks like quite an interesting piece of software.</p><h3>SAML</h3><p>In these modern times, “as a Service” is the new norm. The value proposition of <em>running your own</em> is diminishing daily. With the addition of SAML to github.com and additionally married with 2FA more businesses, especially medium to large sized ones would consider moving their code bases to .com where they can leverage their existing employee identities and make code sharing with the public identities as well open sourcing in general that much more seamless. There’s some expected controls I’d hope would be in place in order to prevent accidentally publicizing proprietary code or code that isn’t yet “ready” to be externalized but the path is being laid towards that happy place and I’m content to see that. This feature was announced to be coming in 2017.</p><h3>Interesting Sessions and Content</h3><p>The sessions are going to be posted online shortly so I’m only going to recap the ones I found most interesting:</p><ul><li><a href="http://githubuniverse.com/program/sessions/#graphql">Implementing and Using GraphQL at GitHub</a> by Kyle Daigle @ GitHub and Dan Schafer @ Facebook. This was the GraphQL session I mentioned earlier.</li><li><a href="http://githubuniverse.com/program/sessions/#instagram">Codifying Company Values</a> by Hui Ding @ Instagram. I think the name of this one is a bit misleading but there’s a lot of good insight into the scaling challenges that Instagram has had to overcome and their decision making process that drove the tech stack they currently run. A couple takeaways for me…they use Postgres to manage all their user data with no DBAs on staff and only a dozen or so infrastructure engineers. Also clearly Python can scale, granted it does need to be tuned but so does every piece of software when exercised to that level.</li><li><a href="http://githubuniverse.com/program/sessions/#tips-n-tricks">Tips &amp; Tricks: Gotta Git Them All</a> by Jamie Strusz and Brent Beer @ GitHub. This entire session was worth noting down. I at first thought it was going to be a repeat of last year’s however it was everything but. Here’s a few goodies I pulled out… <strong><em>git config — global help.autocorrect 10</em></strong> can be used to allow git to autocorrect your commands, no more <strong><em>git sttus</em></strong><em>. </em>In GitHub, actually in Markdown, to enable syntax highlighting <a href="https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting">https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting</a>. In Atom check out the git-time-machine package :).</li><li><a href="http://githubuniverse.com/program/sessions/#distributed-inclusive">Building and Scaling a Distributed and Inclusive Team</a> by Mathias Meyer @ Travis CI. I really liked this talk as he showed how the mostly remote and globally distributed employee base of Travis CI deal with communication and day to day interactions. They use the typical suite of tools as most any other company, no magic there but it was clear that it takes some thinking differently and there is no perfect answer. They have a mantra of “if it’s not written down, it doesn’t exist” which makes complete sense when everyone is dispersed all over the world in varying timezones. Another documentation mantra they have, “Less oral communication means more accidental documentation”. They use Google Docs and Pull Requests for documentation, Slack for real-time communication and Issues for discussions (in lieu of something like threaded conversations in Slack). They maintain a “Builders Manual” that sounds like it’s an employee playbook with links to other sources as a way to centralize where all the dispersed information can be found.</li><li><a href="https://octoverse.github.com/">State of the Octoverse</a>. Fascinating infographic showing just how awesome the opensource community really is. Check out the top starred repos and the ones with the most forks as well as most contributing users, a lot of gems in there.</li></ul><p>Well it was a great 3 days and I’d be lying if I didn’t say I’m looking forward to next year.</p><p>Here are some pics of the impressive venue <a href="https://goo.gl/photos/VoS8jUjXNbJutGFN6">https://goo.gl/photos/VoS8jUjXNbJutGFN6</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=846eb6d9b9cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/github-universe-conference-report-846eb6d9b9cf">GitHub Universe: Conference Report</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Github Universe Day 0]]></title>
            <link>https://medium.com/simple-thoughts-amplified/github-universe-day-0-52fef2d9c7a3?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/52fef2d9c7a3</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Wed, 14 Sep 2016 05:01:18 GMT</pubDate>
            <atom:updated>2016-09-14T05:01:18.185Z</atom:updated>
            <content:encoded><![CDATA[<p>Github Universe Day 0</p><p>I’m at Github Universe this week. After being so impressed by the high quality sessions last year I was really looking forward to going again. Today was the training day. Overall the sessions were good and I’d even go as far as saying more basic than I was hoping but I did learn a few things so that’s still winning. In particular the class on the API had a few good tidbits to share, for example the <em>httpie</em> tool. Think of <em>curl</em> but even nicer. There was a class on hubot as well which has really got me thinking about how I can “Lambdarize” hubot for use on our Slack. Hubit running on Lamba in a fully automated and continuously deployable way. Thatll be my next pet project.</p><p>So tomorrow will be Day 1. I’ll post notes then of anything significant I take away.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52fef2d9c7a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/github-universe-day-0-52fef2d9c7a3">Github Universe Day 0</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deleting Multiple Rows in DynamoDB]]></title>
            <link>https://medium.com/simple-thoughts-amplified/deleting-multiple-rows-in-dynamodb-e4551d3c07ea?source=rss-fdf947cbca4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4551d3c07ea</guid>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Alan Williams]]></dc:creator>
            <pubDate>Sun, 21 Aug 2016 09:13:17 GMT</pubDate>
            <atom:updated>2016-08-21T09:13:17.439Z</atom:updated>
            <content:encoded><![CDATA[<p>Had to do this today and after struggling with it for a bit, I finally got it working. Here’s how…</p><p>First of, my table, <em>talr-taskStatus</em>, has a partition key called <em>requestId</em> and a sort key called <em>eventTimestamp</em>. My specific scenario is that the table grew to a fairly large size and I wanted to purge all the rows for a given requestId which was about 10K rows.</p><p>DynamoDB doesn’t have a command that deletes multiple rows so I ended up running a Query call, looping through the response to feed into a BatchWriteItem call. Here’s how in Python:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d75184b2e8a1041500309272558cc31b/href">https://medium.com/media/d75184b2e8a1041500309272558cc31b/href</a></iframe><p>Worked quite well, just had to increase the write capacity units as well as the Lambda timeout (the request ran in a Lambda function).</p><p>One learning, as you can see from the code above, I’m using <em>boto3.client</em>. Originally I was using <em>boto3.resource</em> and was getting the following error:</p><blockquote>An error occurred (ValidationException) when calling the BatchWriteItem operation: The provided key element does not match the schema</blockquote><p>Unfortunately that error had nothing to do with the root cause of the problem and caused over an hour of unneeded troubleshooting in the wrong area but switching the <em>resource</em> to <em>client</em> did the trick.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4551d3c07ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simple-thoughts-amplified/deleting-multiple-rows-in-dynamodb-e4551d3c07ea">Deleting Multiple Rows in DynamoDB</a> was originally published in <a href="https://medium.com/simple-thoughts-amplified">Simple Thoughts Amplified</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>