3 years ago · 0ad02cc1b2
--- a/cache/2021/13fac7e78342ffd7e5286a6d5519e19e/index.html
+++ b/cache/2021/13fac7e78342ffd7e5286a6d5519e19e/index.html
--- a/cache/2021/13fac7e78342ffd7e5286a6d5519e19e/index.md
+++ b/cache/2021/13fac7e78342ffd7e5286a6d5519e19e/index.md
--- a/cache/2021/75dddb3b875088c9e1908a83687e7725/index.html
+++ b/cache/2021/75dddb3b875088c9e1908a83687e7725/index.html
@@ -0,0 +1,219 @@
 <!doctype html><!-- This is a valid HTML5 document. -->
 <!-- Screen readers, SEO, extensions and so on. -->
 <html lang="fr">
 <!-- Has to be within the first 1024 bytes, hence before the <title>
  See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
 <meta charset="utf-8">
 <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
 <!-- The viewport meta is quite crowded and we are responsible for that.
  See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
 <meta name="viewport" content="width=device-width,initial-scale=1">
 <!-- Required to make a valid HTML5 document. -->
 <title>Four fours - Sentiers Media (archive) — David Larlet</title>
 <meta name="description" content="Publication mise en cache pour en conserver une trace.">
 <!-- That good ol' feed, subscribe :). -->
 <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
 <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
 <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
 <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
 <link rel="manifest" href="/static/david/icons2/site.webmanifest">
 <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
 <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
 <meta name="msapplication-TileColor" content="#f0f0ea">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f0f0ea">
 <!-- Documented, feel free to shoot an email. -->
 <link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
 <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <script>
    function toggleTheme(themeName) {
        document.documentElement.classList.toggle(
            'forced-dark',
            themeName === 'dark'
        )
        document.documentElement.classList.toggle(
            'forced-light',
            themeName === 'light'
        )
    }
    const selectedTheme = localStorage.getItem('theme')
    if (selectedTheme !== 'undefined') {
        toggleTheme(selectedTheme)
    }
 </script>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://sentiers.media/four-fours/">

 <body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick">

 <article>
  <header>
    <h1>Four fours - Sentiers Media</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://sentiers.media/four-fours/" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p class="has-large-font-size">How do you work? I think productivity gets somewhat of a bad rap, some people talk and write about it nonstop, for some it’s a way to optimize their workaholic tendencies, and sometimes it leads to too much focus on details, not enough on what you are actually trying to get done. On the other hand, I think it <i>is</i> useful to see how others work, and to try to have and evolve your own system, not simply diving in heads down in the morning and hoping for the best.</p>

 <p>In the spirit of “this might be useful to someone else” but also, more so, with the goal of putting some low level peer-pressure on myself, I thought I’d share how I’m trying to structure 2021. Because I like alliterations and repeating things, but also simply because of our calendar, I call it the Four fours. Or 4x4x4x4.</p>

 <ul><li>Four solid hours of knowledge work a day.
 </li><li>Four work days a week.
 </li><li>Four things delivered each week.
 </li><li>Four projects a year.
 </li></ul>

 <h2 id="Four solid hours of knowledge work a day">Four solid hours of knowledge work a day</h2>

 <p>This one is 100% lifted from Doug Belshaw. I’ve <a href="https://i.never.nu/four-hours-of-knowledge-work/">written about it before</a> and it’s really <a href="https://dougbelshaw.com/blog/2017/03/17/my-daily-routine/">Doug’s routine</a> and his mention of it that got me to think this way.</p>

 <blockquote class="wp-block-quote"><p>My time is precious.   of solid knowledge work is what I aim for each day <a href="http://thinksimplenow.com/productivity/the-4-hour-workday/">Four hours</a> as <a href="http://www.economist.com/blogs/freeexchange/2013/09/working-hours">research</a> backs up my theory that this is optimal. I feel sorry for people who work in offices who have long commutes each way, have to spend time maintaining relationships with colleagues they don’t particularly like, and in meetings that are a waste of time.</p></blockquote>

 <p>There are a couple of links in the quote above, and I could find a few more through the research I was doing back in the day when I was writing a newsletter on lifelong learning. Four hours of focused work is roughly the most we can expect, and dozens of great creators had this type of schedule.</p>

 <p>Like Doug, I don’t just work four hours; admin, emails, and meetings are not counted in there. But, especially in pandemic times with the kid at home more, if I manage four good hours of focused work, I consider it a good day. One hour, a quick break, another hour. Morning and afternoon, the rest falls around those hours. It’s a case of managing expectations. If only for morale reasons, it’s good to have a reasonable idea of what you can get done in a day and not expect too much of yourself in a tense time.</p>

 <h2 id="Four work days a week">Four work days a week</h2>

 <p>On this one I’m blatantly cheating. I do work five days a week but Friday is for writing <i>Sentiers</i>, which is not work per se. On that day I don’t book meetings or plan on anything else than catching up on readings, curating what goes in, and writing the insights/summaries. I’m doing all the same things as when I’m working but it’s for my own thing, written for readers but also for myself.</p>

 <h2 id="Four things delivered each week">Four things delivered each week</h2>

 <p>This is the new one and why I came up with this post. In his <a href="https://twitter.com/lennysan/status/1347642516481351680">excellent thread on writing a newsletter</a>, Lenny Rachitsky said this: “Just sending an email to a few friends regularly with your concrete goals about writing (and anything else) works wonders.” (Example below.)</p>

 <figure class="wp-block-image alignwide size-large"><img src="https://pbs.twimg.com/media/ErPAnzOVoAEPfvT?format=jpg&amp;name=large" alt data-lazy-src="https://pbs.twimg.com/media/ErPAnzOVoAEPfvT?format=jpg&amp;name=large&amp;is-pending-load=1" srcset="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class=" jetpack-lazy-image"><noscript><img src="https://pbs.twimg.com/media/ErPAnzOVoAEPfvT?format=jpg&amp;name=large" alt=""></noscript><figcaption>Lenny’s example, lifted from his thread.</figcaption></figure>

 <p>I thought about it a bit, but I couldn’t really think of enough friends who would be interested in getting this <i>and</i> pay attention to have a critical mass of some of them replying or inquiring. And thus, no pressure yet “bugging” people with it anyway. Also, I’m already achieving roughly that level of things, I wanted pressure for more smaller things and the flexibility of changing things up, as long as I complete them.</p>

 <p>And so, I thought I’d start writing weeknotes. A <a href="https://medium.com/job-garden/a-pre-history-of-weeknotes-plus-why-i-write-them-and-perhaps-why-you-should-too-week-16-31a4a5cbf7b0">well established practice</a> a lot of people have been doing these for years. I plan on a simple version, a list of things delivered that week, potentially some more thoughts, and usually one “practice related” article read during the week.</p>

 <p>By “things delivered” I’m just thinking of almost any kind of work completed. For example, this week:</p>

 <ol><li>Researched and wrote-up two posts for DA VINCI. (Yeah! Finally using project names!)
 </li><li>Wrote up two posts for the <i>Sentiers</i> website (this one and another scheduled to publish).
 </li><li>Wrapped up the archive conversion for ECO.
 </li><li>Completed and posted the report for CRICHTON.
 </li></ol>

 <p>I’m setting this up for two mental tricks on myself; the routine of writing these, and the (almost) entirely imagined peer-pressure of posting them in public.</p>

 <h2 id="Four projects a year">Four projects a year</h2>

 <p>This one I’ve already shared in <a href="https://sentiers.media/on-projects/">On projects, newsletters, products, and formats</a>.  At this point, three projects of four months each might have been a better idea, but allowing for relatively blurry lines between each, I’m still hopeful to manage to ship four larger things a year. The first, ECO, was supposed to be over the last quarter of 2020 but is ongoing. I’m lining up a smaller project and might get both done before March 31st (😳). Although if the BABBAGE client project gets off the ground, maybe not.</p>

 <h2 id="Two hundred fifty-six">Two hundred fifty-six</h2>

 <p>Hopefully this can somehow be useful to others, and hopefully writing it and putting it out there, along with the weeknotes, helps me stick to the schedule and complete things with more regularity.</p>
 </article>


 <hr>

 <footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
      </svg> Accueil</a> •
    <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-rss2"></use>
      </svg> RSS</a> •
    <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-user-tie"></use>
      </svg> Pro</a> •
    <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-mail"></use>
      </svg> Email</a> •
    <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-hammer2"></use>
      </svg> Légal</abbr>
  </p>
  <template id="theme-selector">
      <form>
          <fieldset>
              <legend><svg class="icon icon-brightness-contrast">
                <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-brightness-contrast"></use>
              </svg> Thème</legend>
              <label>
                  <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
              </label>
              <label>
                  <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
              </label>
              <label>
                  <input type="radio" value="light" name="chosen-color-scheme"> Clair
              </label>
          </fieldset>
      </form>
  </template>
 </footer>
 <script>
    function loadThemeForm(templateName) {
        const themeSelectorTemplate = document.querySelector(templateName)
        const form = themeSelectorTemplate.content.firstElementChild
        themeSelectorTemplate.replaceWith(form)

        form.addEventListener('change', (e) => {
            const chosenColorScheme = e.target.value
            localStorage.setItem('theme', chosenColorScheme)
            toggleTheme(chosenColorScheme)
        })

        const selectedTheme = localStorage.getItem('theme')
        if (selectedTheme && selectedTheme !== 'undefined') {
            form.querySelector(`[value="${selectedTheme}"]`).checked = true
        }
    }

    const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
    window.addEventListener('load', () => {
        let hasDarkRules = false
        for (const styleSheet of Array.from(document.styleSheets)) {
            let mediaRules = []
            for (const cssRule of styleSheet.cssRules) {
                if (cssRule.type !== CSSRule.MEDIA_RULE) {
                    continue
                }
                // WARNING: Safari does not have/supports `conditionText`.
                if (cssRule.conditionText) {
                    if (cssRule.conditionText !== prefersColorSchemeDark) {
                        continue
                    }
                } else {
                    if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
                        continue
                    }
                }
                mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
            }

            // WARNING: do not try to insert a Rule to a styleSheet you are
            // currently iterating on, otherwise the browser will be stuck
            // in a infinite loop…
            for (const mediaRule of mediaRules) {
                styleSheet.insertRule(mediaRule.cssText)
                hasDarkRules = true
            }
        }
        if (hasDarkRules) {
            loadThemeForm('#theme-selector')
        }
    })
 </script>
 </body>
 </html>
