<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (notaddicted)</title>
    <link>https://pinboard.in/u:notaddicted/public/</link>
    <description>recent bookmarks from notaddicted</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.youtube.com/watch?v=zuBw1HFJMsM&amp;app=desktop"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=16300152"/>
	<rdf:li rdf:resource="https://blog.acolyer.org/2018/01/17/some-thoughts-on-security-after-ten-years-of-qmail-1-0/"/>
	<rdf:li rdf:resource="https://blog.openai.com/scaling-kubernetes-to-2500-nodes/"/>
	<rdf:li rdf:resource="https://www.zenhub.com/"/>
	<rdf:li rdf:resource="https://www.quora.com/I-am-the-CEO-at-a-SaaS-startup-My-dev-team-is-complaining-that-requirements-are-not-detailed-enough-though-we-are-Agile-I-feel-like-they-are-asking-to-be-bricklayers-instead-of-architects-Do-I-tell-them-to-take-more-initiative-in-understanding-the-customer-problem-or-tell-them-what-to-build"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=16076932"/>
	<rdf:li rdf:resource="https://danluu.com/learning-to-program/"/>
	<rdf:li rdf:resource="https://serverless.com/blog/serverless-aurora-future-of-data/"/>
	<rdf:li rdf:resource="http://smmry.com/"/>
	<rdf:li rdf:resource="http://nbviewer.jupyter.org/url/norvig.com/ipython/Advent%20of%20Code.ipynb"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=15813318"/>
	<rdf:li rdf:resource="https://github.com/danluu/debugging-stories"/>
	<rdf:li rdf:resource="http://forum.arduino.cc/index.php?topic=325886.0"/>
	<rdf:li rdf:resource="http://elm-chan.org/docs/mmc/mmc_e.html"/>
	<rdf:li rdf:resource="http://www.avrfreaks.net/forum/spi-clock-rate-and-sd-cards"/>
	<rdf:li rdf:resource="http://www.eugenewei.com/blog/2017/11/13/remove-the-legend"/>
	<rdf:li rdf:resource="https://www.nominum.com/tech-blog/domain-correlation-just-let-malware-beat/"/>
	<rdf:li rdf:resource="https://research.googleblog.com/2017/11/fused-video-stabilization-on-pixel-2.html"/>
	<rdf:li rdf:resource="http://r4ds.had.co.nz/model-basics.html"/>
	<rdf:li rdf:resource="https://github.com/knsv/mermaid"/>
	<rdf:li rdf:resource="https://hillelwayne.com/post/why-tdd-isnt-crap/"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=15582969"/>
	<rdf:li rdf:resource="https://code.facebook.com/posts/1537144479682247/finding-inter-procedural-bugs-at-scale-with-infer-static-analyzer/"/>
	<rdf:li rdf:resource="https://www.hillelwayne.com/post/handwriting-j/"/>
	<rdf:li rdf:resource="https://www.reddit.com/r/programming/comments/73nnv1/clever_way_of_skirting_game_code_quality_tests/"/>
	<rdf:li rdf:resource="https://github.com/hmemcpy/milewski-ctfp-pdf"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=JIQETrFC_SQ&amp;list=WL&amp;index=18"/>
	<rdf:li rdf:resource="http://dnsviz.net/d/87.is/analyze/"/>
	<rdf:li rdf:resource="https://www.oath.com/press/open-sourcing-vespa-yahoo-s-big-data-processing-and-serving-eng/"/>
	<rdf:li rdf:resource="https://blogs.dropbox.com/tech/2017/09/optimizing-web-servers-for-high-throughput-and-low-latency/"/>
	<rdf:li rdf:resource="http://samwho.co.uk/blog/2017/09/06/move-your-bugs-to-the-left/"/>
	<rdf:li rdf:resource="https://jakevdp.github.io/PythonDataScienceHandbook/05.06-linear-regression.html"/>
	<rdf:li rdf:resource="http://zipcpu.com/blog/2017/08/21/rules-for-newbies.html"/>
	<rdf:li rdf:resource="https://www.theatlantic.com/technology/archive/2017/08/inside-waymos-secret-testing-and-simulation-facilities/537648/"/>
	<rdf:li rdf:resource="http://graydon2.dreamwidth.org/253769.html"/>
	<rdf:li rdf:resource="http://fermatslibrary.com/s/the-emperors-old-clothes"/>
	<rdf:li rdf:resource="https://engineering.tumblr.com/post/161854099032/jetpants-integration-testing"/>
	<rdf:li rdf:resource="https://www.reddit.com/r/programming/comments/6gr2fc/til_the_current_hash_function_for_java_strings_is/disnr9v/"/>
	<rdf:li rdf:resource="https://www.jackkinsella.ie/articles/programming-accounting-features-in-web-apps"/>
	<rdf:li rdf:resource="http://cosette.cs.washington.edu/"/>
	<rdf:li rdf:resource="http://btorpey.github.io/blog/2016/11/12/even-mo-static/"/>
	<rdf:li rdf:resource="http://kubernetesbyexample.com/"/>
	<rdf:li rdf:resource="https://segment.com/blog/spotting-a-million-dollars-in-your-aws-account/"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Fluidics"/>
	<rdf:li rdf:resource="https://github.com/MarcoPon/SeqBox"/>
	<rdf:li rdf:resource="http://t3x.org/t3x/"/>
	<rdf:li rdf:resource="https://landing.google.com/sre/book/chapters/data-integrity.html"/>
	<rdf:li rdf:resource="https://landing.google.com/sre/book/chapters/testing-reliability.html"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=14221848"/>
	<rdf:li rdf:resource="https://github.com/Miserlou/Zappa#basic-usage"/>
	<rdf:li rdf:resource="https://medium.com/espark-engineering-blog/formal-methods-in-practice-8f20d72bce4f"/>
	<rdf:li rdf:resource="http://zipkin.io/"/>
	<rdf:li rdf:resource="https://blog.ycombinator.com/founder-stories-kate-heddleston/"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=14183767"/>
	<rdf:li rdf:resource="https://www.goodreads.com/author_blog_posts/2484147-lessons-i-learned-at-mcdonald-s-that-help-me-build-software"/>
	<rdf:li rdf:resource="http://steve-yegge.blogspot.ca/2008/06/done-and-gets-things-smart.html"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Pearson_correlation_coefficient"/>
	<rdf:li rdf:resource="https://medium.com/@cheapsteak/quick-and-dirty-tricks-for-debugging-javascript-d0e911c3afa"/>
	<rdf:li rdf:resource="https://www.redbubble.com/people/ange4771/works/11126212-elf101-a-linux-executable-walkthrough?c=249202-elf101-all-versions"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=14046446"/>
	<rdf:li rdf:resource="http://aosabook.org/en/index.html"/>
	<rdf:li rdf:resource="http://viewsourcecode.org/snaptoken/kilo/index.html"/>
	<rdf:li rdf:resource="https://myers.io/2017/04/04/the-joel-test-for-2017/"/>
	<rdf:li rdf:resource="https://github.com/madler/zlib/commit/51370f365607fe14a6a7a1a27b3bd29d788f5e5b"/>
	<rdf:li rdf:resource="https://automatetheboringstuff.com/"/>
	<rdf:li rdf:resource="http://www.diveintopython3.net/"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=14034401"/>
	<rdf:li rdf:resource="https://blog.skyliner.io/fourteen-months-with-clojure-beb8b3e4bf00"/>
	<rdf:li rdf:resource="https://stripe.com/blog/rate-limiters"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.youtube.com/watch?v=zuBw1HFJMsM&amp;app=desktop">
    <title>Stanford Seminar - Exploiting modern microarchitectures: Meltdown, Spectre, &amp; other hardware attacks - YouTube</title>
    <dc:date>2018-02-04T21:11:27+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=zuBw1HFJMsM&amp;app=desktop</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:65e0ce3a1fba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=16300152">
    <title>You can use the debugger on low level api calls to get pretty much anywhere in t... | Hacker News</title>
    <dc:date>2018-02-03T23:58:41+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=16300152</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming debugging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:50f3084c1ef3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:debugging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.acolyer.org/2018/01/17/some-thoughts-on-security-after-ten-years-of-qmail-1-0/">
    <title>Some thoughts on security after ten years of qmail 1.0 | the morning paper</title>
    <dc:date>2018-01-29T16:39:43+00:00</dc:date>
    <link>https://blog.acolyer.org/2018/01/17/some-thoughts-on-security-after-ten-years-of-qmail-1-0/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[For many years I have been systematically identifying error-prone programming habits — by reviewing the literature, analyzing other people’s mistakes, and analyzing my own mistakes — and redesigning my programming environment to eliminate those habits.

