<?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 Andrei Soare on Medium]]></title>
        <description><![CDATA[Stories by Andrei Soare on Medium]]></description>
        <link>https://medium.com/@andreisoare?source=rss-921e7ae74302------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IYx6Mb2bJlttO3-hZr5NPQ.jpeg</url>
            <title>Stories by Andrei Soare on Medium</title>
            <link>https://medium.com/@andreisoare?source=rss-921e7ae74302------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:41:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andreisoare/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[Strange Loop 2017 Conference Notes]]></title>
            <link>https://medium.com/@andreisoare/strange-loop-2017-conference-notes-8b1fee6ad716?source=rss-921e7ae74302------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b1fee6ad716</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <dc:creator><![CDATA[Andrei Soare]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 21:42:54 GMT</pubDate>
            <atom:updated>2017-10-04T21:42:54.724Z</atom:updated>
            <content:encoded><![CDATA[<p>I attended Strange Loop in St. Louis this year and was impressed with the quality of the conference.</p><p>It focused on <em>problems that the industry is solving right now</em> rather than research that’s still trying to figure out solutions.</p><p>It also focused on <em>breadth of problems rather than depth</em> in a single, specific field.</p><p>This is especially useful if you’re a <em>full stack engineer working on customer facing products</em>, because the problems that you’re solving often change with user needs.</p><p>Most popular topics covered:</p><ul><li>Security</li><li>Distributed Systems</li><li>Programming Languages</li><li>Domain Specific Languages</li><li>Machine Learning</li></ul><h3><strong>Inclusion was a general theme for the entire conference.</strong></h3><p>There were lots of female speakers, which I thought was really great!</p><p><a href="https://github.com/strangeloop/StrangeLoop2017/blob/master/selected-talks/why-not-haskell/StrangeLoopWhyNotHaskell.pdf">A Haskell programmer thought that the reason Haskell isn’t popular is because the community is arrogant and unfriendly to people who want to learn.</a> So we should all be more friendly and have more patience with each other. This probably shouldn’t be generalized, and I don’t think that was the intention. Given that Haskell has a higher learning barrier, I can see how this is happening — it requires more patience to explain things and fewer people have that. And it snowballs.</p><p>Another talk <a href="https://github.com/strangeloop/StrangeLoop2017/blob/master/selected-talks/Programming%20Shibboleths.pdf">raised awareness about experienced developers spreading classic programming jokes, memes, that require deep context to understand</a>. This behavior makes new programmers feel like outsiders.</p><p>Another problem covered that I don’t see often discussed is <a href="https://github.com/strangeloop/StrangeLoop2017/blob/master/selected-talks/BrainstormingIntroverts.key">extrovert bias</a>: how do we make sure introverts have as much visibility and opportunity when working in teams as extroverts do?</p><p>Finally, there was a talk about <a href="https://youtu.be/sBD1SGuH2aI">mentoring minorities</a>.</p><h3><strong>Security</strong></h3><p>My favorite strange talk was about <a href="https://youtu.be/s0XmiXs8iRw">security in gaming consoles</a>. It goes through the history of all gaming consoles, from the very first until the latest that was released in 2017 and presents all the security flaws in each one and how they were exploited. Then takes a step back from each of these flaws and correlates them with principles that we apply today in software.</p><p>Another great talk was about <a href="https://youtu.be/QS8mrbAPLJc">Rocket</a>, a new web framework for Rust, which aims to solve many of the security problems that still exist or are easy to miss when using today’s most popular frameworks (Wordpress, Django, Rails):</p><ul><li>remote code execution</li><li>input validation</li><li>authentication</li><li>authorization</li><li>misconfiguration</li></ul><p>This talk reminded me of an article I read on Hacker News a while ago about the amount of <a href="https://news.ycombinator.com/item?id=15321015">security problems that the web still hasn’t solved</a>.</p><p>A big problem for security is the fact that usage of open source software is growing exponentially, and yet project maintainers are at alarmingly low numbers. 93% of NPM packages have one maintainer — and these packages are used by Fortune 500 companies. That’s scary. <a href="https://youtu.be/VS6IpvTWwkQ">This talk expands on this problem and potential solutions that we all should help with</a>.</p><p>Another talk covered <a href="https://youtu.be/gF-M4ja9lrA">security in authentication systems</a> in depth. I thought the last bit was interesting — I’ve been reading lately about how companies should get rid of passwords and allow authentication with just your email. Slack actually has a very nice implementation of this. But it turns out this method is still susceptible to a MITM attack because of how security is implemented in email servers.</p><p>Also <a href="https://youtu.be/a4UXnZaunJQ">working in the government is very challenging</a> because of the very strict security requirements.</p><h3><strong>Machine Learning</strong></h3><p>A problem that people in this field are trying to solve is understanding how neural networks make decisions and explaining these decisions to humans. <a href="https://youtu.be/DiWkKqZChF0">Strip was actually forced to solve this problem</a> with a solution that’s not ideal, sometimes maybe even wrong, but good enough to get away with it.</p><h3><strong>Domain Specific Languages</strong></h3><p><a href="https://youtu.be/shDoux5Dcyk">This talk gives a high level overview of what they are and how they’re made</a>.</p><p>Among the topics covered:</p><ul><li><a href="https://youtu.be/yJW--wNMv1M">Architecture</a> — I liked this one because it’s very far from tech and it’s also easy to relate with, even for non-architects.</li><li><a href="https://youtu.be/NsMTe9vxQxk">Infrastructure management</a></li><li><a href="https://youtu.be/CshFcfPtyoM">Biology</a></li></ul><h3><strong>Distributed systems</strong></h3><p>It was great to see a lot of hard problems that companies have to solve when they use a services architecture.</p><p>Netflix talks about how <a href="https://youtu.be/SM2uXpmyJmA">systems are doomed to fail and how you should embrace that and just kill them yourself</a> often. The popular Chaos Monkey.</p><p><a href="https://youtu.be/kxMKnx__uso">Caching is a big deal at Twitter</a>. Especially for services like their User Service (reads and writes to user data), that have significantly more reads than writes. For that one their cache hit rate is &gt; 99.9%. And there’s a bunch of problems that they had to solve, each one motivated by a different outage :-)</p><ul><li>Read spikes would put too much load on the Memcache service — solved with a 30 second TTL in-process cache.</li><li>Retry storms (common in all services architectures) — solved by darkmoding = serving most of the traffic from cache until affected services become healthy again.</li><li>Caching bad values (not found, corrupted, or just incorrect) — solved by dynamic TTLs that start with a very small value and slowly increase with the likelihood that the values are correct.</li></ul><p>Comcast is another company dealing with big problems in a services architecture. I learned about <a href="https://youtu.be/m64SWl9bfvk">Queuing theory and how they rely on it to manage capacity across all their services</a>.</p><p>Another great talk was about <a href="https://youtu.be/6OFeuNy39Qg">the history and future of databases</a>.</p><ul><li>It started with a few database implementations that were really hard to use.</li><li>Then SQL / RDBMS become popular really quickly (MySQL, PostgreSQL) and probably will still be for a while.</li><li>Then, as more and more people had access to the internet, and companies had to deal with more data, NoSQL was born to solve the scalability problems of SQL. They became very popular very quickly, but now people are realizing that they are only great for a small subset of problems and they’re decreasing in popularity.</li><li>Now, companies like Google are moving away from NoSQL to a new type, commonly referred to as NewSQL, that tries to bundle the benefits of both SQL and NoSQL. Google built Spanner, and the industry is following with open source solutions like CockroachDB.</li></ul><h3>Education for engineers</h3><p>I want to call out a small trend that I noticed — learning about technology by rebuilding it.</p><p>There was a talk about git where the presenter reimplemented a barebones git client from scratch in 40 minutes in Ruby. By the end he was able to create commits and use git log to read them. Unfortunately, a recording of it will not be published.</p><p>But this is similar to another great article that I read on Medium about Blockchain — <a href="https://hackernoon.com/learn-blockchains-by-building-one-117428612f46">learn Blockchain by building one</a>!</p><p>The reason why I like this approach is because often times a new technology can look scary. And it’s usually because it’s poorly documented and you have no idea how it works, or how to use it. Actually no — maybe it’s because documentation isn’t created with learning in mind, but rather to be used as a reference when you’re already familiar with the technology and are using it in a project.</p><p>But once you actually think about how to implement it from scratch, and go through a very barebones implementation, step by step, it doesn’t look that scary anymore. It’s just some piece of code. That even you could have created, if you had been exposed to the problems it’s solving, at the right time.</p><h3><strong>Site Reliability Engineering</strong></h3><p>This talk gives a high level view of <a href="https://youtu.be/xWAfTAu0Mww">best practices that companies should be using to keep their site up</a>.</p><p>And this one focuses on the challenges that companies face when using <a href="https://youtu.be/1wjovFSCGhE">micro services</a>, and the shift from monitoring to observability.</p><h3><strong>Data infrastructure</strong></h3><p>And this one gives a high level overview of <a href="https://youtu.be/0Eimlcrj-tg">how data infrastructure is implemented at Netflix</a>.</p><h3><strong>Stranger talks</strong></h3><p>Just to clarify — these are strange in a very good way. It’s awesome to see people use technology outside the technology field.</p><p>There were 2 people who generate art with code:</p><ul><li><a href="https://youtu.be/L3D0JEA1Jdc">Poetry</a></li><li><a href="https://youtu.be/5R9eywArFTE">Paintings</a></li></ul><h3><strong>What else?</strong></h3><p>I appreciate the fact that all talks were 30–40 minutes, which worked well for my short attention span.</p><p>You can find the <a href="https://www.thestrangeloop.com/schedule.html">full schedule here</a> and <a href="https://www.youtube.com/channel/UC_QIfHvN9auy2CoOdSfMWDw/videos">recordings of most videos here</a>, in case you want to explore some of the talks that I missed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b1fee6ad716" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>