--- a/cache/2021/75dddb3b875088c9e1908a83687e7725/index.md
+++ b/cache/2021/75dddb3b875088c9e1908a83687e7725/index.md
@@ -0,0 +1,97 @@
 title: Four fours - Sentiers Media
 url: https://sentiers.media/four-fours/
 hash_url: 75dddb3b875088c9e1908a83687e7725

 <p class="has-large-font-size">How do you work? I think productivity gets somewhat of a bad rap, some people talk and write about it nonstop, for some it’s a way to optimize their workaholic tendencies, and sometimes it leads to too much focus on details, not enough on what you are actually trying to get done. On the other hand, I think it <i>is</i> useful to see how others work, and to try to have and evolve your own system, not simply diving in heads down in the morning and hoping for the best.</p>



 <p>In the spirit of “this might be useful to someone else” but also, more so, with the goal of putting some low level peer-pressure on myself, I thought I’d share how I’m trying to structure 2021. Because I like alliterations and repeating things, but also simply because of our calendar, I call it the Four fours. Or 4x4x4x4.</p>



 <ul><li>Four solid hours of knowledge work a day.
 </li><li>Four work days a week.
 </li><li>Four things delivered each week.
 </li><li>Four projects a year.
 </li></ul>



 <h2 id="Four solid hours of knowledge work a day">Four solid hours of knowledge work a day</h2>



 <p>This one is 100% lifted from Doug Belshaw. I’ve <a href="https://i.never.nu/four-hours-of-knowledge-work/">written about it before</a> and it’s really <a href="https://dougbelshaw.com/blog/2017/03/17/my-daily-routine/">Doug’s routine</a> and his mention of it that got me to think this way.</p>



 <blockquote class="wp-block-quote"><p>My time is precious.   of solid knowledge work is what I aim for each day <a href="http://thinksimplenow.com/productivity/the-4-hour-workday/">Four hours</a> as <a href="http://www.economist.com/blogs/freeexchange/2013/09/working-hours">research</a> backs up my theory that this is optimal. I feel sorry for people who work in offices who have long commutes each way, have to spend time maintaining relationships with colleagues they don’t particularly like, and in meetings that are a waste of time.</p></blockquote>



 <p>There are a couple of links in the quote above, and I could find a few more through the research I was doing back in the day when I was writing a newsletter on lifelong learning. Four hours of focused work is roughly the most we can expect, and dozens of great creators had this type of schedule.</p>



 <p>Like Doug, I don’t just work four hours; admin, emails, and meetings are not counted in there. But, especially in pandemic times with the kid at home more, if I manage four good hours of focused work, I consider it a good day. One hour, a quick break, another hour. Morning and afternoon, the rest falls around those hours. It’s a case of managing expectations. If only for morale reasons, it’s good to have a reasonable idea of what you can get done in a day and not expect too much of yourself in a tense time.</p>



 <h2 id="Four work days a week">Four work days a week</h2>



 <p>On this one I’m blatantly cheating. I do work five days a week but Friday is for writing <i>Sentiers</i>, which is not work per se. On that day I don’t book meetings or plan on anything else than catching up on readings, curating what goes in, and writing the insights/summaries. I’m doing all the same things as when I’m working but it’s for my own thing, written for readers but also for myself.</p>



 <h2 id="Four things delivered each week">Four things delivered each week</h2>



 <p>This is the new one and why I came up with this post. In his <a href="https://twitter.com/lennysan/status/1347642516481351680">excellent thread on writing a newsletter</a>, Lenny Rachitsky said this: “Just sending an email to a few friends regularly with your concrete goals about writing (and anything else) works wonders.” (Example below.)</p>



 <figure class="wp-block-image alignwide size-large"><img src="https://pbs.twimg.com/media/ErPAnzOVoAEPfvT?format=jpg&amp;name=large" alt data-lazy-src="https://pbs.twimg.com/media/ErPAnzOVoAEPfvT?format=jpg&amp;name=large&amp;is-pending-load=1" srcset="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class=" jetpack-lazy-image"><noscript><img src="https://pbs.twimg.com/media/ErPAnzOVoAEPfvT?format=jpg&amp;name=large" alt=""></noscript><figcaption>Lenny’s example, lifted from his thread.</figcaption></figure>



 <p>I thought about it a bit, but I couldn’t really think of enough friends who would be interested in getting this <i>and</i> pay attention to have a critical mass of some of them replying or inquiring. And thus, no pressure yet “bugging” people with it anyway. Also, I’m already achieving roughly that level of things, I wanted pressure for more smaller things and the flexibility of changing things up, as long as I complete them.</p>



 <p>And so, I thought I’d start writing weeknotes. A <a href="https://medium.com/job-garden/a-pre-history-of-weeknotes-plus-why-i-write-them-and-perhaps-why-you-should-too-week-16-31a4a5cbf7b0">well established practice</a> a lot of people have been doing these for years. I plan on a simple version, a list of things delivered that week, potentially some more thoughts, and usually one “practice related” article read during the week.</p>



 <p>By “things delivered” I’m just thinking of almost any kind of work completed. For example, this week:</p>



 <ol><li>Researched and wrote-up two posts for DA VINCI. (Yeah! Finally using project names!)
 </li><li>Wrote up two posts for the <i>Sentiers</i> website (this one and another scheduled to publish).
 </li><li>Wrapped up the archive conversion for ECO.
 </li><li>Completed and posted the report for CRICHTON.
 </li></ol>



 <p>I’m setting this up for two mental tricks on myself; the routine of writing these, and the (almost) entirely imagined peer-pressure of posting them in public.</p>



 <h2 id="Four projects a year">Four projects a year</h2>



 <p>This one I’ve already shared in <a href="https://sentiers.media/on-projects/">On projects, newsletters, products, and formats</a>.  At this point, three projects of four months each might have been a better idea, but allowing for relatively blurry lines between each, I’m still hopeful to manage to ship four larger things a year. The first, ECO, was supposed to be over the last quarter of 2020 but is ongoing. I’m lining up a smaller project and might get both done before March 31st (😳). Although if the BABBAGE client project gets off the ground, maybe not.</p>



 <h2 id="Two hundred fifty-six">Two hundred fifty-six</h2>



 <p>Hopefully this can somehow be useful to others, and hopefully writing it and putting it out there, along with the weeknotes, helps me stick to the schedule and complete things with more regularity.</p>