Some of the techniques recommended include ensuring data flow is explicit (designing large portions of qmail to run in separate processes connected through pipelines made much of qmail’s internal data flow easier to see for example), simplifying integer semantics (using big integers and regular arithmetic rather than the conventional modular arithmetic), and factoring code in order to make it easier to test error cases.]]></description>
<dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d31f8e5162e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.openai.com/scaling-kubernetes-to-2500-nodes/">
    <title>Scaling Kubernetes to 2,500 Nodes</title>
    <dc:date>2018-01-18T17:27:16+00:00</dc:date>
    <link>https://blog.openai.com/scaling-kubernetes-to-2500-nodes/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[todo: collect and read all openai writings
]]></description>
<dc:subject>programming sysadmin todo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:7106d6a8f6e9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:sysadmin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:todo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.zenhub.com/">
    <title>ZenHub - Agile Project Management for GitHub</title>
    <dc:date>2018-01-17T15:11:11+00:00</dc:date>
    <link>https://www.zenhub.com/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>management programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:edacb75e4cc8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.quora.com/I-am-the-CEO-at-a-SaaS-startup-My-dev-team-is-complaining-that-requirements-are-not-detailed-enough-though-we-are-Agile-I-feel-like-they-are-asking-to-be-bricklayers-instead-of-architects-Do-I-tell-them-to-take-more-initiative-in-understanding-the-customer-problem-or-tell-them-what-to-build">
    <title>I am the CEO at a SaaS startup. My dev team is complaining that requirements are not detailed enough though we are Agile. I feel like they are asking to be bricklayers instead of architects. Do I tell them to take more initiative in understanding the cust</title>
    <dc:date>2018-01-14T23:06:15+00:00</dc:date>
    <link>https://www.quora.com/I-am-the-CEO-at-a-SaaS-startup-My-dev-team-is-complaining-that-requirements-are-not-detailed-enough-though-we-are-Agile-I-feel-like-they-are-asking-to-be-bricklayers-instead-of-architects-Do-I-tell-them-to-take-more-initiative-in-understanding-the-customer-problem-or-tell-them-what-to-build</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[I have created entire products with nothing more than index cards, whiteboards, and the occasional printout of a visual mock. So it's definitely doable.

One odd thing about the way you phrase this is that it's very us vs them. In an Agile context, the relationship between product managers, programmers, and designers should be "we". It's one team.

Given that, my tips for you:

