<?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 (rtlechow)</title>
    <link>https://pinboard.in/u:rtlechow/public/</link>
    <description>recent bookmarks from rtlechow</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.seangoedecke.com/how-i-estimate-work/"/>
	<rdf:li rdf:resource="https://github.com/hacksider/Deep-Live-Cam"/>
	<rdf:li rdf:resource="https://partyrock.aws/guide/getStarted"/>
	<rdf:li rdf:resource="http://nil.lcs.mit.edu/6.824/2020/schedule.html"/>
	<rdf:li rdf:resource="https://christophermeiklejohn.com/publications/cmeiklej_phd_s3d_2024.pdf"/>
	<rdf:li rdf:resource="https://github.com/o-oconnell/minixfromscratch"/>
	<rdf:li rdf:resource="https://mailchi.mp/railsspeed/a-barbell-strategy-for-performance?e=71459d59e6"/>
	<rdf:li rdf:resource="https://github.com/rvaiya/warpd"/>
	<rdf:li rdf:resource="https://blog.pragmaticengineer.com/rfcs-and-design-docs/"/>
	<rdf:li rdf:resource="https://github.com/hpjansson/chafa"/>
	<rdf:li rdf:resource="https://logseq.com/"/>
	<rdf:li rdf:resource="https://obsidian.md/"/>
	<rdf:li rdf:resource="http://tarotcardsoftech.artefactgroup.com/"/>
	<rdf:li rdf:resource="https://www.bespokesynth.com/"/>
	<rdf:li rdf:resource="https://iism.org/article/is-management-pressuring-you-to-deliver-unfinished-code-59"/>
	<rdf:li rdf:resource="https://martinfowler.com/articles/ship-show-ask.html#HowDoYouDoContinuousIntegrationWithPullRequests"/>
	<rdf:li rdf:resource="https://jessitron.com/2021/08/02/better-coordination-or-better-software/amp/?__twitter_impression=true"/>
	<rdf:li rdf:resource="https://www.intercom.com/blog/first-rule-prioritization-no-snacking/"/>
	<rdf:li rdf:resource="https://espanso.org/"/>
	<rdf:li rdf:resource="https://alerner1st.medium.com/the-strange-case-of-the-twiddle-wakka-5a70a0f5a509"/>
	<rdf:li rdf:resource="https://github.com/rust-analyzer/rust-analyzer/blob/d7c99931d05e3723d878bea5dc26766791fa4e69/docs/dev/architecture.md"/>
	<rdf:li rdf:resource="https://ghidra-sre.org/"/>
	<rdf:li rdf:resource="https://copyconstruct.medium.com/post-commit-reviews-b4cc2163ac7a"/>
	<rdf:li rdf:resource="https://eventmodeling.org/"/>
	<rdf:li rdf:resource="https://developers.google.com/web/updates/2020/02/chromium-chronicle"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=8uE6-vIi1rQ"/>
	<rdf:li rdf:resource="https://blog.jessitron.com/2020/04/14/measuring-effort-gets-you-effort/"/>
	<rdf:li rdf:resource="http://experimentguide.com/"/>
	<rdf:li rdf:resource="https://github.com/xi-editor/xi-editor"/>
	<rdf:li rdf:resource="https://github.com/trimstray/the-book-of-secret-knowledge"/>
	<rdf:li rdf:resource="https://gidi.io/2018/07/28/the-secret-sauce-to-an-effective-team.html"/>
	<rdf:li rdf:resource="https://userinject.com/#/"/>
	<rdf:li rdf:resource="https://seesparkbox.com/foundry/stop_giving_depressing_code_reviews?__s=wy767durrhvpwkebafhz"/>
	<rdf:li rdf:resource="https://avdi.codes/test-driven-re-implementation-with-josh-thompson/?__s=wy767durrhvpwkebafhz"/>
	<rdf:li rdf:resource="https://blog.newrelic.com/engineering/capacity-planning/"/>
	<rdf:li rdf:resource="http://www.thagomizer.com/blog/2017/06/18/there-is-no-perfect-interview.html"/>
	<rdf:li rdf:resource="http://www.gettingagile.com/2007/10/22/research-spikes-tracer-bullets-oh-my/"/>
	<rdf:li rdf:resource="https://www.stephenwolfram.com/livestreams/"/>
	<rdf:li rdf:resource="https://circleci.com/blog/what-we-ve-learned-about-hiring-engineering-managers/"/>
	<rdf:li rdf:resource="https://ronjeffries.com/articles/018-01ff/no-estimates-logic/"/>
	<rdf:li rdf:resource="https://pragprog.com/magazines/2013-02/estimation-is-evil"/>
	<rdf:li rdf:resource="https://www.fridayfwd.com/missing-out/##subForm2"/>
	<rdf:li rdf:resource="https://devdb.io/devdb"/>
	<rdf:li rdf:resource="https://www.michaelnygard.com/blog/2015/07/the-fear-cycle/"/>
	<rdf:li rdf:resource="https://www.intercom.com/blog/prioritizing-product-announcements-saas-world/"/>
	<rdf:li rdf:resource="http://www.maschall.com/development/2018/11/05/remote-vs-distributed.html"/>
	<rdf:li rdf:resource="https://www.joelonsoftware.com/2000/03/29/painless-software-schedules/"/>
	<rdf:li rdf:resource="http://www.priceintelligently.com/hubfs/Price-Intelligently-SaaS-Pricing-Strategy.pdf"/>
	<rdf:li rdf:resource="http://www.brightball.com/articles/reality-driven-development-fixing-project-management-in-software"/>
	<rdf:li rdf:resource="https://10words.io/"/>
	<rdf:li rdf:resource="https://medium.com/@timferriss/how-to-create-a-million-dollar-business-this-weekend-examples-appsumo-mint-chihuahuas-fae4dab10842"/>
	<rdf:li rdf:resource="https://www.protopie.io/"/>
	<rdf:li rdf:resource="http://www.littlepotatosoftware.com/alphababy_mac.html"/>
	<rdf:li rdf:resource="http://www.product-frameworks.com/"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Versioning_file_system#ITS"/>
	<rdf:li rdf:resource="https://www.onepagecrm.com/pricing"/>
	<rdf:li rdf:resource="http://boz.com/articles/ownership-and-entitlement.html"/>
	<rdf:li rdf:resource="https://michaelfeathers.silvrback.com/converting-queries-to-commands?__s=wy767durrhvpwkebafhz"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=14209168"/>
	<rdf:li rdf:resource="https://medium.com/@sitapati/the-impact-github-is-having-on-your-software-career-right-now-6ce536ec0b50"/>
	<rdf:li rdf:resource="http://ascii.textfiles.com/archives/5153?__s=wy767durrhvpwkebafhz"/>
	<rdf:li rdf:resource="http://www.cio.co.nz/article/466635/amazon_cto_stop_spending_money_undifferentiated_heavy_lifting_/"/>
	<rdf:li rdf:resource="https://uxdesign.cc/the-best-youtube-channels-for-designers-and-developers-eda97b38d46a#.dj4q41q1x"/>
	<rdf:li rdf:resource="http://programmingisterrible.com/post/139222674273/write-code-that-is-easy-to-delete-not-easy-to"/>
	<rdf:li rdf:resource="https://www.sidefx.com/"/>
	<rdf:li rdf:resource="https://www.indiehackers.com/businesses/fundraising-report-card"/>
	<rdf:li rdf:resource="http://c2.com/doc/everything.html"/>
	<rdf:li rdf:resource="https://m.signalvnoise.com/a-rant-against-maximization-b5091d75abda#.pul3bjos8"/>
	<rdf:li rdf:resource="https://www.hypergolix.com/"/>
	<rdf:li rdf:resource="https://hackernoon.com/why-microsoft-teams-flopped-and-what-it-means-for-slack-cb2bbfa53963#.bjepptaap"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.seangoedecke.com/how-i-estimate-work/">
    <title>How I estimate work as a staff software engineer</title>
    <dc:date>2026-01-26T21:16:37+00:00</dc:date>
    <link>https://www.seangoedecke.com/how-i-estimate-work/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[How I estimate work as a staff software engineer