--- a/cache/2021/b7829aa5073173cca4ed3f4ea23e767f/index.html
+++ b/cache/2021/b7829aa5073173cca4ed3f4ea23e767f/index.html
@@ -0,0 +1,210 @@
 <!doctype html><!-- This is a valid HTML5 document. -->
 <!-- Screen readers, SEO, extensions and so on. -->
 <html lang="fr">
 <!-- Has to be within the first 1024 bytes, hence before the <title>
  See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
 <meta charset="utf-8">
 <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
 <!-- The viewport meta is quite crowded and we are responsible for that.
  See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
 <meta name="viewport" content="width=device-width,initial-scale=1">
 <!-- Required to make a valid HTML5 document. -->
 <title>Développeur de logiciel senior / principal(e) (Python) (archive) — David Larlet</title>
 <meta name="description" content="Publication mise en cache pour en conserver une trace.">
 <!-- That good ol' feed, subscribe :). -->
 <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
 <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
 <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
 <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
 <link rel="manifest" href="/static/david/icons2/site.webmanifest">
 <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
 <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
 <meta name="msapplication-TileColor" content="#f0f0ea">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f0f0ea">
 <!-- Documented, feel free to shoot an email. -->
 <link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
 <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <script>
    function toggleTheme(themeName) {
        document.documentElement.classList.toggle(
            'forced-dark',
            themeName === 'dark'
        )
        document.documentElement.classList.toggle(
            'forced-light',
            themeName === 'light'
        )
    }
    const selectedTheme = localStorage.getItem('theme')
    if (selectedTheme !== 'undefined') {
        toggleTheme(selectedTheme)
    }
 </script>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://numerique.canada.ca/join-our-team/positions/d%C3%A9veloppeur-de-logiciel-senior-principal-e-python/">

 <body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick">

 <article>
  <header>
    <h1>Développeur de logiciel senior / principal(e) (Python)</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://numerique.canada.ca/join-our-team/positions/d%C3%A9veloppeur-de-logiciel-senior-principal-e-python/" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <h2 class="section--title">Nous embauchons</h2>

 <pre><code>      &lt;p&gt;Le Service numérique canadien (SNC) est chargé de changer la façon dont le gouvernement fédéral conçoit et fournit les services numériques, afin de réduire les risques d’échec des produits, de réduire les coûts, de garantir la confidentialité des utilisateurs et la sécurité des systèmes, et surtout, d’améliorer la vie des gens en appelant l’attention sur leurs besoins et préoccupations. Selon nous, chaque expérience vécue par les Canadiennes et Canadiens lorsqu’ils interagissent avec le gouvernement devrait répondre ou dépasser leurs attentes modernes et valables voulant que les services numériques soient sûrs, rapides, faciles, transparents et accessibles. Nous travaillons ouvertement, renforçant ainsi les capacités dans tout le gouvernement pour améliorer la prestation de services. Et nous avons besoin de vous.&lt;/p&gt;
 </code></pre>
 <p>Nous recrutons des Développeurs de logiciel principal(e) et senior. Bien que nous ayons des bureaux à Ottawa, Montréal, Toronto et Kitchener, nous travaillons en grande partie de manière distribuée et nous embauchons également des candidats dans d&rsquo;autres régions du Canada.</p>

 <p>Ces postes font partie de la Communauté de développement de logiciels et relèvent du Chef du développement de logiciels, qui affecte les employés aux projets en fonction des besoins organisationnels et des plans de croissance personnelle. </p>

 <p>Les Développeurs senior sont classés <a href="https://www.tbs-sct.gc.ca/agreements-conventions/view-visualiser-fra.aspx?id=1#toc12259212260">CS-04</a> et les Développeurs Principal(e) sont classés <a href="https://www.tbs-sct.gc.ca/agreements-conventions/view-visualiser-fra.aspx?id=1#toc12259212260">CS-05</a> dans le groupe des systèmes d’ordinateur.</p>

 <p><strong>Vous devrez accomplir les tâches suivantes :</strong></p>

 <ol>
 <li>Fournir du code Python de haute qualité qui sera publié dans le nuage et faire preuve d’une expertise et d’une volonté d’apprendre de nouveaux langages informatiques et de nouvelles technologies au besoin.</li>
 <li>Expédier des applications web complète (de l&rsquo;interface utilisateur à l&rsquo;infrastructure). Cela comprend l&rsquo;architecture, le codage, l&rsquo;exploitation, la mise en service, les tests et les réglages. Vous devrez les réaliser de manière ouverte et en collaboration avec des équipes interfonctionnelles. Cela peut impliquer une rotation des services sur appel.</li>
 <li>Créer et défendre des pratiques par défaut au sein du SNC afin d&rsquo;accroître notre capacité à exploiter et à fournir de la valeur sur nos produits de la Plateforme. Tout ne sera pas réutilisable avec nos ministères partenaires, mais ceux-ci devraient démontrer les bonnes pratiques qu&rsquo;ils pourraient suivre.</li>
 <li>Déterminer, communiquer et fournir de manière itérative des fonctionnalités et des processus qui amélioreront les choses pour les utilisateurs dès maintenant. Il est essentiel de faire preuve d&rsquo;agilité, même si le gouvernement est dirigé par une approche en cascade.</li>
 <li>Écouter, apprendre et aider les autres employés du gouvernement et des ministères à améliorer leur façon de travailler et de fournir des services publics. En vous basant sur ce qui est à la fois faisable et efficace, vous devez aider à la gestion du changement, à la fiabilité du site, à la sécurisation des systèmes et des processus et à la conception centrée sur les usagers dans les endroits où nous n&rsquo;avons pas d&rsquo;autorité officielle.</li>
 <li>Construire des prototypes et/ou des logiciels bien conçus et maintenables en fonction du contexte. </li>
 </ol>

 <p><strong>Nous vous évaluerons en fonction de :</strong></p>

 <ul>
 <li>Création et livraison de logiciels</li>
 <li>Utiliser la pratique de la fiabilité des sites et la culture du développement moderne </li>
 <li>Sécurisation des systèmes et des processus</li>
 <li>Découvrir les besoins des utilisateurs/entreprises et les obstacles opérationnels</li>
 <li>Travailler dans des environnements très variables et impliquant de multiples parties prenantes</li>
 <li>Conseiller les hauts dirigeants et les gens non techniques </li>
 <li>Promouvoir une prestation de service inclusive et maintenir l&rsquo;impact, l&rsquo;ouverture, l&rsquo;intégrité et l&rsquo;équité.</li>
 </ul>

 <p>Au SNC, nous n’acceptons pas seulement les différences, nous les célébrons. C’est avec fierté et passion que nous nous efforçons activement de rendre le SNC plus représentatif et plus inclusif de la société que nous servons. Notre capacité à fournir des services publics améliorés — des services accessibles et inclusifs — ne peut être réalisée que si nous pouvons reconnaître et exploiter l’éventail le plus diversifié de pensées, d’expériences et de compétences. Nous travaillons fort pour créer un environnement où les différentes perspectives et expériences sont valorisées. Nous nous engageons à aider les talents divers à s’épanouir.</p>

 <p>Le SNC prend en considération tous les candidats et candidates, peu importe leur race, leur origine ethnique, leur religion, leur orientation sexuelle, leur identité ou leur expression de genre, leur origine nationale, leur handicap, leur âge, leur statut d’ancien combattant, leur situation matrimoniale, leur grossesse ou leurs obligations familiales. </p>

 <p>Nous nous engageons à fournir un environnement de travail inclusif et sans obstacle, en commençant par le processus d’embauche. Si vous avez besoin de mesures d’adaptation au cours des phases du processus d’évaluation, veuillez utiliser les coordonnées ci-dessous pour demander des mesures particulières. Toutes les informations reçues concernant les mesures d’adaptation seront gardées confidentielles.</p>

 <p><a href="https://www.canada.ca/fr/commission-fonction-publique/services/mesures-d-adaptation-matiere-evaluation.html">Mesures d’adaptation en matière d’évaluation</a></p>

 <p>Par prudence, toutes les entrevues seront menées par vidéo ou téléconférence pour un futur proche.</p>
 </article>


 <hr>

 <footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
      </svg> Accueil</a> •
    <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-rss2"></use>
      </svg> RSS</a> •
    <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-user-tie"></use>
      </svg> Pro</a> •
    <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-mail"></use>
      </svg> Email</a> •
    <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-hammer2"></use>
      </svg> Légal</abbr>
  </p>
  <template id="theme-selector">
      <form>
          <fieldset>
              <legend><svg class="icon icon-brightness-contrast">
                <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-brightness-contrast"></use>
              </svg> Thème</legend>
              <label>
                  <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
              </label>
              <label>
                  <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
              </label>
              <label>
                  <input type="radio" value="light" name="chosen-color-scheme"> Clair
              </label>
          </fieldset>
      </form>
  </template>
 </footer>
 <script>
    function loadThemeForm(templateName) {
        const themeSelectorTemplate = document.querySelector(templateName)
        const form = themeSelectorTemplate.content.firstElementChild
        themeSelectorTemplate.replaceWith(form)

        form.addEventListener('change', (e) => {
            const chosenColorScheme = e.target.value
            localStorage.setItem('theme', chosenColorScheme)
            toggleTheme(chosenColorScheme)
        })

        const selectedTheme = localStorage.getItem('theme')
        if (selectedTheme && selectedTheme !== 'undefined') {
            form.querySelector(`[value="${selectedTheme}"]`).checked = true
        }
    }

    const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
    window.addEventListener('load', () => {
        let hasDarkRules = false
        for (const styleSheet of Array.from(document.styleSheets)) {
            let mediaRules = []
            for (const cssRule of styleSheet.cssRules) {
                if (cssRule.type !== CSSRule.MEDIA_RULE) {
                    continue
                }
                // WARNING: Safari does not have/supports `conditionText`.
                if (cssRule.conditionText) {
                    if (cssRule.conditionText !== prefersColorSchemeDark) {
                        continue
                    }
                } else {
                    if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
                        continue
                    }
                }
                mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
            }

            // WARNING: do not try to insert a Rule to a styleSheet you are
            // currently iterating on, otherwise the browser will be stuck
            // in a infinite loop…
            for (const mediaRule of mediaRules) {
                styleSheet.insertRule(mediaRule.cssText)
                hasDarkRules = true
            }
        }
        if (hasDarkRules) {
            loadThemeForm('#theme-selector')
        }
    })
 </script>
 </body>
 </html>