Sit together - In Agile processes, communication takes the place of documentation. If you are sitting a few feet from the engineers and answer questions as they come up, then they shouldn't need "requirements" (which are not an Agile thing).
Release early and often - At my last company, we released a few times a day, and there were only a half-dozen of us. The more frequently you release, the more the engineers can see how what they're doing affects the real world.
Work in small units - Each unit of work for us was circa 1 pair-day of work. A fine-grained approach made it easy to stay in sync while working relatively independently.
Make sure your user stories meet the INVEST criteria - Each unit of work should be Independent, Negotiable, Valuable, Estimatable, Small, and Testable.  If they're frequently producing things that are whole and useful, they'll quickly gain confidence in their judgment.
Define your stories in 3-7 words - Our index cards only had a handful of words on each of them. That forced us to have frequent discussions, rather than building documents. Remember, stories are just tokens for conversations, not mini-specs.
Do regular user testing - We had 4 people in every Tuesday afternoon, and rigged it so engineers could watch remotely. We loved it. Nothing creates an understanding of customer problems like seeing customers having problems.
Don't create features, solve problems - If you're telling them "go build Feature X" and expect them to make the thing you imagine, they're going to want a spec. Instead, have them solve problems. E.g., "Users are struggling with problem Y; come up with some solutions, test them out, and then let's pick the best one together."
Don't manage; mentor - Our society trains employees to do what bosses tell them to do. If you act like a manager, they'll act like minions. Instead, whenever they come to you for instructions, mentor them in doing whatever it is that generates the instructions.
Discuss this frankly in your retrospectives - Since you say you're an Agile shop, that means you must be doing retrospectives, hopefully weekly. Bring it up with them, and ask what you can do to help them be more engaged and independent. 

Get all that working and I'd be surprised if you still have this problem.

P.S. I'm glad to discuss this further in comments. Or feel free to send me an email or a Quora message if there's private stuff.]]></description>
<dc:subject>programming management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:9a2572844d4c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=16076932">
    <title>How does GDB call functions? | Hacker News</title>
    <dc:date>2018-01-05T18:00:20+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=16076932</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>c programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:7ff6735d8557/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://danluu.com/learning-to-program/">
    <title>How I learned to program</title>
    <dc:date>2017-12-26T21:58:30+00:00</dc:date>
    <link>https://danluu.com/learning-to-program/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[That would have been educational regardless of the methodology used, but it was a particularly great learning experience because of how the design was done. We started with a lengthy discussion on what core algorithm we were going to use. After we figured out an algorithm that would give us acceptable performance, we coded up design docs for every major module before getting serious about implementation.

Many people consider writing design docs to be a waste of time nowadays, but going through this process, which took months, had a couple big advantages. The first is that working through a design collaboratively teaches everyone on the team everyone else’s tricks. It’s a lot like the kind of skill transfer you get with pair programming, but applied to design. This was great for me, because as someone with only a decade of experience, I was one of the least experienced people in the room.

The second is that the iteration speed is much faster in the design phase, where throwing away a design just means erasing a whiteboard. Once you start coding, iterating on the design can mean throwing away code; for infrastructure projects, that can easily be person-years or even tens of persons-years of work. Since working on the TPU project, I’ve seen a couple of teams on projects of similar scope insist on getting “working” code as soon as possible. In every single case, that resulted in massive delays as huge chunks of code had to be re-written, and in a few cases the project was fundamentally flawed in a way that required the team had to start over from scratch.

I get that on product-y projects, where you can’t tell how much traction you’re going to get from something, you might want to get an MVP out the door and iterate, but for pure infrastructure, it’s often possible to predict how useful something will be in the design phase.

...

The most common sort of career advice I see is “you should do what I did because I’m successful”. It’s usually phrased differently, but that’s the gist of it. That basically never works. When I compare notes with friends and acquaintances, it’s pretty clear that my career has been unusual in a number of ways, but it’s not really clear why.

]]></description>
<dc:subject>programming funny design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:daf75fe32711/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:funny"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://serverless.com/blog/serverless-aurora-future-of-data/">
    <title>Serverless Aurora: What it means and why it's the future of data</title>
    <dc:date>2017-12-05T00:43:06+00:00</dc:date>
    <link>https://serverless.com/blog/serverless-aurora-future-of-data/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:29f248cb643c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://smmry.com/">
    <title>SMMRY - Summarize Everything</title>
    <dc:date>2017-11-30T16:54:31+00:00</dc:date>
    <link>http://smmry.com/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[todo: look into]]></description>
<dc:subject>api programming cloudai</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:7772db7e50a5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:cloudai"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nbviewer.jupyter.org/url/norvig.com/ipython/Advent%20of%20Code.ipynb">
    <title>Jupyter Notebook Viewer</title>
    <dc:date>2017-11-30T16:51:41+00:00</dc:date>
    <link>http://nbviewer.jupyter.org/url/norvig.com/ipython/Advent%20of%20Code.ipynb</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[todo: blog post subject, review basics of all norvig's day0 setup?]]></description>
<dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:f05be25e4e1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=15813318">
    <title>Advent of Code 2017 | Hacker News</title>
    <dc:date>2017-11-30T16:50:01+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=15813318</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:8bfe8ddef899/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/danluu/debugging-stories">
    <title>danluu/debugging-stories: A collection of debugging stories. PRs welcome :-)</title>
    <dc:date>2017-11-27T18:56:02+00:00</dc:date>
    <link>https://github.com/danluu/debugging-stories</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d8fc3ba7eebe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://forum.arduino.cc/index.php?topic=325886.0">
    <title>SPI SD Card Speed Reading..</title>
    <dc:date>2017-11-24T17:29:39+00:00</dc:date>
    <link>http://forum.arduino.cc/index.php?topic=325886.0</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[I used a high-end 32 GB SanDisk card.

512 byte block read: 499.5 KB/sec

64 byte block read: 316.3 KB/sec

8 byte block read: 125.4 KB/sec

2 byte block read: 40.4 KB/sec