There’s a kind of polite fiction at the heart of the software industry. It goes something like this:

Estimating how long software projects will take is very hard, but not impossible. A skilled engineering team can, with time and effort, learn how long it will take for them to deliver work, which will in turn allow their organization to make good business plans.
This is, of course, false. As every experienced software engineer knows, it is not possible to accurately estimate software projects. The tension between this polite fiction and its well-understood falseness causes a lot of strange activity in tech companies.

]]></description>
<dc:subject>estimation bestpractices engineering blog software programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:9ebf58953a18/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:estimation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:bestpractices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:blog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/hacksider/Deep-Live-Cam">
    <title>hacksider/Deep-Live-Cam: real time face swap and one-click video deepfake with only a single image</title>
    <dc:date>2025-04-24T14:16:23+00:00</dc:date>
    <link>https://github.com/hacksider/Deep-Live-Cam</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>machine image ml images ai software face swap github</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:06292870f726/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:machine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:image"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:images"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:face"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:swap"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:github"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://partyrock.aws/guide/getStarted">
    <title>PartyRock | Getting started</title>
    <dc:date>2025-03-02T15:12:24+00:00</dc:date>
    <link>https://partyrock.aws/guide/getStarted</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[PartyRock is a space where you can build AI-generated apps in a playground powered by Amazon Bedrock. It’s a fast and fun way to learn about generative AI.]]></description>
<dc:subject>ai software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:0c963dcff37d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nil.lcs.mit.edu/6.824/2020/schedule.html">
    <title>6.824 Schedule: Spring 2020</title>
    <dc:date>2025-03-02T15:10:12+00:00</dc:date>
    <link>http://nil.lcs.mit.edu/6.824/2020/schedule.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>course learning programming software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:f0baf27d2a09/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:course"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://christophermeiklejohn.com/publications/cmeiklej_phd_s3d_2024.pdf">
    <title>cmeiklej_phd_s3d_2024.pdf</title>
    <dc:date>2024-09-26T02:16:16+00:00</dc:date>
    <link>https://christophermeiklejohn.com/publications/cmeiklej_phd_s3d_2024.pdf</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>services architecture software netflix doordash</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:663dd6f68e48/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:doordash"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/o-oconnell/minixfromscratch">
    <title>o-oconnell/minixfromscratch: Development and compilation setup for the book version of MINIX (3.1.0) on QEMU</title>
    <dc:date>2023-02-21T13:58:56+00:00</dc:date>
    <link>https://github.com/o-oconnell/minixfromscratch</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>minix os software learning tutorial linux unix</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:f794b15dcfcc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:minix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:os"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:unix"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mailchi.mp/railsspeed/a-barbell-strategy-for-performance?e=71459d59e6">
    <title>A Barbell Strategy for Performance</title>
    <dc:date>2023-02-16T16:37:08+00:00</dc:date>
    <link>https://mailchi.mp/railsspeed/a-barbell-strategy-for-performance?e=71459d59e6</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[In performance work, I often find that work in the "middle" of the effort distribution lacks the effort-to-benefit ratio of the "low" and "high" effort ends.