--- a/cache/2021/b7829aa5073173cca4ed3f4ea23e767f/index.md
+++ b/cache/2021/b7829aa5073173cca4ed3f4ea23e767f/index.md
@@ -0,0 +1,45 @@
 title: Développeur de logiciel senior / principal(e) (Python)
 url: https://numerique.canada.ca/join-our-team/positions/d%C3%A9veloppeur-de-logiciel-senior-principal-e-python/
 hash_url: b7829aa5073173cca4ed3f4ea23e767f

 <h2 class="section--title">Nous embauchons</h2>
          <p>Le Service numérique canadien (SNC) est chargé de changer la façon dont le gouvernement fédéral conçoit et fournit les services numériques, afin de réduire les risques d’échec des produits, de réduire les coûts, de garantir la confidentialité des utilisateurs et la sécurité des systèmes, et surtout, d’améliorer la vie des gens en appelant l’attention sur leurs besoins et préoccupations. Selon nous, chaque expérience vécue par les Canadiennes et Canadiens lorsqu’ils interagissent avec le gouvernement devrait répondre ou dépasser leurs attentes modernes et valables voulant que les services numériques soient sûrs, rapides, faciles, transparents et accessibles. Nous travaillons ouvertement, renforçant ainsi les capacités dans tout le gouvernement pour améliorer la prestation de services. Et nous avons besoin de vous.</p>

 <p>Nous recrutons des Développeurs de logiciel principal(e) et senior. Bien que nous ayons des bureaux à Ottawa, Montréal, Toronto et Kitchener, nous travaillons en grande partie de manière distribuée et nous embauchons également des candidats dans d&rsquo;autres régions du Canada.</p>

 <p>Ces postes font partie de la Communauté de développement de logiciels et relèvent du Chef du développement de logiciels, qui affecte les employés aux projets en fonction des besoins organisationnels et des plans de croissance personnelle. </p>

 <p>Les Développeurs senior sont classés <a href="https://www.tbs-sct.gc.ca/agreements-conventions/view-visualiser-fra.aspx?id=1#toc12259212260">CS-04</a> et les Développeurs Principal(e) sont classés <a href="https://www.tbs-sct.gc.ca/agreements-conventions/view-visualiser-fra.aspx?id=1#toc12259212260">CS-05</a> dans le groupe des systèmes d’ordinateur.</p>

 <p><strong>Vous devrez accomplir les tâches suivantes :</strong></p>

 <ol>
 <li>Fournir du code Python de haute qualité qui sera publié dans le nuage et faire preuve d’une expertise et d’une volonté d’apprendre de nouveaux langages informatiques et de nouvelles technologies au besoin.</li>
 <li>Expédier des applications web complète (de l&rsquo;interface utilisateur à l&rsquo;infrastructure). Cela comprend l&rsquo;architecture, le codage, l&rsquo;exploitation, la mise en service, les tests et les réglages. Vous devrez les réaliser de manière ouverte et en collaboration avec des équipes interfonctionnelles. Cela peut impliquer une rotation des services sur appel.</li>
 <li>Créer et défendre des pratiques par défaut au sein du SNC afin d&rsquo;accroître notre capacité à exploiter et à fournir de la valeur sur nos produits de la Plateforme. Tout ne sera pas réutilisable avec nos ministères partenaires, mais ceux-ci devraient démontrer les bonnes pratiques qu&rsquo;ils pourraient suivre.</li>
 <li>Déterminer, communiquer et fournir de manière itérative des fonctionnalités et des processus qui amélioreront les choses pour les utilisateurs dès maintenant. Il est essentiel de faire preuve d&rsquo;agilité, même si le gouvernement est dirigé par une approche en cascade.</li>
 <li>Écouter, apprendre et aider les autres employés du gouvernement et des ministères à améliorer leur façon de travailler et de fournir des services publics. En vous basant sur ce qui est à la fois faisable et efficace, vous devez aider à la gestion du changement, à la fiabilité du site, à la sécurisation des systèmes et des processus et à la conception centrée sur les usagers dans les endroits où nous n&rsquo;avons pas d&rsquo;autorité officielle.</li>
 <li>Construire des prototypes et/ou des logiciels bien conçus et maintenables en fonction du contexte. </li>
 </ol>

 <p><strong>Nous vous évaluerons en fonction de :</strong></p>

 <ul>
 <li>Création et livraison de logiciels</li>
 <li>Utiliser la pratique de la fiabilité des sites et la culture du développement moderne </li>
 <li>Sécurisation des systèmes et des processus</li>
 <li>Découvrir les besoins des utilisateurs/entreprises et les obstacles opérationnels</li>
 <li>Travailler dans des environnements très variables et impliquant de multiples parties prenantes</li>
 <li>Conseiller les hauts dirigeants et les gens non techniques </li>
 <li>Promouvoir une prestation de service inclusive et maintenir l&rsquo;impact, l&rsquo;ouverture, l&rsquo;intégrité et l&rsquo;équité.</li>
 </ul>

 <p>Au SNC, nous n’acceptons pas seulement les différences, nous les célébrons. C’est avec fierté et passion que nous nous efforçons activement de rendre le SNC plus représentatif et plus inclusif de la société que nous servons. Notre capacité à fournir des services publics améliorés — des services accessibles et inclusifs — ne peut être réalisée que si nous pouvons reconnaître et exploiter l’éventail le plus diversifié de pensées, d’expériences et de compétences. Nous travaillons fort pour créer un environnement où les différentes perspectives et expériences sont valorisées. Nous nous engageons à aider les talents divers à s’épanouir.</p>

 <p>Le SNC prend en considération tous les candidats et candidates, peu importe leur race, leur origine ethnique, leur religion, leur orientation sexuelle, leur identité ou leur expression de genre, leur origine nationale, leur handicap, leur âge, leur statut d’ancien combattant, leur situation matrimoniale, leur grossesse ou leurs obligations familiales. </p>

 <p>Nous nous engageons à fournir un environnement de travail inclusif et sans obstacle, en commençant par le processus d’embauche. Si vous avez besoin de mesures d’adaptation au cours des phases du processus d’évaluation, veuillez utiliser les coordonnées ci-dessous pour demander des mesures particulières. Toutes les informations reçues concernant les mesures d’adaptation seront gardées confidentielles.</p>

 <p><a href="https://www.canada.ca/fr/commission-fonction-publique/services/mesures-d-adaptation-matiere-evaluation.html">Mesures d’adaptation en matière d’évaluation</a></p>

 <p>Par prudence, toutes les entrevues seront menées par vidéo ou téléconférence pour un futur proche.</p>