1 byte reads: 24.0 KB/sec

peek followed by 1 byte read: 12.1 KB/sec

SD is not a good substitute for external SPI RAM for small reads.]]></description>
<dc:subject>programming embedded sd</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:fbee6bbbb069/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:embedded"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:sd"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://elm-chan.org/docs/mmc/mmc_e.html">
    <title>How to Use MMC/SDC</title>
    <dc:date>2017-11-24T16:39:35+00:00</dc:date>
    <link>http://elm-chan.org/docs/mmc/mmc_e.html</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[MMC/SDC can work at the clock frequency upto 20/25 MHz. Of course all native interfaces guarantee to work at the maximum clock frequency. However generic SPI interface integrated in the microcontrollers may not work at high clock frequency due to a timing issue. Right image shows the timing diagram of the SPI interface. In SPI mode 0/3, the data is shifted out by falling edge of the SCLK and latched by next rising edge. td is the SCLK to DO propagation delay at the SDC, 14ns maximum. tsu is the minimum setup time of the MISO input. Therefore the maximum allowable SCLK frequency can be calculated by:
FSCLK(max) = 0.5 / (td + tsu)
Some microcontrollers I have used are limited the allowable clock frequency around 10 MHz according to the timing specs.
]]></description>
<dc:subject>embedded sd programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:13c162e31856/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:embedded"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:sd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.avrfreaks.net/forum/spi-clock-rate-and-sd-cards">
    <title>SPI Clock Rate and SD Cards | AVR Freaks</title>
    <dc:date>2017-11-24T16:01:50+00:00</dc:date>
    <link>http://www.avrfreaks.net/forum/spi-clock-rate-and-sd-cards</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[Keep in mind that, regardless of the clock rate you're using, the AVR may be driving slaves with much faster SPI ports, with clock speeds well in the VHF region.  This means, a noise spike might be invisible for the AVR but a slave might see it as 2 clock pulses, leading to sync errors very hard to trace.
This checklist saved me a lot of trouble on those cases:
 
- Check the bus timings on the datasheet: /CS guard times, clock edge setup time, etc.
- Check the SPI mode, clock idle state, which clock edge I should write or read to the slave, etc.
- Identify with oscilloscope any noise sources on the board.  Typical cases are switch-mode regulators, other data buses (I2C, UARTs, USB, etc.), stepper drivers, speaker amplifiers (Class-D), oscillators, RTC, etc.  Set the SPI clock frequency as far as possible from all noise frequencies.
- Use pull-ups on all SPI lines with the min resistance allowed in the datasheets.
- All SPI tracks running parallel to each other and a GND plane below.
- If using 4-layer boards, the SPI tracks can be "sandwiched" between GND planes.
- Non-SPI tracks always crossing the bus tracks at 90º and never running parallel.
- Inductive filters like ferrite beads or PCB vias, placed close to the receiving pins (MISO on AVR, MOSI and SCK on slaves)
- Assume a worst case scenario. Fragment large streams of data where possible, add CRC or parity check to data, verify commands sent, reset slaves if necessary, etc.
- Minimize bus usage, for example block writes send the start address once, while word writes send the address with every data word, etc.]]></description>
<dc:subject>programming embedded sd</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:c48ecd2402d2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:embedded"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:sd"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.eugenewei.com/blog/2017/11/13/remove-the-legend">
    <title>Remove the legend to become one — Remains of the Day</title>
    <dc:date>2017-11-15T14:01:00+00:00</dc:date>
    <link>http://www.eugenewei.com/blog/2017/11/13/remove-the-legend</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[My other source of grief was another tool of deep fragility: linked spreadsheets in Excel 97. I am, to this day, an advocate for Excel, the best tool in the Microsoft Office suite, and still, if you're doing serious work, the top spreadsheet on the planet. However, I'll never forget the nightmare of linked workbooks in Excel 97, an idea which sounded so promising in theory and worked so inconsistently in practice.

Why not just use one giant workbook? Various departments had to submit data for different graphs, and back then it was a complete mess to have multiple people work in the same Excel spreadsheet simultaneously. Figuring out whose changes stuck, that whole process of diffs, was untenable. So I created Excel workbooks for all the different departments. Some of the data I'd collect myself and enter by hand, while some departments had younger employees with the time and wherewithal to enter and maintain the data for their organization.

[todo: python or js function for graph style]]]></description>
<dc:subject>programming software visualization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:1ea4f8fc7bc4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:visualization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.nominum.com/tech-blog/domain-correlation-just-let-malware-beat/">
    <title>Domain Correlation: just let the malware beat itself — Nominum</title>
    <dc:date>2017-11-13T17:44:37+00:00</dc:date>
    <link>https://www.nominum.com/tech-blog/domain-correlation-just-let-malware-beat/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>visualization ai ml programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:feeb9a39fd70/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:ml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://research.googleblog.com/2017/11/fused-video-stabilization-on-pixel-2.html">
    <title>Research Blog: Fused Video Stabilization on the Pixel 2 and Pixel 2 XL</title>
    <dc:date>2017-11-10T22:05:07+00:00</dc:date>
    <link>https://research.googleblog.com/2017/11/fused-video-stabilization-on-pixel-2.html</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[You’ll notice that it’s still not very stable. To further improve the quality, we trained a model to extract intentional motions from the noisy real camera motions. We then apply additional filters given the predicted motion. For example, if we predict the camera is panning horizontally, we would reject more vertical motions. The result is shown below.