Here's some examples of what I consider "low effort" performance work:
Tuning request queueing correctly
Changing environment variables
Using jemalloc
Setting up a CDN
And medium effort:
Fixing N+1s/optimizing ORM usage
Using flamegraphs to determine why a controller is spending lots of time executing Ruby
And high effort:
Re-architecting the site to use Turbo
Changing all of your site's Javascript tags to use async
Adding threaded concurrency (going from 1 thread to N threads)
Low effort performance work is almost always my first priority. While the risk and effort required to implement these changes is low, sometimes the benefits are massive. Jemalloc can cut memory usage by 50%. Fixing request queueing and autoscaling configuration can revolutionize how you scale. But these things are usually not actually that hard to implement. And sometimes, when you try these "tricks", they don't have a benefit. But who cares? You wasted an hour or two, at most, giving it a shot.]]></description>
<dc:subject>software ruby performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:5b050e6841a4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/rvaiya/warpd">
    <title>GitHub - rvaiya/warpd: A modal keyboard-driven virtual pointer</title>
    <dc:date>2022-11-06T15:25:56+00:00</dc:date>
    <link>https://github.com/rvaiya/warpd</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>keyboard ui linux software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:dd1036824126/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:keyboard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.pragmaticengineer.com/rfcs-and-design-docs/">
    <title>Companies Using RFCs or Design Docs and Examples of These - The Pragmatic Engineer</title>
    <dc:date>2022-09-11T20:23:20+00:00</dc:date>
    <link>https://blog.pragmaticengineer.com/rfcs-and-design-docs/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>rfc documentation software design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:aaf28e19a577/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rfc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/hpjansson/chafa">
    <title>hpjansson/chafa: 📺🗿 Terminal graphics for the 21st century.</title>
    <dc:date>2022-02-14T17:07:18+00:00</dc:date>
    <link>https://github.com/hpjansson/chafa</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>dev awesome art software cli</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:53c8db8d9794/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:dev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:awesome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cli"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://logseq.com/">
    <title>Logseq: A privacy-first, open-source knowledge base</title>
    <dc:date>2021-10-28T13:09:32+00:00</dc:date>
    <link>https://logseq.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>personal knowledge notes markdown software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:d197d91bcc5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:personal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:notes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://obsidian.md/">
    <title>Obsidian</title>
    <dc:date>2021-10-28T13:09:28+00:00</dc:date>
    <link>https://obsidian.md/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>personal knowledge notes markdown software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:eebb977ef31f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:personal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:notes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tarotcardsoftech.artefactgroup.com/">
    <title>The Tarot Cards Of Tech</title>
    <dc:date>2021-10-21T13:17:37+00:00</dc:date>
    <link>http://tarotcardsoftech.artefactgroup.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>technology design tarot software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:4820721fac71/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:tarot"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.bespokesynth.com/">
    <title>Bespoke Synth</title>
    <dc:date>2021-10-14T02:29:23+00:00</dc:date>
    <link>https://www.bespokesynth.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>synthesizer synth macos music software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:ea2c22ece5c7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:synthesizer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:synth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:macos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:music"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://iism.org/article/is-management-pressuring-you-to-deliver-unfinished-code-59">
    <title>iiSM.org</title>
    <dc:date>2021-09-16T19:51:10+00:00</dc:date>
    <link>https://iism.org/article/is-management-pressuring-you-to-deliver-unfinished-code-59</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Engineers are problem solvers, and a manager who applies pressure becomes the problem the engineers decide they need to solve. If it is really important to deliver Something™ by the date, engineers will, if enough pressure is applied, deliver unfinished code by that date. Unfinished code that is full of race conditions, performance problems, outright bugs and worst of all, poor to non-existent product/market fit. Pressuring engineering teams to deliver Something™ by an arbitrary date can tank your entire business!

]]></description>
<dc:subject>career culture business development software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:862a486f3f29/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/articles/ship-show-ask.html#HowDoYouDoContinuousIntegrationWithPullRequests">
    <title>Ship / Show / Ask</title>
    <dc:date>2021-09-13T12:57:34+00:00</dc:date>
    <link>https://martinfowler.com/articles/ship-show-ask.html#HowDoYouDoContinuousIntegrationWithPullRequests</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[But the adoption of Pull Requests as the primary way of contributing code has created problems. We’ve lost some of the “Ready to Ship” mentality we had when we did Continuous Integration. Features-in-progress stay out of the way by delaying integration, and so we fall into the pitfalls of low-frequency integration that Continuous Integration sought to address.

Sometimes Pull Requests sit around and get stale, or we’re not sure what to work on while we wait for review. Sometimes they become bloated as we think “well, I may as well do this while I’m here.”

We also get tired of the number of Pull Requests we have to review, so we don't talk about the code anymore. We stop paying attention and we just click “Approve” or say “Looks good to me”.]]></description>
<dc:subject>ci software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:bc2f5f1afe20/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ci"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://jessitron.com/2021/08/02/better-coordination-or-better-software/amp/?__twitter_impression=true">
    <title>Better coordination, or better software? – Jessitron</title>
    <dc:date>2021-09-09T13:57:26+00:00</dc:date>
    <link>https://jessitron.com/2021/08/02/better-coordination-or-better-software/amp/?__twitter_impression=true</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Try this: instead of making coordination easier, imagine that it is really expensive. How would we do less?
To minimize coordination, establish boundaries and the few interfaces that cross them. Work carefully on those interfaces: document them thoroughly, and test on both sides. Change them sparingly and with effort: versioning, backwards compatibility, gradual deprecation.

Instead of asking when the other side of the boundary will be ready, assume we can’t know. Write contract tests, translation layers, and custom fakes for testing.

Treat the other department more like another company, like Software as a Service, where we can’t control their schedules. Where we can’t access their tracking tools.

Communicate heavily around the content of the interface. And nowhere else. This lets the departments work separately.