--- a/cache/2021/d685a0ad4878f3d833374164b49b3438/index.html
+++ b/cache/2021/d685a0ad4878f3d833374164b49b3438/index.html
@@ -0,0 +1,194 @@
 <!doctype html><!-- This is a valid HTML5 document. -->
 <!-- Screen readers, SEO, extensions and so on. -->
 <html lang="fr">
 <!-- Has to be within the first 1024 bytes, hence before the <title>
  See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
 <meta charset="utf-8">
 <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
 <!-- The viewport meta is quite crowded and we are responsible for that.
  See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
 <meta name="viewport" content="width=device-width,initial-scale=1">
 <!-- Required to make a valid HTML5 document. -->
 <title>Read the Principles - Design Justice Network (archive) — David Larlet</title>
 <meta name="description" content="Publication mise en cache pour en conserver une trace.">
 <!-- That good ol' feed, subscribe :). -->
 <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
 <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
 <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
 <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
 <link rel="manifest" href="/static/david/icons2/site.webmanifest">
 <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
 <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
 <meta name="msapplication-TileColor" content="#f0f0ea">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f0f0ea">
 <!-- Documented, feel free to shoot an email. -->
 <link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
 <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <script>
    function toggleTheme(themeName) {
        document.documentElement.classList.toggle(
            'forced-dark',
            themeName === 'dark'
        )
        document.documentElement.classList.toggle(
            'forced-light',
            themeName === 'light'
        )
    }
    const selectedTheme = localStorage.getItem('theme')
    if (selectedTheme !== 'undefined') {
        toggleTheme(selectedTheme)
    }
 </script>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://designjustice.org/read-the-principles">

 <body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick">

 <article>
  <header>
    <h1>Read the Principles - Design Justice Network</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://designjustice.org/read-the-principles" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p class="">This is a living document. Last update: summer 2018</p>

 <p class="">Design mediates so much of our realities and has tremendous impact on our lives, yet very few of us participate in design processes. In particular, the people who are most adversely affected by design decisions — about visual culture, new technologies, the planning of our communities, or the structure of our political and economic systems — tend to have the least influence on those decisions and how they are made.</p>

 <p class="">Design justice rethinks design processes, centers people who are normally marginalized by design, and uses collaborative, creative practices to address the deepest challenges our communities face.</p>

 <h2>Principle 1</h2>
 <p>We use design to sustain, heal, and empower our communities, as well as to seek liberation from exploitative and oppressive systems.</p>
 <h2>Principle 2</h2>
 <p>We center the voices of those who are directly impacted by the outcomes of the design process.</p>
 <h2>Principle 3</h2>
 <p>We prioritize design’s impact on the community over the intentions of the designer.</p>
 <h2>Principle 4</h2>
 <p>We view change as emergent from an accountable, accessible, and collaborative process, rather than as a point at the end of a process.*</p>
 <h2>Principle 5</h2>
 <p>We see the role of the designer as a facilitator rather than an expert.</p>
 <h2>Principle 6</h2>
 <p>We believe that everyone is an expert based on their own lived experience, and that we all have unique and brilliant contributions to bring to a design process.</p>
 <h2>Principle 7</h2>
 <p>We share design knowledge and tools with our communities.</p>
 <h2>Principle 8</h2>
 <p>We work towards sustainable, community-led and -controlled outcomes.</p>
 <h2>Principle 9</h2>
 <p>We work towards non-exploitative solutions that reconnect us to the earth and to each other.</p>
 <h2>Principle 10</h2>
 <p>Before seeking new design solutions, we look for what is already working at the community level. We honor and uplift traditional, indigenous, and local knowledge and practices.</p>
 </article>


 <hr>

 <footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
      </svg> Accueil</a> •
    <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-rss2"></use>
      </svg> RSS</a> •
    <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-user-tie"></use>
      </svg> Pro</a> •
    <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-mail"></use>
      </svg> Email</a> •
    <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-hammer2"></use>
      </svg> Légal</abbr>
  </p>
  <template id="theme-selector">
      <form>
          <fieldset>
              <legend><svg class="icon icon-brightness-contrast">
                <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-brightness-contrast"></use>
              </svg> Thème</legend>
              <label>
                  <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
              </label>
              <label>
                  <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
              </label>
              <label>
                  <input type="radio" value="light" name="chosen-color-scheme"> Clair
              </label>
          </fieldset>
      </form>
  </template>
 </footer>
 <script>
    function loadThemeForm(templateName) {
        const themeSelectorTemplate = document.querySelector(templateName)
        const form = themeSelectorTemplate.content.firstElementChild
        themeSelectorTemplate.replaceWith(form)

        form.addEventListener('change', (e) => {
            const chosenColorScheme = e.target.value
            localStorage.setItem('theme', chosenColorScheme)
            toggleTheme(chosenColorScheme)
        })

        const selectedTheme = localStorage.getItem('theme')
        if (selectedTheme && selectedTheme !== 'undefined') {
            form.querySelector(`[value="${selectedTheme}"]`).checked = true
        }
    }

    const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
    window.addEventListener('load', () => {
        let hasDarkRules = false
        for (const styleSheet of Array.from(document.styleSheets)) {
            let mediaRules = []
            for (const cssRule of styleSheet.cssRules) {
                if (cssRule.type !== CSSRule.MEDIA_RULE) {
                    continue
                }
                // WARNING: Safari does not have/supports `conditionText`.
                if (cssRule.conditionText) {
                    if (cssRule.conditionText !== prefersColorSchemeDark) {
                        continue
                    }
                } else {
                    if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
                        continue
                    }
                }
                mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
            }

            // WARNING: do not try to insert a Rule to a styleSheet you are
            // currently iterating on, otherwise the browser will be stuck
            // in a infinite loop…
            for (const mediaRule of mediaRules) {
                styleSheet.insertRule(mediaRule.cssText)
                hasDarkRules = true
            }
        }
        if (hasDarkRules) {
            loadThemeForm('#theme-selector')
        }
    })
 </script>
 </body>
 </html>
--- a/cache/2021/d685a0ad4878f3d833374164b49b3438/index.md
+++ b/cache/2021/d685a0ad4878f3d833374164b49b3438/index.md
@@ -0,0 +1,45 @@
 title: Read the Principles - Design Justice Network
 url: https://designjustice.org/read-the-principles
 hash_url: d685a0ad4878f3d833374164b49b3438

 <p class="">This is a living document. Last update: summer 2018</p><p class="">Design mediates so much of our realities and has tremendous impact on our lives, yet very few of us participate in design processes. In particular, the people who are most adversely affected by design decisions — about visual culture, new technologies, the planning of our communities, or the structure of our political and economic systems — tend to have the least influence on those decisions and how they are made.</p><p class="">Design justice rethinks design processes, centers people who are normally marginalized by design, and uses collaborative, creative practices to address the deepest challenges our communities face.</p>

 ## Principle 1

 We use design to sustain, heal, and empower our communities, as well as to seek liberation from exploitative and oppressive systems.

 ## Principle 2

 We center the voices of those who are directly impacted by the outcomes of the design process.

 ## Principle 3

 We prioritize design’s impact on the community over the intentions of the designer.

 ## Principle 4

 We view change as emergent from an accountable, accessible, and collaborative process, rather than as a point at the end of a process.*

 ## Principle 5

 We see the role of the designer as a facilitator rather than an expert.

 ## Principle 6

 We believe that everyone is an expert based on their own lived experience, and that we all have unique and brilliant contributions to bring to a design process.

 ## Principle 7

 We share design knowledge and tools with our communities.

 ## Principle 8

 We work towards sustainable, community-led and -controlled outcomes.

 ## Principle 9

 We work towards non-exploitative solutions that reconnect us to the earth and to each other.

 ## Principle 10

 Before seeking new design solutions, we look for what is already working at the community level. We honor and uplift traditional, indigenous, and local knowledge and practices.