[other projects that detect intention?]]]></description>
<dc:subject>programming ai ml</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d141ed57360f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:ml"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://r4ds.had.co.nz/model-basics.html">
    <title>R for Data Science</title>
    <dc:date>2017-11-03T17:31:56+00:00</dc:date>
    <link>http://r4ds.had.co.nz/model-basics.html</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming statistics linreg</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:16ddd1fc758b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:linreg"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/knsv/mermaid">
    <title>knsv/mermaid: Generation of diagram and flowchart from text in a similar manner as markdown</title>
    <dc:date>2017-10-31T13:20:39+00:00</dc:date>
    <link>https://github.com/knsv/mermaid</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>markdown programming design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:ad4f4dc4f0c6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hillelwayne.com/post/why-tdd-isnt-crap/">
    <title>Why TDD Isn't Crap • Hillel Wayne</title>
    <dc:date>2017-10-31T13:18:59+00:00</dc:date>
    <link>https://hillelwayne.com/post/why-tdd-isnt-crap/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:2d7a87189309/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=15582969">
    <title>https://news.ycombinator.com/item?id=15582969</title>
    <dc:date>2017-10-30T16:38:42+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=15582969</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming verification</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:0bcca20e669c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:verification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://code.facebook.com/posts/1537144479682247/finding-inter-procedural-bugs-at-scale-with-infer-static-analyzer/">
    <title>Finding inter-procedural bugs at scale with Infer static analyzer | Engineering Blog | Facebook Code</title>
    <dc:date>2017-10-13T14:58:20+00:00</dc:date>
    <link>https://code.facebook.com/posts/1537144479682247/finding-inter-procedural-bugs-at-scale-with-infer-static-analyzer/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>analysis code sec programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:40912c447061/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:sec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.hillelwayne.com/post/handwriting-j/">
    <title>Handwriting Programs in J • Hillel Wayne</title>
    <dc:date>2017-10-11T17:12:07+00:00</dc:date>
    <link>https://www.hillelwayne.com/post/handwriting-j/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:7cf5fa3608b0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.reddit.com/r/programming/comments/73nnv1/clever_way_of_skirting_game_code_quality_tests/">
    <title>Clever way of skirting game code quality tests from the 90s (x-post /r/Games) : programming</title>
    <dc:date>2017-10-02T01:19:12+00:00</dc:date>
    <link>https://www.reddit.com/r/programming/comments/73nnv1/clever_way_of_skirting_game_code_quality_tests/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:b252b8ab8e15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/hmemcpy/milewski-ctfp-pdf">
    <title>hmemcpy/milewski-ctfp-pdf: Bartosz Milewski's 'Category Theory for Programmers' unofficial PDF and LaTeX source</title>
    <dc:date>2017-09-30T18:57:23+00:00</dc:date>
    <link>https://github.com/hmemcpy/milewski-ctfp-pdf</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming tex</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:7e671ffa2970/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:tex"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=JIQETrFC_SQ&amp;list=WL&amp;index=18">
    <title>AWS re:Invent 2014: AWS Innovation at Scale with James Hamilton (SPOT301) - YouTube</title>
    <dc:date>2017-09-28T03:05:57+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=JIQETrFC_SQ&amp;list=WL&amp;index=18</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[@11 min cost breakdown cloud ]]></description>
<dc:subject>programming aws</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d00cda01f064/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:aws"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dnsviz.net/d/87.is/analyze/">
    <title>87.is | DNSViz</title>
    <dc:date>2017-09-27T21:55:44+00:00</dc:date>
    <link>http://dnsviz.net/d/87.is/analyze/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>dns programming webdev</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:3cfba2077bf8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:dns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:webdev"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.oath.com/press/open-sourcing-vespa-yahoo-s-big-data-processing-and-serving-eng/">
    <title>Open Sourcing Vespa, Yahoo’s Big Data Processing and Serving Engine</title>
    <dc:date>2017-09-27T14:55:19+00:00</dc:date>
    <link>https://www.oath.com/press/open-sourcing-vespa-yahoo-s-big-data-processing-and-serving-eng/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[To achieve both speed and scale, Vespa distributes data and computation over many machines without any single master as a bottleneck. Where conventional applications work by pulling data into a stateless tier for processing, Vespa instead pushes computations to the data. This involves managing clusters of nodes with background redistribution of data in case of machine failures or the addition of new capacity, implementing distributed low latency query and processing algorithms, handling distributed data consistency, and a lot more. It's a ton of hard work!

As the team behind Vespa, we have been working on developing search and serving capabilities ever since building alltheweb.com, which was later acquired by Yahoo. Over the last couple of years we have rewritten most of the engine from scratch to incorporate our experience onto a modern technology stack. Vespa is larger in scope and lines of code than any open source project we've ever released. Now that this has been battle-proven on Yahoo's largest and most critical systems, we are pleased to release it to the world.]]></description>
<dc:subject>programming webdev</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:5ea5429781a0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:webdev"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blogs.dropbox.com/tech/2017/09/optimizing-web-servers-for-high-throughput-and-low-latency/">
    <title>Optimizing web servers for high throughput and low latency | Dropbox Tech Blog</title>
    <dc:date>2017-09-06T19:05:02+00:00</dc:date>
    <link>https://blogs.dropbox.com/tech/2017/09/optimizing-web-servers-for-high-throughput-and-low-latency/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[Application level: Highlevel
