davidbgk
/
larlet-fr-david-cache
Seguir 1
Destacar 0
Fork 0
Código Lanzamientos 0 Actividad
A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
60 Commits
1 Rama
Árbol: e305ebd928
Ramas Etiquetas
${ item.name }
Crear rama ${ searchTerm }
desde 'e305ebd928'
${ noResults }
larlet-fr-david-cache/cache/2020/ef5d670c8473add5c3e43f8d4db.../index.html

index.html 8.3KB
Original Blame Histórico

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788 
  1. <!doctype html><!-- This is a valid HTML5 document. -->

  2. <!-- Screen readers, SEO, extensions and so on. -->

  3. <html lang="fr">

  4. <!-- Has to be within the first 1024 bytes, hence before the <title>

  5.   See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->

  6. <meta charset="utf-8">

  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->

  8. <!-- The viewport meta is quite crowded and we are responsible for that.

  9.   See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->

  10. <meta name="viewport" content="width=device-width,initial-scale=1">

  11. <!-- Required to make a valid HTML5 document. -->

  12. <title>Integrated systems for integrated programmers (archive) — David Larlet</title>

  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->

  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">

  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">

  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">

  17. <link rel="manifest" href="/static/david/icons2/site.webmanifest">

  18. <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">

  19. <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">

  20. <meta name="msapplication-TileColor" content="#f0f0ea">

  21. <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">

  22. <meta name="theme-color" content="#f0f0ea">

  23. <!-- Documented, feel free to shoot an email. -->

  24. <link rel="stylesheet" href="/static/david/css/style_2020-04-25.css">

  25. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->

  26. <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>

  27. <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>

  28. <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>

  29. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  30. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  31. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  32. 

  33.   <meta name="robots" content="noindex, nofollow">

  34.   <meta content="origin-when-cross-origin" name="referrer">

  35.   <!-- Canonical URL for SEO purposes -->

  36.   <link rel="canonical" href="https://m.signalvnoise.com/integrated-systems-for-integrated-programmers/">

  37. 

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

  39. 

  40. <article>

  41. <h1>Integrated systems for integrated programmers</h1>

  42. <h2><a href="https://m.signalvnoise.com/integrated-systems-for-integrated-programmers/">Source originale du contenu</a></h2>

  43. <p>One of the great tragedies of modern web development over the last five years or so has been the irrational exuberance for microservices. The idea that making a single great web application had simply become too hard, but if we broke that app up into many smaller apps, it’d all be much easier. Turned out, surprise-surprise, that it mostly wasn’t.</p>

  44. 

  45. <p>As Kelsey Hightower <a href="https://changelog.com/posts/monoliths-are-the-future">searingly put the fallacy</a>: “We’re gonna break it up and somehow find the engineering discipline we never had in the first place”.</p>

  46. 

  47. <p>But it’s one of those hard lessons that nobody actually wants to hear. You don’t want to hear that the reason your monolith is a spaghetti monster is because you let it become that way, one commit at the time, due to weak habits, pressurized deadlines, or simply sheer lack of competence. No, what you want to hear is that none of that mess is your fault. That it was simply because of the oppressive monolithic architecture. And that, really, you’re just awesome, and if you take your dirty code and stick it into this new microservices tumbler, it’s going to come out sparking clean, smelling like fucking daffodils.</p>

  48. 

  49. <p>The great thing about such delusions is that they can keep you warm for quite a while. A yeah, sure, maybe the complexities of your new microservices monstrosity are plain as day right from the get go, but you can always excuse them with “it’s really going to pay off once we…” bullshit. And it’ll work! For a while. Because, who knows? Maybe this is better? But it’s not. And the day you have to really admit its not, you’re probably not even still there. On to the next thing.</p>

  50. 

  51. <p>Microservices as an architectural gold rush appealed to developers for the same reason TDD appeals to developers: <a href="https://www.youtube.com/watch?v=9LfmrkyP81M&amp;t=19m59s">it’s the pseudoscientific promise of a diet</a>. The absolution of a new paradigm to wash away and forgive our sins. Who doesn’t want that?</p>

  52. 

  53. <p>Well, maybe you? Now after you’ve walked through the intellectual desert of a microservice approach to a problem that didn’t remotely warrant it (ie, almost all of them). Maybe now you’re ready to hear a different story. There’s a slot in your brain for a counterargument that just wasn’t there before.</p>

  54. 

  55. <p>So here’s the counterargument: Integrated systems are good. Integrated developers are good. Being able to wrap your mind around the whole application, and have developers who are able to make whole features, is good! The road to madness and despair lays in specialization and compartmentalization.</p>

  56. 

  57. <p>The galaxy brain takes it all in.</p>

  58. 

  59. <p>But of course, you cry, what if the system is too large to fit in my brain? Won’t it just swap and swap until I kernel failure? Yes, if you try to stick in a bloated beast of an application, sure.</p>

  60. 

  61. <p>So the work is to shrink the conceptual surface area of your application until it fits in a normal, but capable and competent, programmer’s brain. Using <a href="https://www.youtube.com/watch?v=zKyv-IGvgGE&amp;t=17m27s">conceptual compression</a>, sheer good code writing, a productive and succinct environment, using shortcuts and patterns. That’s the work.</p>

  62. 

  63. <p>But the payoff is glorious. Magnificent. SUBLIME. The magic of working on an integrated system together with integrated programmers is a line without limits, arbitrary boundaries, or sully gatekeepers.</p>

  64. 

  65. <p>Forget frontend or backend. The answer is all of it. At the same time. In the same mind.</p>

  66. 

  67. <p>This sounds impossible if you’ve cooked your noodle too long in the stew of modern <a href="https://www.joelonsoftware.com/2001/04/21/dont-let-architecture-astronauts-scare-you/">astronautic abstractions</a>. If you turn down the temperature, you’ll see that the web is actually much the same as it always was. Sure, a few expectations increased here, and a couple of breakthrough techniques appeared there, but fundamentally, it’s the same. What changed was us. And mostly not in ways for the better.</p>

  68. 

  69. <p>If your lived experience still haven’t hit the inevitable wall of defeat on the question of microservices, then be my guest, sit there with your folded arms and your smug pout. It’s ok. I get it. There’s not an open slot for this argument in your brain just yet. It’s ok. I’m patient! I’ll still be here in a couple of years when there’s room. And then I’ll send you a link to this article on twitter.</p>

  70. 

  71. <p>Peace. Love. Integration.</p>

  72. </article>

  73. 

  74. 

  75. <hr>

  76. 

  77. <footer>

  78.   <p>

  79.     <a href="/david/" title="Aller à l’accueil">🏠</a> •

  80.     <a href="/david/log/" title="Accès au flux RSS">🤖</a> •

  81.     <a href="http://larlet.com" title="Go to my English profile" data-instant>🇨🇦</a> •

  82.     <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">📮</a> •

  83.     <abbr title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340">🧚</abbr>

  84.   </p>

  85. </footer>

  86. <script src="/static/david/js/instantpage-3.0.0.min.js" type="module" defer></script>

  87. </body>

  88. </html>