--- a/cache/2021/eef2b3e3085a9b71cd7fe64f21fa0453/index.html
+++ b/cache/2021/eef2b3e3085a9b71cd7fe64f21fa0453/index.html
@@ -0,0 +1,214 @@
 <!doctype html><!-- This is a valid HTML5 document. -->
 <!-- Screen readers, SEO, extensions and so on. -->
 <html lang="fr">
 <!-- Has to be within the first 1024 bytes, hence before the <title>
  See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
 <meta charset="utf-8">
 <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
 <!-- The viewport meta is quite crowded and we are responsible for that.
  See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
 <meta name="viewport" content="width=device-width,initial-scale=1">
 <!-- Required to make a valid HTML5 document. -->
 <title>Anxious feelings about optimisation through complexity (archive) — David Larlet</title>
 <meta name="description" content="Publication mise en cache pour en conserver une trace.">
 <!-- That good ol' feed, subscribe :). -->
 <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
 <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
 <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
 <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
 <link rel="manifest" href="/static/david/icons2/site.webmanifest">
 <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
 <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
 <meta name="msapplication-TileColor" content="#f0f0ea">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f0f0ea">
 <!-- Documented, feel free to shoot an email. -->
 <link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
 <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <script>
    function toggleTheme(themeName) {
        document.documentElement.classList.toggle(
            'forced-dark',
            themeName === 'dark'
        )
        document.documentElement.classList.toggle(
            'forced-light',
            themeName === 'light'
        )
    }
    const selectedTheme = localStorage.getItem('theme')
    if (selectedTheme !== 'undefined') {
        toggleTheme(selectedTheme)
    }
 </script>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="http://interconnected.org/home/2021/02/12/optimisation">

 <body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick">

 <article>
  <header>
    <h1>Anxious feelings about optimisation through complexity</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="http://interconnected.org/home/2021/02/12/optimisation" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p class="measure-wide f6 f5-l lh-copy black-80">Optimisation makes me itchy.</p>

 <p class="measure-wide f6 f5-l lh-copy black-80">A couple of examples. The thermostat Google Nest has <a href="https://support.google.com/googlenest/answer/9244031">Rush Hour Rewards</a> which will <q>automatically tune temperatures before and during a Rush Hour to reduce energy use and lower grid costs</q> (a “Rush Hour” is when everyone turns their air conditioning on at the same time).</p>

 <p class="measure-wide f6 f5-l lh-copy black-80">Similar: <a href="https://carbon.coop/portfolio/power-shaper/">Power Shaper by Carbon Co-op</a> which I’m sorry to pick on because lots of UK energy companies will be doing this with smart meters, but this is the one I saw first. <em>(Thanks <a href="https://holdfastprojects.com">Rod McLaren</a> for sending it my way.)</em></p>

 <blockquote class="bl bw1 pl2 b--light-red ml0 italic i">
 <p class="measure-wide f6 f5-l lh-copy black-80">Carbon Co-op technicians will visit your home and install equipment which will enable certain existing electrical appliances (such as electric vehicle chargers, heat pumps, immersion water heaters, battery storage) to be turned on/off remotely.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">We turn things on/off only when we receive a request from grid operators and other parties.</p>
 </blockquote>

 <p class="measure-wide f6 f5-l lh-copy black-80">On the face of it, this makes a ton of sense.</p>

 <p class="measure-wide f6 f5-l lh-copy black-80">We’re shifting to renewable energy. The wind and sun have their own schedule. But say everyone gets home at 7pm and plugs in their new electric car, or turns the kettle at halftime in the football, that’s a demand spike, and that’s when a coal power station fires up, so the energy is supplied to the grid but it’s dirty energy.</p>

 <p class="measure-wide f6 f5-l lh-copy black-80">Long term this gets fixed by having neighbourhood batteries to smooth the spikes. Ahead of that, demand can be adjusted by automatically turning things off. Feedback loops.</p>

 <p class="measure-wide f6 f5-l lh-copy black-80">BUT.</p>

 <p class="measure-wide f6 f5-l lh-copy black-80">In Vernor Vinge’s space opera <a href="https://en.wikipedia.org/wiki/A_Fire_Upon_the_Deep">A Fire Upon the Deep</a> (1992) there’s a planet called <em>Namqem</em> with a high technology civilisation 4,000 years old.</p>

 <blockquote class="bl bw1 pl2 b--light-red ml0 italic i">
 <p class="measure-wide f6 f5-l lh-copy black-80">Namqem was a triumph of distributed automation. And every decade it became a little better. Every decade the flexibility of the governance responded to the pressures to optimize resource allocation, and the margins of safety shrank.</p>
 </blockquote>

 <p class="measure-wide f6 f5-l lh-copy black-80">Which is a problem. As one of the characters says: <q>They’ve accepting optimizing pressures for centuries now. … finally the optimizations have taken them to the point of fragility.</q></p>

 <blockquote class="bl bw1 pl2 b--light-red ml0 italic i">
 <p class="measure-wide f6 f5-l lh-copy black-80">‘The symptoms are classic. The last decade, the rate of system deadlocks has steadily increased throughout Namqem. See here, thirty percent of business commuting between the outer moons is in locked state at any given time.’ All the hardware was in working order, but the system complexity was so great that vehicles could not get the go-ahead.</p>
 </blockquote>

 <p class="measure-wide f6 f5-l lh-copy black-80">So eventually, as an alternative to escalating resource wars, optimisation becomes complete: every embedded computing system an instrument for total social control.</p>

 <p class="measure-wide f6 f5-l lh-copy black-80">But it doesn’t help, collapse comes, billions die, and so on.</p>

 <p><hr class="h1 xh2-ns w1 xw2-ns ml4 mv4 bb bw1 b--white">
 <p class="measure-wide f6 f5-l lh-copy black-80">I must have read Vinge at a particularly susceptible age. Because since then I see optimisation-through-complexity as a particular kind of danger.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">Not optimisation on its own. Doing something with as little energy as possible is <em>elegant.</em></p>
 <p class="measure-wide f6 f5-l lh-copy black-80">And not complexity on its own either. Complexity has its own problems: reduced legibility, the creation of priesthoods to maintain it, etc.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">But when you increase complexity in order to optimise, demand never really goes down. The optimisation becomes an opportunity to do more, and so the complexity gets locked in – there will never be the chance to remove it.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">And that compounding complexity, layers upon layers of it, a nest of interlocking feedback loops, increases the risk of fatal, emergent complexity quakes.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">All of which colours my approach to everything from how I architect my code, to how I organise my finances, to what government policies I like.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">Whenever I see something like Nest’s Rush Hour Rewards or Carbon Co-op’s Power Shaper, it makes me feel like we’re all taking one step closer to an invisible cliff edge, and the drop could be half a mile away, or it could be one inch.</p>
 <hr class="h1 xh2-ns w1 xw2-ns ml4 mv4 bb bw1 b--white">
 <p class="measure-wide f6 f5-l lh-copy black-80">I also have a high level of nervousness around magnets. I grew up with floppy disks (that would be wiped) and cathode ray tube screens (that would be permanently ruined). So magnets on wallets or toys – I’m on edge if they’re ever near electronics, and I watch them with a hawk eye until they’re at a safe distance. Magnets on laptops and iPads still seem wrong to me. Even though it’s fine now and has been for many years.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">By which I mean, don’t take my views too seriously, I’m a mess of unfounded prejudices about emergent systems and ferrous solids.</p></p>
 </article>


 <hr>

 <footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
      </svg> Accueil</a> •
    <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-rss2"></use>
      </svg> RSS</a> •
    <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-user-tie"></use>
      </svg> Pro</a> •
    <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-mail"></use>
      </svg> Email</a> •
    <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
        <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-hammer2"></use>
      </svg> Légal</abbr>
  </p>
  <template id="theme-selector">
      <form>
          <fieldset>
              <legend><svg class="icon icon-brightness-contrast">
                <use xlink:href="/static/david/icons2/symbol-defs.svg#icon-brightness-contrast"></use>
              </svg> Thème</legend>
              <label>
                  <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
              </label>
              <label>
                  <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
              </label>
              <label>
                  <input type="radio" value="light" name="chosen-color-scheme"> Clair
              </label>
          </fieldset>
      </form>
  </template>
 </footer>
 <script>
    function loadThemeForm(templateName) {
        const themeSelectorTemplate = document.querySelector(templateName)
        const form = themeSelectorTemplate.content.firstElementChild
        themeSelectorTemplate.replaceWith(form)

        form.addEventListener('change', (e) => {
            const chosenColorScheme = e.target.value
            localStorage.setItem('theme', chosenColorScheme)
            toggleTheme(chosenColorScheme)
        })

        const selectedTheme = localStorage.getItem('theme')
        if (selectedTheme && selectedTheme !== 'undefined') {
            form.querySelector(`[value="${selectedTheme}"]`).checked = true
        }
    }

    const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
    window.addEventListener('load', () => {
        let hasDarkRules = false
        for (const styleSheet of Array.from(document.styleSheets)) {
            let mediaRules = []
            for (const cssRule of styleSheet.cssRules) {
                if (cssRule.type !== CSSRule.MEDIA_RULE) {
                    continue
                }
                // WARNING: Safari does not have/supports `conditionText`.
                if (cssRule.conditionText) {
                    if (cssRule.conditionText !== prefersColorSchemeDark) {
                        continue
                    }
                } else {
                    if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
                        continue
                    }
                }
                mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
            }

            // WARNING: do not try to insert a Rule to a styleSheet you are
            // currently iterating on, otherwise the browser will be stuck
            // in a infinite loop…
            for (const mediaRule of mediaRules) {
                styleSheet.insertRule(mediaRule.cssText)
                hasDarkRules = true
            }
        }
        if (hasDarkRules) {
            loadThemeForm('#theme-selector')
        }
    })
 </script>
 </body>
 </html>