To analyze effectiveness of your optimizations on that level you will need to collect RUM data. In browsers you can use Navigation Timing APIs and Resource Timing APIs. Your main metrics are TTFB and TTV/TTI. Having that data in an easily queriable and graphable formats will greatly simplify iteration.

]]></description>
<dc:subject>programming performance perf</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:c359d2aca8f7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:perf"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://samwho.co.uk/blog/2017/09/06/move-your-bugs-to-the-left/">
    <title>Move Your Bugs to the Left</title>
    <dc:date>2017-09-06T17:42:01+00:00</dc:date>
    <link>http://samwho.co.uk/blog/2017/09/06/move-your-bugs-to-the-left/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:4fa0c3b9a204/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://jakevdp.github.io/PythonDataScienceHandbook/05.06-linear-regression.html">
    <title>In Depth: Linear Regression | Python Data Science Handbook</title>
    <dc:date>2017-09-01T22:41:10+00:00</dc:date>
    <link>https://jakevdp.github.io/PythonDataScienceHandbook/05.06-linear-regression.html</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>python programming statistics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:f5dafd12b7b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:statistics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://zipcpu.com/blog/2017/08/21/rules-for-newbies.html">
    <title>Rules for new FPGA designers</title>
    <dc:date>2017-08-25T16:40:19+00:00</dc:date>
    <link>http://zipcpu.com/blog/2017/08/21/rules-for-newbies.html</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming debugging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:0da879c0bb8d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:debugging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.theatlantic.com/technology/archive/2017/08/inside-waymos-secret-testing-and-simulation-facilities/537648/">
    <title>Inside Waymo's Secret World for Training Self-Driving Cars - The Atlantic</title>
    <dc:date>2017-08-23T18:19:13+00:00</dc:date>
    <link>https://www.theatlantic.com/technology/archive/2017/08/inside-waymos-secret-testing-and-simulation-facilities/537648/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[“That iteration cycle is tremendously important to us and all the work we’ve done on simulation allows us to shrink it dramatically,” Dolgov told me. “The cycle that would take us weeks in the early days of the program now is on the order of minutes.”]]></description>
<dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:5ed671e7f085/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://graydon2.dreamwidth.org/253769.html">
    <title>graydon2 | &quot;What next?&quot;</title>
    <dc:date>2017-08-19T18:57:38+00:00</dc:date>
    <link>http://graydon2.dreamwidth.org/253769.html</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming proglang</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:143a87578fa5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:proglang"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fermatslibrary.com/s/the-emperors-old-clothes">
    <title>Fermat's Library | The Emperor's Old Clothes annotated/explained version.</title>
    <dc:date>2017-07-20T16:29:42+00:00</dc:date>
    <link>http://fermatslibrary.com/s/the-emperors-old-clothes</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[ What was 
amazing  was  that  a  large  team  of  highly  intelligent 
programmers could labor so  hard  and  so long on such 
an unpromising project.

[ ... ]

ust recently, I have discovered that an early advocate 
of the assertional  method of program  proving was none 
other  than Alan  Turing himself. On June 24,  1950 at  a 
conference in Cambridge,  he gave a  short talk entitled, 
"Checking  a  Large  Routine"  which  explains  the  idea 
with great clarity.  "How can one check a large routine in 
the  sense  of making  sure that  it's  right? In  order that  the 
man who  checks may  not  have too  difficult  a  task,  the 
programmer should make a number of definite 
assertions which can  be  checked individually, and from which  the 
correctness of the  whole  program  easily  follows.]]></description>
<dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d4f29af09ffc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://engineering.tumblr.com/post/161854099032/jetpants-integration-testing">
    <title>Tumblr Engineering — Jetpants Integration Testing</title>
    <dc:date>2017-06-15T16:29:28+00:00</dc:date>
    <link>https://engineering.tumblr.com/post/161854099032/jetpants-integration-testing</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>testing programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:e52580387ce1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.reddit.com/r/programming/comments/6gr2fc/til_the_current_hash_function_for_java_strings_is/disnr9v/">
    <title>LeifCarrotson comments on TIL the current hash function for Java strings is of unknown author. In 2004 Joshua Bloch &quot;went so far as to call up Dennis Ritchie, who said that he did not know where the hash function came from. He walked across the hall and a</title>
    <dc:date>2017-06-13T23:16:22+00:00</dc:date>
    <link>https://www.reddit.com/r/programming/comments/6gr2fc/til_the_current_hash_function_for_java_strings_is/disnr9v/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>funny programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d7942c33132c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:funny"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.jackkinsella.ie/articles/programming-accounting-features-in-web-apps">
    <title>Tips for Programming Accounting Features in Web Apps | Jack Kinsella</title>
    <dc:date>2017-06-06T18:18:57+00:00</dc:date>
    <link>https://www.jackkinsella.ie/articles/programming-accounting-features-in-web-apps</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>business accounting programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:dd4fddab3bbc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:accounting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://cosette.cs.washington.edu/">
    <title>Cosette: An Automated SQL Solver</title>
    <dc:date>2017-06-05T19:06:59+00:00</dc:date>
    <link>http://cosette.cs.washington.edu/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming sql</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:a03871290093/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:sql"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://btorpey.github.io/blog/2016/11/12/even-mo-static/">
    <title>Even Mo' Static - Confessions of a Wall Street Programmer</title>
    <dc:date>2017-06-01T15:32:56+00:00</dc:date>
    <link>http://btorpey.github.io/blog/2016/11/12/even-mo-static/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:060c59c3f022/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kubernetesbyexample.com/">
    <title>Kubernetes By Example</title>
    <dc:date>2017-05-31T16:31:25+00:00</dc:date>
    <link>http://kubernetesbyexample.com/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:a1d230d24bb4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://segment.com/blog/spotting-a-million-dollars-in-your-aws-account/">
    <title>Spotting a million dollars in your AWS account · Segment Blog</title>
    <dc:date>2017-05-18T19:09:06+00:00</dc:date>
    <link>https://segment.com/blog/spotting-a-million-dollars-in-your-aws-account/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[https://news.ycombinator.com/item?id=14366881

However, you can enable certain tags to appear alongside your line item costs using cost allocation tags. 