A strong boundary is like an extra component. It takes more work, but that work stays within the department, not across. There’s no task-level entanglement. Each team proceeds at its pace.
While some production releases may wait for all the components to be delivered, none of the components’ development is waiting on each other. That makes this faster than the highly-coordinated, tightly-coupled release. When difficulty increases with size (such as in software systems), several smaller systems can work more effectively than one larger system.

This decoupling requires more work on the software.
It’s faster, but is it cheaper? This takes more work: writing tests and fakes, architecting ports and adapters, changing those adapters when our first guess at the interface was wrong. It takes more building software.

That isn’t the work we wanted to do! We wanted to build software — oh wait.

The extra work to make clear boundaries makes better software.
The extra work of coordination only makes it take longer.

When we change the system later, strong boundaries make those changes faster. Deep coordination makes those changes harder: the tight coupling still exists but the armies have moved on, the armies of project managers who heroically held together that initial release.

The coordination is really expensive, too. More managers. Plus, software developers sitting on coordination calls, struggling to test, and waiting for dependencies are expensive (and unhappy).

Making coordination smoother increases coupling, requiring more coordination. The alternative is spending development effort on healthy boundaries. You can pay for better coordination, or better software.]]></description>
<dc:subject>business software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:379c7123c7c6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.intercom.com/blog/first-rule-prioritization-no-snacking/">
    <title>The first rule of prioritization: No snacking | Inside Intercom</title>
    <dc:date>2021-03-02T18:10:57+00:00</dc:date>
    <link>https://www.intercom.com/blog/first-rule-prioritization-no-snacking/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[The high-effort, high-impact work reflects the strategy you’re deliberately deploying. Everyone’s favorite quadrant is the low-effort, high-impact stuff. But when you continually pick the low-hanging fruit, the branches will stop growing, so this work dries up quickly as your product and team matures. Most startups are sensible enough to avoid the high-effort, low-impact work, so it’s the last quadrant that’s worth talking about.

It’s the low-effort, low-impact work that can kill you, because it’s so attractive. Hunter refers to it as “snacking”. It feels rewarding and can solve a short term problem, but if you never eat anything of substance you’ll suffer.]]></description>
<dc:subject>work business software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:1adbfbbde24d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://espanso.org/">
    <title>espanso - Cross-platform Text Expander written in Rust</title>
    <dc:date>2021-02-22T03:35:23+00:00</dc:date>
    <link>https://espanso.org/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>linux software productivity rust</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:a08a0fa18d38/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rust"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://alerner1st.medium.com/the-strange-case-of-the-twiddle-wakka-5a70a0f5a509">
    <title>The Strange Case of the Twiddle Wakka | by Alyssa Lerner First | Medium</title>
    <dc:date>2021-02-11T02:26:14+00:00</dc:date>
    <link>https://alerner1st.medium.com/the-strange-case-of-the-twiddle-wakka-5a70a0f5a509</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>ruby software programming history</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:2e37e34d50e1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:history"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/rust-analyzer/rust-analyzer/blob/d7c99931d05e3723d878bea5dc26766791fa4e69/docs/dev/architecture.md">
    <title>rust-analyzer/architecture.md at d7c99931d05e3723d878bea5dc26766791fa4e69 · rust-analyzer/rust-analyzer</title>
    <dc:date>2021-02-08T14:42:28+00:00</dc:date>
    <link>https://github.com/rust-analyzer/rust-analyzer/blob/d7c99931d05e3723d878bea5dc26766791fa4e69/docs/dev/architecture.md</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>rust architecture documentation software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:044c57f554b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ghidra-sre.org/">
    <title>Ghidra</title>
    <dc:date>2021-02-03T14:33:04+00:00</dc:date>
    <link>https://ghidra-sre.org/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[A software reverse engineering (SRE) suite of tools developed by NSA's Research Directorate in support of the Cybersecurity mission]]></description>
<dc:subject>security software hack</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:7662ad744fda/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:hack"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://copyconstruct.medium.com/post-commit-reviews-b4cc2163ac7a">
    <title>Post-Commit Reviews. I recently read an excellent article in… | by Cindy Sridharan | Medium</title>
    <dc:date>2021-01-18T15:14:26+00:00</dc:date>
    <link>https://copyconstruct.medium.com/post-commit-reviews-b4cc2163ac7a</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Benefits of Post-Commit Reviews
Focus
By far and away, the biggest benefit of post-commit reviews is developer focus.]]></description>
<dc:subject>ci management software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:550f2cc8f193/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ci"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://eventmodeling.org/">
    <title>Event Modeling - Designing Modern Information Systems</title>
    <dc:date>2020-07-21T23:56:50+00:00</dc:date>
    <link>https://eventmodeling.org/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>design software architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:6d4125be6033/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developers.google.com/web/updates/2020/02/chromium-chronicle">
    <title>The Chromium Chronicle: Catching UI Regressions with Pixel Tests  |  Web</title>
    <dc:date>2020-05-26T21:04:52+00:00</dc:date>
    <link>https://developers.google.com/web/updates/2020/02/chromium-chronicle</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Chrome’s testing strategy relies heavily on automated functional correctness tests and manual testing, but neither of these reliably catch minor UI regressions. Use pixel tests to automate testing your desktop browser UI.

When writing a pixel test, avoid flakiness by (1) disabling animation, (2) using mock data, and (3) testing the minimum possible surface area.]]></description>
<dc:subject>testing browser software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:eaeb0931e0ec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=8uE6-vIi1rQ">
    <title>Cursed Problems in Game Design - YouTube</title>
    <dc:date>2020-05-19T17:05:55+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=8uE6-vIi1rQ</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>design games video talks software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:a592ced2dff7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:talks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.jessitron.com/2020/04/14/measuring-effort-gets-you-effort/">
    <title>Measuring effort gets you effort – Jessitron</title>
    <dc:date>2020-05-04T18:07:59+00:00</dc:date>
    <link>https://blog.jessitron.com/2020/04/14/measuring-effort-gets-you-effort/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[When outcomes are hard to measure, we can measure activity toward those outcomes