--- a/cache/2021/eef2b3e3085a9b71cd7fe64f21fa0453/index.md
+++ b/cache/2021/eef2b3e3085a9b71cd7fe64f21fa0453/index.md
@@ -0,0 +1,36 @@
 title: Anxious feelings about optimisation through complexity
 url: http://interconnected.org/home/2021/02/12/optimisation
 hash_url: eef2b3e3085a9b71cd7fe64f21fa0453

 <p class="measure-wide f6 f5-l lh-copy black-80">Optimisation makes me itchy.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">A couple of examples. The thermostat Google Nest has <a href="https://support.google.com/googlenest/answer/9244031">Rush Hour Rewards</a> which will <q>automatically tune temperatures before and during a Rush Hour to reduce energy use and lower grid costs</q> (a “Rush Hour” is when everyone turns their air conditioning on at the same time).</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">Similar: <a href="https://carbon.coop/portfolio/power-shaper/">Power Shaper by Carbon Co-op</a> which I’m sorry to pick on because lots of UK energy companies will be doing this with smart meters, but this is the one I saw first. <em>(Thanks <a href="https://holdfastprojects.com">Rod McLaren</a> for sending it my way.)</em></p>
 <blockquote class="bl bw1 pl2 b--light-red ml0 italic i">
 <p class="measure-wide f6 f5-l lh-copy black-80">Carbon Co-op technicians will visit your home and install equipment which will enable certain existing electrical appliances (such as electric vehicle chargers, heat pumps, immersion water heaters, battery storage) to be turned on/off remotely.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">We turn things on/off only when we receive a request from grid operators and other parties.</p>
 </blockquote>
 <p class="measure-wide f6 f5-l lh-copy black-80">On the face of it, this makes a ton of sense.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">We’re shifting to renewable energy. The wind and sun have their own schedule. But say everyone gets home at 7pm and plugs in their new electric car, or turns the kettle at halftime in the football, that’s a demand spike, and that’s when a coal power station fires up, so the energy is supplied to the grid but it’s dirty energy.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">Long term this gets fixed by having neighbourhood batteries to smooth the spikes. Ahead of that, demand can be adjusted by automatically turning things off. Feedback loops.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">BUT.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">In Vernor Vinge’s space opera <a href="https://en.wikipedia.org/wiki/A_Fire_Upon_the_Deep">A Fire Upon the Deep</a> (1992) there’s a planet called <em>Namqem</em> with a high technology civilisation 4,000 years old.</p>
 <blockquote class="bl bw1 pl2 b--light-red ml0 italic i">
 <p class="measure-wide f6 f5-l lh-copy black-80">Namqem was a triumph of distributed automation. And every decade it became a little better. Every decade the flexibility of the governance responded to the pressures to optimize resource allocation, and the margins of safety shrank.</p>
 </blockquote>
 <p class="measure-wide f6 f5-l lh-copy black-80">Which is a problem. As one of the characters says: <q>They’ve accepting optimizing pressures for centuries now. … finally the optimizations have taken them to the point of fragility.</q></p>
 <blockquote class="bl bw1 pl2 b--light-red ml0 italic i">
 <p class="measure-wide f6 f5-l lh-copy black-80">‘The symptoms are classic. The last decade, the rate of system deadlocks has steadily increased throughout Namqem. See here, thirty percent of business commuting between the outer moons is in locked state at any given time.’ All the hardware was in working order, but the system complexity was so great that vehicles could not get the go-ahead.</p>
 </blockquote>
 <p class="measure-wide f6 f5-l lh-copy black-80">So eventually, as an alternative to escalating resource wars, optimisation becomes complete: every embedded computing system an instrument for total social control.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">But it doesn’t help, collapse comes, billions die, and so on.</p>
 <hr class="h1 xh2-ns w1 xw2-ns ml4 mv4 bb bw1 b--white">
 <p class="measure-wide f6 f5-l lh-copy black-80">I must have read Vinge at a particularly susceptible age. Because since then I see optimisation-through-complexity as a particular kind of danger.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">Not optimisation on its own. Doing something with as little energy as possible is <em>elegant.</em></p>
 <p class="measure-wide f6 f5-l lh-copy black-80">And not complexity on its own either. Complexity has its own problems: reduced legibility, the creation of priesthoods to maintain it, etc.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">But when you increase complexity in order to optimise, demand never really goes down. The optimisation becomes an opportunity to do more, and so the complexity gets locked in – there will never be the chance to remove it.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">And that compounding complexity, layers upon layers of it, a nest of interlocking feedback loops, increases the risk of fatal, emergent complexity quakes.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">All of which colours my approach to everything from how I architect my code, to how I organise my finances, to what government policies I like.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">Whenever I see something like Nest’s Rush Hour Rewards or Carbon Co-op’s Power Shaper, it makes me feel like we’re all taking one step closer to an invisible cliff edge, and the drop could be half a mile away, or it could be one inch.</p>
 <hr class="h1 xh2-ns w1 xw2-ns ml4 mv4 bb bw1 b--white">
 <p class="measure-wide f6 f5-l lh-copy black-80">I also have a high level of nervousness around magnets. I grew up with floppy disks (that would be wiped) and cathode ray tube screens (that would be permanently ruined). So magnets on wallets or toys – I’m on edge if they’re ever near electronics, and I watch them with a hawk eye until they’re at a safe distance. Magnets on laptops and iPads still seem wrong to me. Even though it’s fine now and has been for many years.</p>
 <p class="measure-wide f6 f5-l lh-copy black-80">By which I mean, don’t take my views too seriously, I’m a mess of unfounded prejudices about emergent systems and ferrous solids.</p>