These tags are officially supported by many AWS resources, S3 buckets, DynamoDB tables, etc. You can toggle a setting in the AWS billing console to make a cost allocation tag show up in the CSV. After a day or so, your chosen tag (we chose product_area) will start showing up as a new column next to the associated resources in the detailed billing CSV. 

If you are doing nothing else, start by using cost allocation tags to tag your infrastructure. It’s essentially ‘free’ and requires zero infrastructure to run.

After we enabled cost allocation tags, we had two challenges: 1) tagging all of the existing infrastructure, and 2) ensuring that any new resources would automatically have tags.]]></description>
<dc:subject>aws programming business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:e9eb5a8a8db4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Fluidics">
    <title>Fluidics - Wikipedia</title>
    <dc:date>2017-05-10T19:21:20+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Fluidics</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:8757f0810360/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/MarcoPon/SeqBox">
    <title>MarcoPon/SeqBox: A single file container/archive that can be reconstructed even after total loss of file system structures</title>
    <dc:date>2017-05-08T18:56:44+00:00</dc:date>
    <link>https://github.com/MarcoPon/SeqBox</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming archive data</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:543180da9688/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:archive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:data"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://t3x.org/t3x/">
    <title>The T3X Language and Compiler - T3X.ORG</title>
    <dc:date>2017-05-05T21:10:09+00:00</dc:date>
    <link>http://t3x.org/t3x/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>book programming proglang</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:32d3554ab46a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:book"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:proglang"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://landing.google.com/sre/book/chapters/data-integrity.html">
    <title>Google - Site Reliability Engineering</title>
    <dc:date>2017-05-04T20:51:48+00:00</dc:date>
    <link>https://landing.google.com/sre/book/chapters/data-integrity.html</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[Similar reasoning applies to applications like Google Photos, Drive, Cloud Storage, and Cloud Datastore, because users don’t necessarily draw a distinction between these discrete products (reasoning, "this product is still Google" or "Google, Amazon, whatever; this product is still part of the cloud"). Data loss, data corruption, and extended unavailability are typically indistinguishable to users. Therefore, data integrity applies to all types of data across all services. When considering data integrity, what matters is that services in the cloud remain accessible to users. User access to data is especially important.]]></description>
<dc:subject>programming testing saas postmortem recovery</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:a06ff843b0fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:saas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:postmortem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:recovery"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://landing.google.com/sre/book/chapters/testing-reliability.html">
    <title>Google - Site Reliability Engineering</title>
    <dc:date>2017-05-04T20:44:18+00:00</dc:date>
    <link>https://landing.google.com/sre/book/chapters/testing-reliability.html</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:8b1e3131feff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=14221848">
    <title>Formal Methods in Practice: Using TLA+ at ESpark | Hacker News</title>
    <dc:date>2017-05-02T21:52:15+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=14221848</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[todo: list of high-leverage design tools.]]></description>
<dc:subject>programming design todo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:4c9c3fd5d3f6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:todo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Miserlou/Zappa#basic-usage">
    <title>Miserlou/Zappa: Serverless Python Web Services</title>
    <dc:date>2017-05-01T18:40:04+00:00</dc:date>
    <link>https://github.com/Miserlou/Zappa#basic-usage</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming webdev todo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:8a9f35b39bea/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:webdev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:todo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/espark-engineering-blog/formal-methods-in-practice-8f20d72bce4f">
    <title>Formal Methods in Practice – eSpark Engineering Blog – Medium</title>
    <dc:date>2017-04-28T19:35:36+00:00</dc:date>
    <link>https://medium.com/espark-engineering-blog/formal-methods-in-practice-8f20d72bce4f</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[Our tool of choice is TLA+. First, we specify the system as a giant abstract state machine and list all of the possible transitions it can make. Then, we specify invariants of the system, properties that every state must have. Finally, we run the model checker, called TLC, on the spec. TLC exhaustively checks all possible states and raises an error if any state violates the invariant. Here’s our initial design:

[todo: use on mblog?]]]></description>
<dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:87ae79fa5aec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://zipkin.io/">
    <title>OpenZipkin · A distributed tracing system</title>
    <dc:date>2017-04-25T19:22:01+00:00</dc:date>
    <link>http://zipkin.io/</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[google dapper
]]></description>
<dc:subject>distributed monitoring performance programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:843e6a382a9e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:monitoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.ycombinator.com/founder-stories-kate-heddleston/">
    <title>Founder Stories: Kate Heddleston of Opsolutely</title>
    <dc:date>2017-04-24T20:03:33+00:00</dc:date>
    <link>https://blog.ycombinator.com/founder-stories-kate-heddleston/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>business programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:3dd8ba2344f5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=14183767">
    <title>High-performance .NET by example: Filtering bot traffic | Hacker News</title>
    <dc:date>2017-04-24T19:57:28+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=14183767</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>performance programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:b79ee0a4cd41/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.goodreads.com/author_blog_posts/2484147-lessons-i-learned-at-mcdonald-s-that-help-me-build-software">
    <title>Goodreads | Ed Weissman's Blog - Lessons I Learned at McDonald's that Help Me Build Software - May 21, 2012 10:58</title>
    <dc:date>2017-04-20T19:30:37+00:00</dc:date>
    <link>https://www.goodreads.com/author_blog_posts/2484147-lessons-i-learned-at-mcdonald-s-that-help-me-build-software</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[7. Good work habits are like antibodies; once you get them, you have them for life.