which gets us more activity

]]></description>
<dc:subject>software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:c038a7fd9269/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://experimentguide.com/">
    <title>Experiment Guide – Accelerate innovation using trustworthy online controlled experiments</title>
    <dc:date>2020-05-01T12:26:46+00:00</dc:date>
    <link>http://experimentguide.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>experiments abtest software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:4cb99be1844c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:experiments"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:abtest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/xi-editor/xi-editor">
    <title>xi-editor/xi-editor: A modern editor with a backend written in Rust.</title>
    <dc:date>2020-02-12T14:25:33+00:00</dc:date>
    <link>https://github.com/xi-editor/xi-editor</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>software editor editors rust</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:de5dd10d28dd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:editor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:editors"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rust"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/trimstray/the-book-of-secret-knowledge">
    <title>trimstray/the-book-of-secret-knowledge: A collection of inspiring lists, manuals, cheatsheets, blogs, hacks, one-liners, cli/web tools and more.</title>
    <dc:date>2020-01-23T14:04:54+00:00</dc:date>
    <link>https://github.com/trimstray/the-book-of-secret-knowledge</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>linux security software tools github</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:ded4e85122d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:github"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gidi.io/2018/07/28/the-secret-sauce-to-an-effective-team.html">
    <title>The secret sauce to an effective team is a mix of Marmalade, Chutney and a little Tahini | Think, Write; Rethink, Rewrite.</title>
    <dc:date>2019-11-03T14:04:24+00:00</dc:date>
    <link>https://gidi.io/2018/07/28/the-secret-sauce-to-an-effective-team.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[These five dynamic are (This list is copy-pasted from the study):

Psychological safety Can we take risks on this team without feeling insecure or embarrassed?
Dependability Can we count on each other to do high quality work on time?
Structure & clarity Are goals, roles, and execution plans on our team clear?
Meaning of work Are we working on something that is personally important for each of us?
Impact of work Do we fundamentally believe that the work we’re doing matters?]]></description>
<dc:subject>teams software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:204f50edcc1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://userinject.com/#/">
    <title>Feedback Community</title>
    <dc:date>2019-06-20T15:56:02+00:00</dc:date>
    <link>https://userinject.com/#/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>user software saas feedback</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:4b0793d48616/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:user"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:saas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:feedback"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://seesparkbox.com/foundry/stop_giving_depressing_code_reviews?__s=wy767durrhvpwkebafhz">
    <title>Stop Giving Depressing Code Reviews</title>
    <dc:date>2019-05-28T16:02:25+00:00</dc:date>
    <link>https://seesparkbox.com/foundry/stop_giving_depressing_code_reviews?__s=wy767durrhvpwkebafhz</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[With that in mind, let me offer a simple suggestion for when you give code reviews:

Give as much positive feedback as you do correction.]]></description>
<dc:subject>software code review</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:581d85b681f1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:review"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://avdi.codes/test-driven-re-implementation-with-josh-thompson/?__s=wy767durrhvpwkebafhz">
    <title>Test-Driven Re-implementation with Josh Thompson – avdi.codes</title>
    <dc:date>2019-05-21T13:34:12+00:00</dc:date>
    <link>https://avdi.codes/test-driven-re-implementation-with-josh-thompson/?__s=wy767durrhvpwkebafhz</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>tdd reimplementation kata software ruby</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:8ae728f4676c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:tdd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:reimplementation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:kata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ruby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.newrelic.com/engineering/capacity-planning/">
    <title>Capacity Planning for Software Development Teams</title>
    <dc:date>2019-05-17T17:54:44+00:00</dc:date>
    <link>https://blog.newrelic.com/engineering/capacity-planning/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>newrelic capacity planning ops software devops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:c867214586d3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:newrelic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:capacity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:devops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.thagomizer.com/blog/2017/06/18/there-is-no-perfect-interview.html">
    <title>There Is No Perfect Interview</title>
    <dc:date>2019-03-21T01:10:35+00:00</dc:date>
    <link>http://www.thagomizer.com/blog/2017/06/18/there-is-no-perfect-interview.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Your grade will be calculated as follows:

25% Homework
25% 1st midterm
25% 2nd midterm
50% Final
Drop the lowest 25%

My interview process at Google (the time I got hired) used a variety of interview methods, and it felt fair. There were some trivia and whiteboard coding questions. My portfolio or previous talks and open source was reviewed. Someone attended one of my talks in person, and I had to prepare a talk to give to the interviewers as homework. ]]></description>
<dc:subject>software hiring</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:70ad392e67c7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:hiring"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.gettingagile.com/2007/10/22/research-spikes-tracer-bullets-oh-my/">
    <title>Research, Spikes, Tracer Bullets, Oh My! | Getting Agile</title>
    <dc:date>2019-02-26T17:34:42+00:00</dc:date>
    <link>http://www.gettingagile.com/2007/10/22/research-spikes-tracer-bullets-oh-my/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Spike – a quick and dirty implementation, designed to be thrown away, to gain knowledge – indicator: unable to estimate a user story effectively