--- a/cache/2021/index.html
+++ b/cache/2021/index.html
@@ -75,6 +75,8 @@
      
        <li><a href="/david/cache/2021/3d37e77a601b6dd7043bbb17a4a2d199/" title="Accès à l’article dans le cache local : Le compromis de la vulgarisation">Le compromis de la vulgarisation</a> (<a href="https://tanialouis.fr/2020/12/27/le-compromis-de-la-vulgarisation/" title="Accès à l’article original distant : Le compromis de la vulgarisation">original</a>)</li>
      
        <li><a href="/david/cache/2021/d685a0ad4878f3d833374164b49b3438/" title="Accès à l’article dans le cache local : Read the Principles - Design Justice Network">Read the Principles - Design Justice Network</a> (<a href="https://designjustice.org/read-the-principles" title="Accès à l’article original distant : Read the Principles - Design Justice Network">original</a>)</li>
      
        <li><a href="/david/cache/2021/9c9968045ffe697a08dc13df854247f1/" title="Accès à l’article dans le cache local : I should have loved biology">I should have loved biology</a> (<a href="https://jsomers.net/i-should-have-loved-biology/" title="Accès à l’article original distant : I should have loved biology">original</a>)</li>
      
        <li><a href="/david/cache/2021/c9fad8039837ef9a671e1fb52cbbeb35/" title="Accès à l’article dans le cache local : “Explain a Topic At Multiple Levels…”">“Explain a Topic At Multiple Levels…”</a> (<a href="https://jacobian.org/2021/feb/8/interview-questions-explain-a-topic/" title="Accès à l’article original distant : “Explain a Topic At Multiple Levels…”">original</a>)</li>
@@ -103,6 +105,8 @@
      
        <li><a href="/david/cache/2021/c4dd46c6f0fe9310b47dd3abda0b5280/" title="Accès à l’article dans le cache local : The computer built to last 50 years">The computer built to last 50 years</a> (<a href="https://ploum.net/the-computer-built-to-last-50-years/" title="Accès à l’article original distant : The computer built to last 50 years">original</a>)</li>
      
        <li><a href="/david/cache/2021/13fac7e78342ffd7e5286a6d5519e19e/" title="Accès à l’article dans le cache local : témoignages des enfants de Pessac">témoignages des enfants de Pessac</a> (<a href="https://www.18h39.fr/articles/ils-construisaient-leurs-maisons-tous-ensemble-puis-les-tiraient-au-sort-lhistoire-des-castors.html" title="Accès à l’article original distant : témoignages des enfants de Pessac">original</a>)</li>
      
        <li><a href="/david/cache/2021/e8ebcfcc0dbd4336a82f618a1bd1a818/" title="Accès à l’article dans le cache local : DNA Chisel - a versatile sequence optimizer">DNA Chisel - a versatile sequence optimizer</a> (<a href="https://edinburgh-genome-foundry.github.io/DnaChisel/" title="Accès à l’article original distant : DNA Chisel - a versatile sequence optimizer">original</a>)</li>
      
        <li><a href="/david/cache/2021/388cf40eae756175ee87c9bf7a1548c4/" title="Accès à l’article dans le cache local : No, Really, mRNA Vaccines Are Not Going To Affect Your DNA">No, Really, mRNA Vaccines Are Not Going To Affect Your DNA</a> (<a href="https://www.deplatformdisease.com/blog/no-really-mrna-vaccines-are-not-going-to-affect-your-dna" title="Accès à l’article original distant : No, Really, mRNA Vaccines Are Not Going To Affect Your DNA">original</a>)</li>
@@ -155,8 +159,12 @@
      
        <li><a href="/david/cache/2021/6ad5b5985682512c140781b2b3c9ff7c/" title="Accès à l’article dans le cache local : That which is unique, breaks">That which is unique, breaks</a> (<a href="https://simonsarris.substack.com/p/that-which-is-unique-breaks" title="Accès à l’article original distant : That which is unique, breaks">original</a>)</li>
      
        <li><a href="/david/cache/2021/b7829aa5073173cca4ed3f4ea23e767f/" title="Accès à l’article dans le cache local : Développeur de logiciel senior / principal(e) (Python)">Développeur de logiciel senior / principal(e) (Python)</a> (<a href="https://numerique.canada.ca/join-our-team/positions/d%C3%A9veloppeur-de-logiciel-senior-principal-e-python/" title="Accès à l’article original distant : Développeur de logiciel senior / principal(e) (Python)">original</a>)</li>
      
        <li><a href="/david/cache/2021/c177668b263f39d20788f002446d2a47/" title="Accès à l’article dans le cache local : 6-month consequences of COVID-19 in patients discharged from hospital: a cohort study">6-month consequences of COVID-19 in patients discharged from hospital: a cohort study</a> (<a href="https://www.thelancet.com/journals/lancet/article/PIIS0140-6736(20)32656-8/fulltext" title="Accès à l’article original distant : 6-month consequences of COVID-19 in patients discharged from hospital: a cohort study">original</a>)</li>
      
        <li><a href="/david/cache/2021/75dddb3b875088c9e1908a83687e7725/" title="Accès à l’article dans le cache local : Four fours - Sentiers Media">Four fours - Sentiers Media</a> (<a href="https://sentiers.media/four-fours/" title="Accès à l’article original distant : Four fours - Sentiers Media">original</a>)</li>
      
        <li><a href="/david/cache/2021/59bd3fea3b3b370bd6b116e77effb69e/" title="Accès à l’article dans le cache local : Nostalgie de l'ancien web">Nostalgie de l'ancien web</a> (<a href="https://osd.ovh/index.php?article10/nostalgie-de-lancien-web" title="Accès à l’article original distant : Nostalgie de l'ancien web">original</a>)</li>
      
        <li><a href="/david/cache/2021/75d7cccf22ce15ad026621e8e753d65b/" title="Accès à l’article dans le cache local : Comment fonctionne une centrale nucléaire ?">Comment fonctionne une centrale nucléaire ?</a> (<a href="https://couleur-science.eu/?d=268bbb--comment-fonctionne-une-centrale-nucleaire" title="Accès à l’article original distant : Comment fonctionne une centrale nucléaire ?">original</a>)</li>
@@ -171,6 +179,8 @@
      
        <li><a href="/david/cache/2021/2057ddcf3fd20edd602cee1b08ac17e8/" title="Accès à l’article dans le cache local : Designing Branch: Sustainable Interaction Design Principles">Designing Branch: Sustainable Interaction Design Principles</a> (<a href="https://branch.climateaction.tech/2020/10/15/designing-branch-sustainable-interaction-design-principles/" title="Accès à l’article original distant : Designing Branch: Sustainable Interaction Design Principles">original</a>)</li>
      
        <li><a href="/david/cache/2021/eef2b3e3085a9b71cd7fe64f21fa0453/" title="Accès à l’article dans le cache local : Anxious feelings about optimisation through complexity">Anxious feelings about optimisation through complexity</a> (<a href="http://interconnected.org/home/2021/02/12/optimisation" title="Accès à l’article original distant : Anxious feelings about optimisation through complexity">original</a>)</li>
      
        <li><a href="/david/cache/2021/44064d714aff0deac9f882cc429d8b9d/" title="Accès à l’article dans le cache local : Some rambling thoughts about the stuttering end of the last ice age and what lockdown means">Some rambling thoughts about the stuttering end of the last ice age and what lockdown means</a> (<a href="http://interconnected.org/home/2020/04/20/continuous_partial_lockdown" title="Accès à l’article original distant : Some rambling thoughts about the stuttering end of the last ice age and what lockdown means">original</a>)</li>
      
        <li><a href="/david/cache/2021/0e0d866f920298fbc0624c03ddc83d24/" title="Accès à l’article dans le cache local : Reconnaissance faciale: Clearview AI a violé la vie privée des Canadiens">Reconnaissance faciale: Clearview AI a violé la vie privée des Canadiens</a> (<a href="https://www.ledevoir.com/societe/594536/reconnaissance-faciale-clearview-ai-a-viole-la-vie-privee-des-canadiens" title="Accès à l’article original distant : Reconnaissance faciale: Clearview AI a violé la vie privée des Canadiens">original</a>)</li>