There were 2 kinds of workers at McDonald's, those who got the work done properly and completely, no matter what, and everyone else. It only took about 5 minutes to tell who was who. And it never changed. Both groups were equally smart, equally capable, and equally personable. What was the critical difference? Work habits. Good workers refused to work in dirty work areas. They refused to release deficient product. They refused to put off what could be done later because they knew it would grow to twice as much work later and screw everything else up in the interim. And most of all, they hated working with those who didn't have the same good habits. Why should I get the product out hot, mop the floor, wipe the counters, stock the freezer, and prepare for closing while Jimmy has a smoke and hangs out in the back. Get him off my shift!
Years later, it's still the same. Got a critical project with a tough deadline?  Need to put out great product quickly and efficiently? Who you gonna call, the brilliant guy who sits and pontificates all night or the one who understands what it takes and won't quit until he's done. Work habits separate the good from the great and show you the way to success. Once you have that taste, it's awfully hard to become a slacker.
]]></description>
<dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:a399660252a8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://steve-yegge.blogspot.ca/2008/06/done-and-gets-things-smart.html">
    <title>Stevey's Blog Rants: Done, and Gets Things Smart</title>
    <dc:date>2017-04-19T22:26:19+00:00</dc:date>
    <link>http://steve-yegge.blogspot.ca/2008/06/done-and-gets-things-smart.html</link>
    <dc:creator>notaddicted</dc:creator><description><![CDATA[At first it's entirely non-obvious who's responsible for Google's culture of engineering discipline: the design docs, audited code reviews, early design reviews, readability reviews, resisting introduction of new languages, unit testing and code coverage, profiling and performance testing, etc. You know. The whole gamut of processes and tools that quality engineering organizations use to ensure that code is open, readable, documented, and generally non-shoddy work.]]></description>
<dc:subject>programming management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:adbd646e36d0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Pearson_correlation_coefficient">
    <title>Pearson correlation coefficient - Wikipedia</title>
    <dc:date>2017-04-17T19:29:16+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Pearson_correlation_coefficient</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming math statistics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d355e4180389/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:math"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:statistics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@cheapsteak/quick-and-dirty-tricks-for-debugging-javascript-d0e911c3afa">
    <title>Quick and dirty tricks for debugging Javascript 🕵 – Chang Wang – Medium</title>
    <dc:date>2017-04-11T17:53:21+00:00</dc:date>
    <link>https://medium.com/@cheapsteak/quick-and-dirty-tricks-for-debugging-javascript-d0e911c3afa</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming debugging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:7d9d71d43a00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:debugging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.redbubble.com/people/ange4771/works/11126212-elf101-a-linux-executable-walkthrough?c=249202-elf101-all-versions">
    <title>&quot;ELF101 a Linux executable walkthrough&quot; Posters by Ange Albertini | Redbubble</title>
    <dc:date>2017-04-07T22:07:47+00:00</dc:date>
    <link>https://www.redbubble.com/people/ange4771/works/11126212-elf101-a-linux-executable-walkthrough?c=249202-elf101-all-versions</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming buy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d4d6b7731938/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:buy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=14046446">
    <title>Build Your Own Text Editor | Hacker News</title>
    <dc:date>2017-04-06T21:40:18+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=14046446</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming edu</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:f392d833e4ab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:edu"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://aosabook.org/en/index.html">
    <title>The Architecture of Open Source Applications</title>
    <dc:date>2017-04-06T21:31:53+00:00</dc:date>
    <link>http://aosabook.org/en/index.html</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming book edu</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:033323d173c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:book"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:edu"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://viewsourcecode.org/snaptoken/kilo/index.html">
    <title>Table of contents | Build Your Own Text Editor</title>
    <dc:date>2017-04-06T21:30:43+00:00</dc:date>
    <link>http://viewsourcecode.org/snaptoken/kilo/index.html</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:8112082cc6c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://myers.io/2017/04/04/the-joel-test-for-2017/">
    <title>The Joel Test for 2017 - myers.io</title>
    <dc:date>2017-04-06T19:58:25+00:00</dc:date>
    <link>https://myers.io/2017/04/04/the-joel-test-for-2017/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:b2682fc4fcff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/madler/zlib/commit/51370f365607fe14a6a7a1a27b3bd29d788f5e5b">
    <title>Fix serious but very rare decompression bug in inftrees.c. · madler/zlib@51370f3</title>
    <dc:date>2017-04-06T17:08:55+00:00</dc:date>
    <link>https://github.com/madler/zlib/commit/51370f365607fe14a6a7a1a27b3bd29d788f5e5b</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming debugging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:c13ca5e8f33a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:debugging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://automatetheboringstuff.com/">
    <title>Automate the Boring Stuff with Python</title>
    <dc:date>2017-04-05T20:01:45+00:00</dc:date>
    <link>https://automatetheboringstuff.com/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>python programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:d07c9e9cf5e2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.diveintopython3.net/">
    <title>Dive Into Python 3</title>
    <dc:date>2017-04-05T20:01:34+00:00</dc:date>
    <link>http://www.diveintopython3.net/</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>python programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:9ce3e68c2b03/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=14034401">
    <title>Secure C coding standards by SEI | Hacker News</title>
    <dc:date>2017-04-05T18:01:56+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=14034401</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:e67660e640c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.skyliner.io/fourteen-months-with-clojure-beb8b3e4bf00">
    <title>Fourteen Months with Clojure – Skyliner</title>
    <dc:date>2017-03-31T22:39:11+00:00</dc:date>
    <link>https://blog.skyliner.io/fourteen-months-with-clojure-beb8b3e4bf00</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming clojure</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:b4a0ac406c86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:clojure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://stripe.com/blog/rate-limiters">
    <title>Scaling your API with rate limiters</title>
    <dc:date>2017-03-30T19:42:30+00:00</dc:date>
    <link>https://stripe.com/blog/rate-limiters</link>
    <dc:creator>notaddicted</dc:creator><dc:subject>programming api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:notaddicted/b:4674e3f42f62/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:notaddicted/t:api"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>