Research – broad, foundational knowledge-gaining to decide what to spike or give the ability to estimate – indicator: don’t know a potential solution
Tracer Bullet – very narrow implementation in production quality of an epic/large user story – indicator: user story is too large in estimation]]></description>
<dc:subject>xp software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:22856297e3ed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:xp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.stephenwolfram.com/livestreams/">
    <title>Stephen Wolfram's Livestreams</title>
    <dc:date>2019-02-25T19:45:11+00:00</dc:date>
    <link>https://www.stephenwolfram.com/livestreams/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>wolfram ceo livestream software development meetings</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:d7e6dfec142c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:wolfram"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ceo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:livestream"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:meetings"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://circleci.com/blog/what-we-ve-learned-about-hiring-engineering-managers/">
    <title>What we’ve learned about hiring engineering managers - CircleCI</title>
    <dc:date>2019-01-31T19:49:04+00:00</dc:date>
    <link>https://circleci.com/blog/what-we-ve-learned-about-hiring-engineering-managers/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Applicant Review > Hiring Manager Phone Screen > Pairing Exercise > Product Thinking & Work Breakdown Discussion > Final Round (Engineering Team Member Interview, Management Skills Deep Dive, Product Interview]]></description>
<dc:subject>software hiring</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:ab71618451ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:hiring"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ronjeffries.com/articles/018-01ff/no-estimates-logic/">
    <title>#NoEstimates isn't crazy</title>
    <dc:date>2019-01-10T20:47:40+00:00</dc:date>
    <link>https://ronjeffries.com/articles/018-01ff/no-estimates-logic/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[We always could stop estimating, but it’s not always the right thing to do. It’s always legitimate to think about it.]]></description>
<dc:subject>software estimation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:5585c65cad35/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:estimation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pragprog.com/magazines/2013-02/estimation-is-evil">
    <title>PragPub February 2013 | Estimation is Evil | The Pragmatic Bookshelf</title>
    <dc:date>2019-01-10T20:41:52+00:00</dc:date>
    <link>https://pragprog.com/magazines/2013-02/estimation-is-evil</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[To no one’s surprise, having been overloaded, the team falls short. Nonetheless, management tells the team that they need to improve their estimates. What management really means is that estimates are promises—even forced estimates—and the team needs to keep their “promises,” even if they never promised. The team accomplishes all that it can accomplish. Then management tries to force the team to do more than they can do, demanding that the team “become more productive,” which means “go faster, promise more, and get it done.”]]></description>
<dc:subject>software estimation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:029e949f4915/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:estimation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.fridayfwd.com/missing-out/##subForm2">
    <title>Jason Fried &amp; the Joy of Missing Out | Friday Forward (#155)</title>
    <dc:date>2018-12-21T21:21:37+00:00</dc:date>
    <link>https://www.fridayfwd.com/missing-out/##subForm2</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Jason Fried does not live within a FOMO mindset. In fact, in his upcoming book, he coins the term “Jomo” The Joy of Missing Out.

Jason doesn’t pay much attention to what anyone else is doing or thinking. He reads the paper once a day. He has no long-term goals for himself or his business. Everything at Basecamp is designed in six week sprints; if something can’t get done in six weeks, they don’t build it.

Jason and his team focus intently on what they are doing now, discovering what is most important to their customer and doing the best job they can to deliver that.]]></description>
<dc:subject>software business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:758a06974a99/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://devdb.io/devdb">
    <title>Jane's CV | DevDB</title>
    <dc:date>2018-12-19T15:09:01+00:00</dc:date>
    <link>https://devdb.io/devdb</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>software cv</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:0beecaa63765/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cv"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.michaelnygard.com/blog/2015/07/the-fear-cycle/">
    <title>The Fear Cycle - Wide Awake Developers</title>
    <dc:date>2018-12-17T03:27:25+00:00</dc:date>
    <link>https://www.michaelnygard.com/blog/2015/07/the-fear-cycle/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Add a few of these events into the company lore and you'll find that developers and project managers become loath to touch anything outside their narrow scope. They seek local safety.

The trouble with local safety is that it requires kludges. The code base will inevitably deteriorate as pressure for larger changes and broader refactoring builds without release.]]></description>
<dc:subject>software complexity devops management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:d33e731fd75a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.intercom.com/blog/prioritizing-product-announcements-saas-world/">
    <title>Prioritizing product announcements in a SaaS world | Inside Intercom</title>
    <dc:date>2018-12-07T03:17:41+00:00</dc:date>
    <link>https://www.intercom.com/blog/prioritizing-product-announcements-saas-world/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Mapping prioritization to tactics
Understanding the priority of an announcement will help you understand what level of effort and investment you should make in announcing it. For us, we map each priority to a set of tactics.]]></description>
<dc:subject>saas marketing software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:d275de9f7cec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:saas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:marketing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.maschall.com/development/2018/11/05/remote-vs-distributed.html">
    <title>Remote vs Distributed — » Mark Schall</title>
    <dc:date>2018-11-09T20:56:25+00:00</dc:date>
    <link>http://www.maschall.com/development/2018/11/05/remote-vs-distributed.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>remote distributed teams work software business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:22b7445eeb86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:remote"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.joelonsoftware.com/2000/03/29/painless-software-schedules/">
    <title>Painless Software Schedules – Joel on Software</title>
    <dc:date>2018-11-01T04:35:02+00:00</dc:date>
    <link>https://www.joelonsoftware.com/2000/03/29/painless-software-schedules/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[As a rule of thumb, each task should be from 2 to 16 hours. If you have a 40 hour (one week) task on your schedule, you’re not breaking it down enough.

Here’s another reason to pick fine grained tasks: it forces you to design the damn feature. If you have a hand-wavy feature called “Internet Integration” and you schedule 3 weeks for it, you are doomed, buddy. If you have to figure out what subroutines you’re going to write, you are forced to pin down the feature. By being forced to plan ahead at this level, you eliminate a lot of the instability in a software project.]]></description>
<dc:subject>planning projects software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:488152d89025/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:projects"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.priceintelligently.com/hubfs/Price-Intelligently-SaaS-Pricing-Strategy.pdf">
    <title>Price-Intelligently-SaaS-Pricing-Strategy.pdf</title>
    <dc:date>2018-10-06T02:30:18+00:00</dc:date>
    <link>http://www.priceintelligently.com/hubfs/Price-Intelligently-SaaS-Pricing-Strategy.pdf</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>saas pricing business software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:02566b412a2f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:saas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:pricing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.brightball.com/articles/reality-driven-development-fixing-project-management-in-software">
    <title>Reality Driven Development: Fixing Project Management in Software | Brightball, Inc</title>
    <dc:date>2018-05-31T13:04:48+00:00</dc:date>
    <link>http://www.brightball.com/articles/reality-driven-development-fixing-project-management-in-software</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>software agile kanban management scrum</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:07de60f80268/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:kanban"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:scrum"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://10words.io/">
    <title>10words - Discover new startups in 10 words or less</title>
    <dc:date>2018-04-12T03:06:16+00:00</dc:date>
    <link>https://10words.io/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>business startups software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:35daa1981625/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:startups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@timferriss/how-to-create-a-million-dollar-business-this-weekend-examples-appsumo-mint-chihuahuas-fae4dab10842">
    <title>How to Create a Million-Dollar Business This Weekend (Examples: AppSumo, Mint, Chihuahuas)</title>
    <dc:date>2018-04-09T19:21:48+00:00</dc:date>
    <link>https://medium.com/@timferriss/how-to-create-a-million-dollar-business-this-weekend-examples-appsumo-mint-chihuahuas-fae4dab10842</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>business software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:13133099386f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.protopie.io/">
    <title>ProtoPie - Prototype mobile interactions as easily as Pie</title>
    <dc:date>2017-12-31T20:30:25+00:00</dc:date>
    <link>https://www.protopie.io/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>design software tools prototype prototyping</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:e35243ac758a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:prototype"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:prototyping"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.littlepotatosoftware.com/alphababy_mac.html">
    <title>AlphaBaby (MacOS) | Little Potato Software</title>
    <dc:date>2017-12-21T02:49:18+00:00</dc:date>
    <link>http://www.littlepotatosoftware.com/alphababy_mac.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>baby software business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:aebdb312a3f2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:baby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.product-frameworks.com/">
    <title>Product Frameworks - The Ultimate Guide to product development frameworks and best practices for building products.</title>
    <dc:date>2017-12-04T19:00:15+00:00</dc:date>
    <link>http://www.product-frameworks.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>product frameworks software business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:76f61cbd484b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:product"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:frameworks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Versioning_file_system#ITS">
    <title>Versioning file system - Wikipedia</title>
    <dc:date>2017-11-10T21:28:35+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Versioning_file_system#ITS</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>software computing history versioning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:566b811e9b1d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:computing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:versioning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.onepagecrm.com/pricing">
    <title>Simple Pricing - OnePageCRMOnePageCRM</title>
    <dc:date>2017-11-07T01:18:48+00:00</dc:date>
    <link>https://www.onepagecrm.com/pricing</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>crm software business pricing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:1348bdfa9aec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:crm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:pricing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://boz.com/articles/ownership-and-entitlement.html">
    <title>Ownership and Entitlement</title>
    <dc:date>2017-07-31T17:36:27+00:00</dc:date>
    <link>http://boz.com/articles/ownership-and-entitlement.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Contrary to popular belief, entitlement is fundamentally the mentality of the victim. The entitled mind is convinced it is inescapably subject to malevolent or negligent forces outside of its control and nurtures a grudge against the perceived injustice. Entitlement represents a fixed mindset where people and power structures can’t be changed which provides an excuse to complain without taking any meaningful action. As a consequence, interactions are treated as transactional and zero-sum so solutions are measured in the short term from employment agreements to APIs.

Entitled people believe that a great deal is owed to them. If you were to believe that, then you would spend your time:
* comparing yourself to others and looking for opportunities to make yourself relatively superior
* hiring as few good people to compete with you as possible
* avoiding direct conversations where there is any personal risk
* waiting for others to point out problems and then join the bandwagon when there are enough people that it feels safe
* passing responsibility and ownership to others to solve problems
* avoiding risks and focusing on safe work even if it isn’t the highest impact
* negotiating for personal gain rather than collective gain
* downplaying or hiding mistakes and overhyping successes
* leaving problems you discover for someone else to fix]]></description>
<dc:subject>psychology startups software business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:1f9a730d9e38/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:psychology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:startups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://michaelfeathers.silvrback.com/converting-queries-to-commands?__s=wy767durrhvpwkebafhz">
    <title>Michael Feathers - Converting Queries to Commands</title>
    <dc:date>2017-07-31T16:04:29+00:00</dc:date>
    <link>https://michaelfeathers.silvrback.com/converting-queries-to-commands?__s=wy767durrhvpwkebafhz</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[OO’s primary advantage is decoupling. We send messages to objects and it is up to them to decide what to do. This view of OO comes from Alan Kay and it takes quite a while to internalize. One of the things you have to accept is that when you tell an object to do something there’s no guarantee that it will actually do it. You could, for instance, tell a graphical widget to move but it may not. It could be a null object that simply receives messages and does nothing. These objects can be very useful in systems but you have to maintain the mental frame: what is done depends upon the object. The method calls we make communicate intent but the object bears the responsibility.]]></description>
<dc:subject>oop programming software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:d7541022d085/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:oop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=14209168">
    <title>Ask HN: Best practices for log format? | Hacker News</title>
    <dc:date>2017-04-27T13:48:30+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=14209168</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>logging software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:8aaa55ca00bf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:logging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@sitapati/the-impact-github-is-having-on-your-software-career-right-now-6ce536ec0b50">
    <title>The Impact GitHub is Having on Your Software Career, Right Now…</title>
    <dc:date>2017-04-04T13:39:13+00:00</dc:date>
    <link>https://medium.com/@sitapati/the-impact-github-is-having-on-your-software-career-right-now-6ce536ec0b50</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[For those of us who spent the past decade making a billion dollar open source software company however, there is nothing free or spare time about working in the open. And the benefits and consequences of working in the open are clear: your reputation is yours and is portable between companies. GitHub is a social network where your social capital, created by your commits and contribution to the global conversation in whatever technology you are working, is yours — not tied to the company you happen to be working at temporarily.]]></description>
<dc:subject>opensource career hiring software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:445155d36991/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:hiring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ascii.textfiles.com/archives/5153?__s=wy767durrhvpwkebafhz">
    <title>Thoughts on a Collection: Apple II Floppies in the Realm of the Now « ASCII by Jason Scott</title>
    <dc:date>2017-03-26T20:03:34+00:00</dc:date>
    <link>http://ascii.textfiles.com/archives/5153?__s=wy767durrhvpwkebafhz</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[I was connected with The 3D0G Knight, a long-retired Apple II pirate/collector who had built up a set of hundreds of floppy disks acquired from many different locations and friends decades ago. He generously sent me his entire collection to ingest into a more modern digital format, as well as the Internet Archive’s software archive.]]></description>
<dc:subject>computer software history apple</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:9b6e5a6ee501/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:computer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:apple"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cio.co.nz/article/466635/amazon_cto_stop_spending_money_undifferentiated_heavy_lifting_/">
    <title>Amazon CTO: Stop spending money on 'undifferentiated heavy lifting' - CIO New Zealand</title>
    <dc:date>2017-03-22T00:16:27+00:00</dc:date>
    <link>http://www.cio.co.nz/article/466635/amazon_cto_stop_spending_money_undifferentiated_heavy_lifting_/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[ “We thrive on feedback how to build better services.”He says enterprises should “stop spending money on undifferentiated heavy lifting.”]]></description>
<dc:subject>software business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:9add9f94d20d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://uxdesign.cc/the-best-youtube-channels-for-designers-and-developers-eda97b38d46a#.dj4q41q1x">
    <title>The best YouTube channels for designers and developers</title>
    <dc:date>2017-03-10T14:50:47+00:00</dc:date>
    <link>https://uxdesign.cc/the-best-youtube-channels-for-designers-and-developers-eda97b38d46a#.dj4q41q1x</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:5b3530feabbe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://programmingisterrible.com/post/139222674273/write-code-that-is-easy-to-delete-not-easy-to">
    <title>Write code that is easy to delete, not easy to... — programming is terrible</title>
    <dc:date>2017-02-14T18:16:19+00:00</dc:date>
    <link>http://programmingisterrible.com/post/139222674273/write-code-that-is-easy-to-delete-not-easy-to</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Write code that is easy to delete, not easy to extend.

“Every line of code is written without reason, maintained out of weakness, and deleted by chance” Jean-Paul Sartre’s Programming in ANSI C.

Every line of code written comes at a price: maintenance. To avoid paying for a lot of code, we build reusable software. The problem with code re-use is that it gets in the way of changing your mind later on.]]></description>
<dc:subject>software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:756dc3a602f5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.sidefx.com/">
    <title>Home | SideFX</title>
    <dc:date>2017-02-01T03:56:19+00:00</dc:date>
    <link>https://www.sidefx.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>software 3d animation consumption graphics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:ccd6f49eb946/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:3d"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:animation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:consumption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:graphics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.indiehackers.com/businesses/fundraising-report-card">
    <title>Fundraising Report Card - Indie Hackers</title>
    <dc:date>2017-01-29T22:38:23+00:00</dc:date>
    <link>https://www.indiehackers.com/businesses/fundraising-report-card</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>nonprofit software analytics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:d0968b88a4e8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:nonprofit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:analytics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://c2.com/doc/everything.html">
    <title>EverythingAboutObjects</title>
    <dc:date>2017-01-25T02:09:20+00:00</dc:date>
    <link>http://c2.com/doc/everything.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[What are these things that we must do to make designing (and skiing) a thrilling and natural activity?

Look Three Bumps Ahead
Use Your Edges
Have No Fear]]></description>
<dc:subject>software programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:9372f4cbc435/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://m.signalvnoise.com/a-rant-against-maximization-b5091d75abda#.pul3bjos8">
    <title>A Rant Against Maximization</title>
    <dc:date>2017-01-19T20:09:49+00:00</dc:date>
    <link>https://m.signalvnoise.com/a-rant-against-maximization-b5091d75abda#.pul3bjos8</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[I get how it works. I just don’t care. I’m not interested in squeezing something so tight that I get every last drop. I don’t want, need, or care about every last drop. Those last drops usually don’t taste as good anyway.]]></description>
<dc:subject>business software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:cfe027a9905c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.hypergolix.com/">
    <title>Hypergolix - programmable cloud sync</title>
    <dc:date>2017-01-16T16:05:27+00:00</dc:date>
    <link>https://www.hypergolix.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>collaboration sync python software cloud</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:7e628698d7ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:sync"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cloud"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hackernoon.com/why-microsoft-teams-flopped-and-what-it-means-for-slack-cb2bbfa53963#.bjepptaap">
    <title>Why Microsoft Teams Flopped And What It Means For Slack.</title>
    <dc:date>2017-01-09T17:30:40+00:00</dc:date>
    <link>https://hackernoon.com/why-microsoft-teams-flopped-and-what-it-means-for-slack-cb2bbfa53963#.bjepptaap</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Let me repeat my old mantra — for a company NOT TO DIE is more important than to grow fast. Perhaps it’s the microbiologist inside me talking. Once you learn biology, your worldview changes.]]></description>
<dc:subject>startups software business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:383ded38802a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:startups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:business"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>