A place to cache linked articles (think custom and personal wayback machine)
Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639
  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,minimum-scale=1,initial-scale=1,shrink-to-fit=no">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>Oil is the New Data (archive) — David Larlet</title>
  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons/apple-touch-icon.png">
  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons/favicon-32x32.png">
  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons/favicon-16x16.png">
  17. <link rel="manifest" href="/manifest.json">
  18. <link rel="mask-icon" href="/static/david/icons/safari-pinned-tab.svg" color="#5bbad5">
  19. <link rel="shortcut icon" href="/static/david/icons/favicon.ico">
  20. <meta name="apple-mobile-web-app-title" content="David Larlet">
  21. <meta name="application-name" content="David Larlet">
  22. <meta name="msapplication-TileColor" content="#da532c">
  23. <meta name="msapplication-config" content="/static/david/icons/browserconfig.xml">
  24. <meta name="theme-color" content="#f0f0ea">
  25. <!-- That good ol' feed, subscribe :p. -->
  26. <link rel=alternate type="application/atom+xml" title=Feed href="/david/log/">
  27. <meta name="robots" content="noindex, nofollow">
  28. <meta content="origin-when-cross-origin" name="referrer">
  29. <!-- Canonical URL for SEO purposes -->
  30. <link rel="canonical" href="https://logicmag.io/nature/oil-is-the-new-data/">
  31. <style>
  32. /* http://meyerweb.com/eric/tools/css/reset/ */
  33. html, body, div, span,
  34. h1, h2, h3, h4, h5, h6, p, blockquote, pre,
  35. a, abbr, address, big, cite, code,
  36. del, dfn, em, img, ins,
  37. small, strike, strong, tt, var,
  38. dl, dt, dd, ol, ul, li,
  39. fieldset, form, label, legend,
  40. table, caption, tbody, tfoot, thead, tr, th, td,
  41. article, aside, canvas, details, embed,
  42. figure, figcaption, footer, header, hgroup,
  43. menu, nav, output, ruby, section, summary,
  44. time, mark, audio, video {
  45. margin: 0;
  46. padding: 0;
  47. border: 0;
  48. font-size: 100%;
  49. font: inherit;
  50. vertical-align: baseline;
  51. }
  52. /* HTML5 display-role reset for older browsers */
  53. article, aside, details, figcaption, figure,
  54. footer, header, hgroup, menu, nav, section { display: block; }
  55. body { line-height: 1; }
  56. blockquote, q { quotes: none; }
  57. blockquote:before, blockquote:after,
  58. q:before, q:after {
  59. content: '';
  60. content: none;
  61. }
  62. table {
  63. border-collapse: collapse;
  64. border-spacing: 0;
  65. }
  66. /* http://practicaltypography.com/equity.html */
  67. /* https://calendar.perfplanet.com/2016/no-font-face-bulletproof-syntax/ */
  68. /* https://www.filamentgroup.com/lab/js-web-fonts.html */
  69. @font-face {
  70. font-family: 'EquityTextB';
  71. src: url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff2') format('woff2'),
  72. url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff') format('woff');
  73. font-weight: 300;
  74. font-style: normal;
  75. font-display: swap;
  76. }
  77. @font-face {
  78. font-family: 'EquityTextB';
  79. src: url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff2') format('woff2'),
  80. url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff') format('woff');
  81. font-weight: 300;
  82. font-style: italic;
  83. font-display: swap;
  84. }
  85. @font-face {
  86. font-family: 'EquityTextB';
  87. src: url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff2') format('woff2'),
  88. url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff') format('woff');
  89. font-weight: 700;
  90. font-style: normal;
  91. font-display: swap;
  92. }
  93. @font-face {
  94. font-family: 'ConcourseT3';
  95. src: url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff2') format('woff2'),
  96. url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff') format('woff');
  97. font-weight: 300;
  98. font-style: normal;
  99. font-display: swap;
  100. }
  101. /* http://practice.typekit.com/lesson/caring-about-opentype-features/ */
  102. body {
  103. /* http://www.cssfontstack.com/ Palatino 99% Win 86% Mac */
  104. font-family: "EquityTextB", Palatino, serif;
  105. background-color: #f0f0ea;
  106. color: #07486c;
  107. font-kerning: normal;
  108. -moz-osx-font-smoothing: grayscale;
  109. -webkit-font-smoothing: subpixel-antialiased;
  110. text-rendering: optimizeLegibility;
  111. font-variant-ligatures: common-ligatures contextual;
  112. font-feature-settings: "kern", "liga", "clig", "calt";
  113. }
  114. pre, code, kbd, samp, var, tt {
  115. font-family: 'TriplicateT4c', monospace;
  116. }
  117. em {
  118. font-style: italic;
  119. color: #323a45;
  120. }
  121. strong {
  122. font-weight: bold;
  123. color: black;
  124. }
  125. nav {
  126. background-color: #323a45;
  127. color: #f0f0ea;
  128. display: flex;
  129. justify-content: space-around;
  130. padding: 1rem .5rem;
  131. }
  132. nav:last-child {
  133. border-bottom: 1vh solid #2d7474;
  134. }
  135. nav a {
  136. color: #f0f0ea;
  137. }
  138. nav abbr {
  139. border-bottom: 1px dotted white;
  140. }
  141. h1 {
  142. border-top: 1vh solid #2d7474;
  143. border-bottom: .2vh dotted #2d7474;
  144. background-color: #e3e1e1;
  145. color: #323a45;
  146. text-align: center;
  147. padding: 5rem 0 4rem 0;
  148. width: 100%;
  149. font-family: 'ConcourseT3';
  150. display: flex;
  151. flex-direction: column;
  152. }
  153. h1.single {
  154. padding-bottom: 10rem;
  155. }
  156. h1 span {
  157. position: absolute;
  158. top: 1vh;
  159. left: 20%;
  160. line-height: 0;
  161. }
  162. h1 span a {
  163. line-height: 1.7;
  164. padding: 1rem 1.2rem .6rem 1.2rem;
  165. border-radius: 0 0 6% 6%;
  166. background: #2d7474;
  167. font-size: 1.3rem;
  168. color: white;
  169. text-decoration: none;
  170. }
  171. h2 {
  172. margin: 4rem 0 1rem;
  173. border-top: .2vh solid #2d7474;
  174. padding-top: 1vh;
  175. }
  176. h3 {
  177. text-align: center;
  178. margin: 3rem 0 .75em;
  179. }
  180. hr {
  181. height: .4rem;
  182. width: .4rem;
  183. border-radius: .4rem;
  184. background: #07486c;
  185. margin: 2.5rem auto;
  186. }
  187. time {
  188. display: bloc;
  189. margin-left: 0 !important;
  190. }
  191. ul, ol {
  192. margin: 2rem;
  193. }
  194. ul {
  195. list-style-type: square;
  196. }
  197. a {
  198. text-decoration-skip-ink: auto;
  199. text-decoration-thickness: 0.05em;
  200. text-underline-offset: 0.09em;
  201. }
  202. article {
  203. max-width: 50rem;
  204. display: flex;
  205. flex-direction: column;
  206. margin: 2rem auto;
  207. }
  208. article.single {
  209. border-top: .2vh dotted #2d7474;
  210. margin: -6rem auto 1rem auto;
  211. background: #f0f0ea;
  212. padding: 2rem;
  213. }
  214. article p:last-child {
  215. margin-bottom: 1rem;
  216. }
  217. p {
  218. padding: 0 .5rem;
  219. margin-left: 3rem;
  220. }
  221. p + p,
  222. figure + p {
  223. margin-top: 2rem;
  224. }
  225. blockquote {
  226. background-color: #e3e1e1;
  227. border-left: .5vw solid #2d7474;
  228. display: flex;
  229. flex-direction: column;
  230. align-items: center;
  231. padding: 1rem;
  232. margin: 1.5rem;
  233. }
  234. blockquote cite {
  235. font-style: italic;
  236. }
  237. blockquote p {
  238. margin-left: 0;
  239. }
  240. figure {
  241. border-top: .2vh solid #2d7474;
  242. background-color: #e3e1e1;
  243. text-align: center;
  244. padding: 1.5rem 0;
  245. margin: 1rem 0 0;
  246. font-size: 1.5rem;
  247. width: 100%;
  248. }
  249. figure img {
  250. max-width: 250px;
  251. max-height: 250px;
  252. border: .5vw solid #323a45;
  253. padding: 1px;
  254. }
  255. figcaption {
  256. padding: 1rem;
  257. line-height: 1.4;
  258. }
  259. aside {
  260. display: flex;
  261. flex-direction: column;
  262. background-color: #e3e1e1;
  263. padding: 1rem 0;
  264. border-bottom: .2vh solid #07486c;
  265. }
  266. aside p {
  267. max-width: 50rem;
  268. margin: 0 auto;
  269. }
  270. /* https://fvsch.com/code/css-locks/ */
  271. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  272. font-size: 1rem;
  273. line-height: calc( 1.5em + 0.2 * 1rem );
  274. }
  275. h1 {
  276. font-size: 1.9rem;
  277. line-height: calc( 1.2em + 0.2 * 1rem );
  278. }
  279. h2 {
  280. font-size: 1.6rem;
  281. line-height: calc( 1.3em + 0.2 * 1rem );
  282. }
  283. h3 {
  284. font-size: 1.35rem;
  285. line-height: calc( 1.4em + 0.2 * 1rem );
  286. }
  287. @media (min-width: 20em) {
  288. /* The (100vw - 20rem) / (50 - 20) part
  289. resolves to 0-1rem, depending on the
  290. viewport width (between 20em and 50em). */
  291. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  292. font-size: calc( 1rem + .6 * (100vw - 20rem) / (50 - 20) );
  293. line-height: calc( 1.5em + 0.2 * (100vw - 50rem) / (20 - 50) );
  294. margin-left: 0;
  295. }
  296. h1 {
  297. font-size: calc( 1.9rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  298. line-height: calc( 1.2em + 0.2 * (100vw - 50rem) / (20 - 50) );
  299. }
  300. h2 {
  301. font-size: calc( 1.5rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  302. line-height: calc( 1.3em + 0.2 * (100vw - 50rem) / (20 - 50) );
  303. }
  304. h3 {
  305. font-size: calc( 1.35rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  306. line-height: calc( 1.4em + 0.2 * (100vw - 50rem) / (20 - 50) );
  307. }
  308. }
  309. @media (min-width: 50em) {
  310. /* The right part of the addition *must* be a
  311. rem value. In this example we *could* change
  312. the whole declaration to font-size:2.5rem,
  313. but if our baseline value was not expressed
  314. in rem we would have to use calc. */
  315. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  316. font-size: calc( 1rem + .6 * 1rem );
  317. line-height: 1.5em;
  318. }
  319. p, li, pre, details {
  320. margin-left: 3rem;
  321. }
  322. h1 {
  323. font-size: calc( 1.9rem + 1.5 * 1rem );
  324. line-height: 1.2em;
  325. }
  326. h2 {
  327. font-size: calc( 1.5rem + 1.5 * 1rem );
  328. line-height: 1.3em;
  329. }
  330. h3 {
  331. font-size: calc( 1.35rem + 1.5 * 1rem );
  332. line-height: 1.4em;
  333. }
  334. figure img {
  335. max-width: 500px;
  336. max-height: 500px;
  337. }
  338. }
  339. figure.unsquared {
  340. margin-bottom: 1.5rem;
  341. }
  342. figure.unsquared img {
  343. height: inherit;
  344. }
  345. @media print {
  346. body { font-size: 100%; }
  347. a:after { content: " (" attr(href) ")"; }
  348. a, a:link, a:visited, a:after {
  349. text-decoration: underline;
  350. text-shadow: none !important;
  351. background-image: none !important;
  352. background: white;
  353. color: black;
  354. }
  355. abbr[title] { border-bottom: 0; }
  356. abbr[title]:after { content: " (" attr(title) ")"; }
  357. img { page-break-inside: avoid; }
  358. @page { margin: 2cm .5cm; }
  359. h1, h2, h3 { page-break-after: avoid; }
  360. p3 { orphans: 3; widows: 3; }
  361. img {
  362. max-width: 250px !important;
  363. max-height: 250px !important;
  364. }
  365. nav, aside { display: none; }
  366. }
  367. ul.with_columns {
  368. column-count: 1;
  369. }
  370. @media (min-width: 20em) {
  371. ul.with_columns {
  372. column-count: 2;
  373. }
  374. }
  375. @media (min-width: 50em) {
  376. ul.with_columns {
  377. column-count: 3;
  378. }
  379. }
  380. ul.with_two_columns {
  381. column-count: 1;
  382. }
  383. @media (min-width: 20em) {
  384. ul.with_two_columns {
  385. column-count: 1;
  386. }
  387. }
  388. @media (min-width: 50em) {
  389. ul.with_two_columns {
  390. column-count: 2;
  391. }
  392. }
  393. .gallery {
  394. display: flex;
  395. flex-wrap: wrap;
  396. justify-content: space-around;
  397. }
  398. .gallery figure img {
  399. margin-left: 1rem;
  400. margin-right: 1rem;
  401. }
  402. .gallery figure figcaption {
  403. font-family: 'ConcourseT3'
  404. }
  405. footer {
  406. font-family: 'ConcourseT3';
  407. display: flex;
  408. flex-direction: column;
  409. border-top: 3px solid white;
  410. padding: 4rem 0;
  411. background-color: #07486c;
  412. color: white;
  413. }
  414. footer > * {
  415. max-width: 50rem;
  416. margin: 0 auto;
  417. }
  418. footer a {
  419. color: #f1c40f;
  420. }
  421. footer .avatar {
  422. width: 200px;
  423. height: 200px;
  424. border-radius: 50%;
  425. float: left;
  426. -webkit-shape-outside: circle();
  427. shape-outside: circle();
  428. margin-right: 2rem;
  429. padding: 2px 5px 5px 2px;
  430. background: white;
  431. border-left: 1px solid #f1c40f;
  432. border-top: 1px solid #f1c40f;
  433. border-right: 5px solid #f1c40f;
  434. border-bottom: 5px solid #f1c40f;
  435. }
  436. </style>
  437. <h1>
  438. <span><a id="jumper" href="#jumpto" title="Un peu perdu ?">?</a></span>
  439. Oil is the New Data (archive)
  440. <time>Pour la pérennité des contenus liés. Non-indexé, retrait sur simple email.</time>
  441. </h1>
  442. <section>
  443. <article>
  444. <h3><a href="https://logicmag.io/nature/oil-is-the-new-data/">Source originale du contenu</a></h3>
  445. <p>I remember being nervous when I flew into Atyrau, Kazakhstan. Before boarding the flight, one of the business managers who organized the trip sent me a message with precise instructions on how to navigate the local airport:</p>
  446. <blockquote><p>Once you land, get into the bus on the right side of the driver. This side opens to the terminal. Pass through immigration, pick up your luggage, and go through Customs. The flight crew will pass out white migration cards. Fill them out, and keep it with your passport. You will need to carry these documents on you at all times once you’ve landed.</p></blockquote>
  447. <p>Another coworker, who had flown in the night before, warned us not to worry if we found ourselves in jail. <i>Don’t panic if you find yourself in jail. Give me a call and we’ll bail you out.</i> Maybe she was joking.</p>
  448. <p>The flight itself was uncanny. I was flying in from Frankfurt, but it felt a lot like a local American flight to somewhere in the Midwest. The plane was filled with middle-aged American businessmen equipped with black Lenovo laptops and baseball caps. The man next to me wore a cowboy-esque leather jacket over a blue-collared business shirt.</p>
  449. <p>After I landed in Atyrau’s single-gate airport, I located my driver, who was holding a card with my name on it. He swiftly led me into a seven-seater Mercedes van and drove me to my hotel, one of the only hotels in the city. Everyone from the flight also seemed to stay there. The drive was short. The city was overwhelmingly gray. Most of it was visibly poor. The hotel was an oasis of wealth. </p>
  450. <p>Across from the hotel was another one of these oases: a gated community with beige bungalows. This was presumably where the expats who worked for Chevron lived. There was a Burger King and a KFC within walking distance. Everyone spoke a bit of English.</p>
  451. <p>Security was taken extremely seriously. Each time we entered one of Chevron’s offices, our passports were checked, our bags were inspected, and our bodies were patted down. Video cameras were mounted on the ceilings of the hallways and conference rooms. We were instructed to travel only using Chevron’s fleet of taxis, which were wired up with cameras and mics.</p>
  452. <p>All of this — Atyrau’s extreme security measures and the steady flow of American businesspeople — comes from the fact that the city is home to Kazakhstan’s biggest and most important oil extraction project. In 1993, shortly after the fall of the Soviet Union, the newly independent nation opened its borders to foreign investment. Kazakhstan’s state-owned energy company agreed to partner with Chevron in a joint venture to extract oil. </p>
  453. <p>The project was named Tengizchevroil, or TCO for short, and it was granted an exclusive forty-year right to the Tengiz oil field near Atyrau. Tengiz carries roughly 26 billion barrels of oil, making it one of the largest fields in the world. Chevron has poured money into the joint venture with the goal of using new technology to increase oil production at the site. And I, a Microsoft engineer, was sent there to help. </p>
  454. <h3>Cloud Wars</h3>
  455. <p>Despite the climate crisis that our planet faces, Big Oil is doubling down on fossil fuels. At over 30 billion barrels of crude oil a year, production has never been <a href="https://transportgeography.org/?page_id=5944">higher</a>. Now, with the help of tech companies like Microsoft, oil companies are using cutting-edge technology to produce even more. </p>
  456. <p>The collaboration between Big Tech and Big Oil might seem counterintuitive. Culturally, who could be further apart? Moreover, many tech companies portray themselves as leaders in corporate sustainability. They try to out-do each other in their support for green initiatives. But in reality, Big Tech and Big Oil are closely linked, and only getting closer. </p>
  457. <p>The foundation of their partnership is the cloud. Cloud computing, like many of today’s online subscription services, is a way for companies to rent servers, as opposed to purchasing them. (This model is more specifically called the <i>public cloud</i>.) It’s like choosing to rent a movie on iTunes for $2.99 instead of buying the DVD for $14.99. In the old days, a company would have to run its website from a server that it bought and maintained itself. By using the cloud, that same company can outsource its infrastructure needs to a cloud provider. </p>
  458. <p>The market is dominated by Amazon’s cloud computing wing, Amazon Web Services (AWS), which now makes up more than half of all of Amazon’s operating income. AWS has grown fast: in 2014, its revenue was $4.6 billion; in 2019, it is set to <a href="https://www.statista.com/statistics/250520/forecast-of-amazon-web-services-revenue/">surpass</a> $36 billion. So many companies run on AWS that when one of its most popular services went down briefly in 2017, it felt like the entire internet stopped working. </p>
  459. <p>Joining the cloud business late, Google and Microsoft are now playing catch-up. As cloud computing becomes widely adopted, Amazon’s competitors are doing whatever they can to grab market share. Over the past several years, Microsoft has reorganized its internal operations to prioritize its cloud business. It is now <a href="https://www.canalys.com/newsroom/aws-and-microsoft-grow-strongly-as-cloud-adoption-shows-no-sign-of-cooling-">spending</a> tens of billions of dollars every year on constructing new data centers around the planet. Meanwhile, Google CEO Sundar Pichai announced that in 2019, the company is <a href="https://www.datacenterknowledge.com/google-alphabet/google-spend-13b-us-data-center-and-office-construction-year">putting</a> $13 billion into constructing new offices and data centers in the US alone, the majority of which will go to the latter.</p>
  460. <p>Startups have long been the biggest early adopters of the public cloud. They are an obvious fit: they do not own their own data centers, so the opportunity cost of switching to the public cloud is low. By contrast, it is much harder for large companies that do run their own data centers to make the leap, since it would require selling or retiring those centers. </p>
  461. <p>This helps explain why cloud providers have only captured about <a href="https://www.networkworld.com/article/3313319/private-cloud-spending-is-increasing-not-decreasing.html">30 percent of the total addressable market</a>. While cloud technology has matured considerably over the past half-decade, big corporations that run their own data centers still dominate the majority of the world’s IT infrastructure. For Amazon, Google, and Microsoft, as well as a few smaller cloud competitors like Oracle and IBM, winning the IT spend of the Fortune 500 is where most of the money in the public cloud market will be made. And among those large companies, Big Oil sits at the top. Out of the biggest ten companies in the world by revenue, <a href="https://en.wikipedia.org/wiki/List_of_largest_companies_by_revenue">six are in the business of oil production</a>. In order words, the success of Big Oil, and the production of fossil fuels, are key to winning the cloud race. </p>
  462. <h3>Making Friends</h3>
  463. <p>In 2017, Chevron signed a seven-year deal with Microsoft, <a href="https://www.moneyshow.com/articles/tradingidea-49236/">potentially worth hundreds of millions of dollars</a>, to establish Microsoft as its primary cloud provider. Oil companies like Chevron are the perfect customer for cloud providers. For years, they have been generating enormous amounts of data about their oil wells. Chevron alone has thousands of oil wells around the world, and each well is covered with sensors that generate more than a terabyte of data per day. (A terabyte is 1,000 gigabytes.) </p>
  464. <p>At best, Chevron has only been able to use a fraction of that data. One problem is the scale of computation required. Many servers are needed to perform the complex workloads capable of analyzing all of this data. As a result, computational needs may skyrocket — but then abruptly subside when the analysis is complete. These sharp fluctuations can put significant pressure on a company like Chevron. During spikes, their data centers lack capacity. During troughs, they sit idly. </p>
  465. <p>This is where the promise of the public cloud comes in. Oil companies can solve their computational woes by turning to the cloud’s renting model, which gives them as many servers as they need and allows them to pay only for what they use. </p>
  466. <p>But Big Tech doesn’t just supply the infrastructure that enables oil companies to crunch their data. It also offers many of the analytical tools themselves. Cloud services provided by Microsoft, Amazon, and Google have the ability to process and analyze vast amounts of data. The tech giants are also leaders in artificial intelligence and machine learning (AI/ML), a field focused on teaching computer systems to automatically perform complex tasks by “learning” from data. With AI/ML, oil companies can make better sense of all the data they are collecting, and can discover patterns that may help them make their operations more efficient and less costly. </p>
  467. <p>AI/ML gives Big Oil yet another reason to depend on Big Tech: the level of sophistication often requires delving into the cutting edge of a field that the tech titans dominate. And if sharing their AI/ML expertise means getting a leg up on the competition in the cloud market, tech companies are more than willing to help. </p>
  468. <p>In recent years, Big Tech has aggressively marketed the transformative potential of the public cloud and AI/ML to Big Oil, with great success. In 2017, Microsoft signed its seven-year contract with Chevron; in 2018, it announced major partnerships with oil giants BP and Equinor; and in 2019, it signed a deal with ExxonMobil that Exxon <a href="https://www.reuters.com/article/us-exxon-mobil-microsoft-cloud/exxon-microsoft-strike-cloud-computing-agreement-for-u-s-shale-idUSKCN1QB1N8">claims</a> is “the industry’s largest [contract] in cloud computing.” Amazon recently opened an AWS office in Houston, the US oil and gas hub, and has been hiring AI/ML experts specifically to work on fossil fuel projects. Google has also developed deep relationships in the industry, partnering with Total, Anadarko Petroleum, and Nine Energy, and appointing Darryl Willis, an oil veteran, to lead Google Cloud’s newly formed Oil, Gas &amp; Energy division. Whatever the tech giants are telling their friends in the fossil fuel industry, it’s working. </p>
  469. <h3>Drill Baby Drill</h3>
  470. <p>The multi-million-dollar partnership between Microsoft and Chevron was the reason I went to Kazakhstan. Microsoft sent me to Atyrau for a week-long workshop to help the Tengiz oil field adopt our technology. I was there to talk about computer vision, a field of AI/ML that gives computers the ability to understand digital images, but the workshop covered a range of topics in both AI/ML and cloud computing. We held it for a team at TCO tasked with boosting daily oil production <a href="https://www.chevron.com/stories/chevron-approves-next-major-tengiz-expansion-project-in-kazakhstan">from 600,000 barrels to 1 million</a>. They wanted to learn about how Microsoft technology could help them modernize their oil field and increase efficiency.</p>
  471. <p>The workshop took place in a large conference room in one of the TCO office buildings. The building itself wasn’t particularly fancy. The exterior was run-down: it looked like it was last renovated in the 1980s. Aside from the security guards dressed in dark clothing, the interior was mostly white, with bright marble floors. The only bits of color came from the biscuits and pastries that were laid out on tables in front of the conference rooms. </p>
  472. <p>At the workshop, I gave a short technical demonstration about running computer vision at scale on Microsoft’s cloud computing platform. There were about forty people in the audience, predominantly businesspeople. My presentation felt like a marketing technique: the point was to flex Microsoft’s engineering prowess to a technically illiterate business crowd. I made sure to include a lot of engineering jargon: “distributed training,” “offline scoring,” “Docker-compatible.”</p>
  473. <p>On the third day of the workshop, a small group of us convened at TCO headquarters in Atyrau to discuss specific AI/ML scenarios they wanted to implement. The meeting room was much nicer than where the workshop was held. It featured new videoconferencing equipment and plush ergonomic chairs. A half-dozen TCO managers were present. Yet, strangely, none of their technical staff attended. The TCO managers were mostly Americans and, with one exception, all white men. They wore monochrome suits and polished leather shoes. I felt out of place wearing sneakers and an oversized button-down. There was not a single Kazakhstani in the room. </p>
  474. <p>To kick off the meeting, a Microsoft account manager gave a PowerPoint presentation that discussed common problems in the oil and gas industry that could be solved using AI/ML. One of the most complex use-cases involved using AI/ML to improve oil exploration. The traditional way to find a new oil or gas deposit is to perform a seismic survey. This is a technique that sends sound waves into the earth and then analyzes the time it takes for those waves to reflect off of different geological features. Because the data is volumetric and spans hundreds of kilometers at a minute granularity, the data collected from a single seismic survey can run over a petabyte. (A petabyte is a million gigabytes.) The output of this data is a 3D geological map, which geophysicists can study in order to recommend promising locations to build wells. </p>
  475. <p>However, interpreting this map is a long and labor-intensive process. It can take months and involve many geophysicists. To make the process more efficient, computer vision technology can automatically segment different geological features to help geophysicists understand the 3D data and identify where best to drill. It seemed like a perfect example of the partnership I had been sent to Kazakhstan to help forge: a technically sophisticated and computationally intensive undertaking that played to the strengths of Big Tech while advancing a core priority of Big Oil, which was to dig more fossil fuels out of the ground while cutting costs. </p>
  476. <h3>Big Oil Is Watching</h3>
  477. <p>But the TCO managers also wanted to talk about something else. “We have a lot of workers in the oil fields. It would be nice to know where they are and what they are doing,” one manager said. “If they are doing anything at all.”</p>
  478. <p>This is what our Chevron partners were most keen to discuss: how to better surveil their workers. TCO had thirty or forty thousand workers on site, nearly all local Kazakhstanis. They worked on rotating shifts — twelve-hour days for two weeks at a time — to keep the oil field running around the clock. And the managers wanted to use AI/ML to keep a closer eye on them. </p>
  479. <p>They proposed using AI/ML to analyze the video streams from existing CCTV cameras to monitor workers throughout the oil field. In particular, they wanted to implement computer vision algorithms that could detect suspicious activity and then identify the worker engaging in that activity. (My Microsoft colleagues and I doubted the technical feasibility of this idea.) Enhancing workplace safety would be the reason for building this system, the managers claimed: more specifically, they hoped to see whether workers were drunk on site so that they could dispatch help and prevent them from hurting themselves. But in order to implement this safety measure, an “always-on” algorithmic monitoring system would have to be put in place — one that would also happen to give management a way to see whether workers were slacking off.</p>
  480. <p>The TCO managers also talked about using the data from the GPS trackers that were installed on all of the trucks used to transport equipment to the oil sites. They told us that the workers were not trustworthy. Drivers would purportedly steal equipment to sell in the black market. Using GPS data, the managers wanted to build a machine learning model to identify suspicious driving activity. It’s not a coincidence that minor tweaks to the same model would also allow management to monitor drivers’ productivity: tracking how frequently they took bathroom breaks, for example, or whether they were sticking to the fastest possible routes.</p>
  481. <p>The TCO managers were also interested in Microsoft products that could analyze large quantities of text. “Let’s say we have the ability to mine everyone’s emails,” one executive asked. “What information could we find?” </p>
  482. <p>When I reflect back on this meeting, it was a surreal experience. Everyone present discussed the idea of building a workplace panopticon with complete normalcy. The TCO managers claimed that monitoring workers was necessary for keeping them safe, or to prevent them from stealing. But it wasn’t convincing in the slightest. We knew that they simply wanted a way to discipline their low-wage Kazakhstani workforce. We knew they wanted a way to squeeze as much work as they could from each worker. </p>
  483. <p>I held my tongue and made sure to appear calm and collected. So did my colleagues. Collectively representing Microsoft, we turned a blind eye, and played along perfectly. We sympathized with TCO’s incriminating portrayal of their Kazakhstani workers and the need to uphold the rule of law. We accepted their explanation that increased surveillance would improve worker safety. But truth be told, we didn’t even need the excuses. Microsoft was hungry for their business. We were ready to concede.</p>
  484. <h3>Skip the Straw</h3>
  485. <p>The topic of worker surveillance took me by surprise. I didn’t sign up for it. I did sign up for helping to accelerate the climate crisis, however — and it was something I had thought about a lot by the time I landed in Atyrau. </p>
  486. <p>When I was first asked to present at the workshop, I was excited. It was good for my career, the technology was fascinating, and I had never been to Kazakhstan. But I hesitated. Did I really want to help Chevron destroy the planet? There were others on my team who could have easily gone in my place. Still, I decided to go. I wanted to learn about the oil industry and the kinds of investments that Big Tech was making. I wanted a front-row seat to the Microsoft-Chevron partnership. I wanted to know what we were up against. </p>
  487. <p>During the workshop, I asked a coworker how she felt about Microsoft working with Big Oil. She responded sympathetically, understanding my concerns about climate change. But she also seemed to feel there was nothing we could do. For her and many other colleagues I’ve spoken to, change has to happen at the top. The problem, of course, is that the top has powerful incentives not to change. Microsoft executives aren’t going to give up on the billions of dollars to be made from Big Oil, especially if it helps them win more of the coveted cloud market.</p>
  488. <p>They are happy to offer employees small ways to live more sustainable lives, however. The company runs various recycling programs, encourages employees to “skip the straw” to reduce plastic consumption, and funds sustainability hackathons. (One hackathon project involved using AI/ML to detect trash in the ocean.) More broadly, Microsoft works hard to present an environmentally friendly public face. Its most ambitious green initiative is its promise to power its energy-hungry data centers with renewable sources. In 2016, Microsoft announced its goal to transition its data centers to 50 percent renewable energy by 2018. Hitting that target one year early, president and chief legal officer Brad Smith announced that the next goal is to <a href="https://blogs.microsoft.com/on-the-issues/2019/04/15/were-increasing-our-carbon-fee-as-we-double-down-on-sustainability/">surpass</a> 70 percent renewable by 2023. “Time is too short, resources too thin and the impact too large to wait for all the answers to act,” he said. </p>
  489. <p>On the surface, then, Microsoft appears to be committed to fighting climate change. Google has constructed a similar reputation. But in reality, these companies are doing just enough to keep their critics distracted while teaming up with the industry that is at the root of the climate crisis. Why go through the effort of using clean energy to power your data centers when those same data centers are being used by companies like Chevron to produce more oil?</p>
  490. <h3>After Empire</h3>
  491. <p>At the workshop in Atyrau, a young Kazakhstani data scientist approached me to ask about a project that he was migrating to Microsoft’s cloud platform. He didn’t speak English fluently, but I could tell he was a good engineer. I wasn’t sure if he really needed my help. It seemed like he just wanted to chat with another engineer in a room filled with businesspeople.</p>
  492. <p>Afterwards, he told me a bit about how he ended up working for TCO, and how he wasn’t able to find any other opportunities in the country that could match the offer. He had attended Purdue University to get an undergraduate degree in computer science. But since the Kazakhstan government paid for his tuition, he had to return to the country to work. “It means that I have to work in oil,” he said. “It’s basically the only industry that pays.” </p>
  493. <p>Speaking with him made me realize the extent of oil’s dominance in Kazakhstan. Oil is by far the biggest economic sector, accounting for 63 percent of the country’s total exports. In 2013, TCO <a href="https://en.tengrinews.kz/companies/tengizchevroil-brings-payments-to-kazakhstan-to-15-billion-26285/">made</a> $15 billion in direct payments to the government — an enormous figure, considering that the country’s entire tax revenue that year came to $21 billion. TCO is also a major source of wealth for the region. For years, the venture has <a href="http://www.tengizchevroil.com/community">invested</a> millions of dollars into building schools, community centers, and fitness centers for the local people. </p>
  494. <p>Kazakhstan’s dependence on oil has only grown over the past decade. In 2016, TCO announced a <a href="https://www.chevron.com/stories/chevron-approves-next-major-tengiz-expansion-project-in-kazakhstan">$36.8 billion expansion</a> to the Tengiz project, tying the country’s economic future even more closely to fossil fuels. To make matters worse, the country’s ability to produce oil relies heavily on multinational oil companies. At the time of its founding, TCO was a fifty-fifty partnership between Chevron and the state-owned KazMunayGas. Since then, ExxonMobil and the Russian oil company LukArco have joined the venture, but only KazMunayGas’s share has been diluted.</p>
  495. <p>While the country would struggle to take advantage of its oil-rich lands without the help of these foreign partners, the partnership is far from a win-win deal. Chevron keeps a tight grip on power, appointing most members of TCO’s upper ranks. The power dynamic was clear at the workshop: lower-level employees were Kazahkstanis while management was almost entirely American. The local economy has also completely aligned itself with the needs of the American-dominated TCO. TCO proudly announced in Q1 of 2019 that it spent over $1 billion on Kazakhstani goods and services, which includes hiring more than forty thousand local workers to work in the oil field. But this makes local businesses highly dependent on TCO. If American oil companies pulled out of the venture or slashed funding, TCO would crumble, and many businesses would lose their biggest (and often only) customer, leaving the economy in shambles.</p>
  496. <p>Big Tech isn’t responsible for Kazakhstan’s reliance on oil. Nor can we blame it for the climate catastrophe that we’re facing. But it is certainly exacerbating both. While Kazahkstan’s economy may benefit in the short run, intensifying the climate disaster will ultimately hurt the country too. Research shows that the region will <a href="https://link.springer.com/article/10.1007/s10113-015-0893-z">suffer</a> from increased aridity and more frequent heat waves, which could decrease crop yields and challenge food security.</p>
  497. <p>How can tech help, instead of hurt, the climate? How can tech companies make local economies more resilient rather than more vulnerable? How can we demand climate justice from Microsoft, a company that claims to be a leader in the fight against climate change?</p>
  498. <p>While I was in Atyrau, these very questions were being asked back home. Amazon employees in the US published an open <a href="https://medium.com/@amazonemployeesclimatejustice/public-letter-to-jeff-bezos-and-the-amazon-board-of-directors-82a8405f5e38">letter</a> calling on their company to reduce its carbon footprint and cancel its many contracts with Big Oil. Sitting in my hotel room not far from one of the largest oil fields in the world, I watched the letter blow up on my social media feeds. The number of Amazon signatures exploded: “3,500 employees challenge Bezos”, “4,200 Amazon workers push for climate action”, “6,000 employees sign an open letter to Bezos.”</p>
  499. <p>I was thrilled. Tech workers like me were taking a stand against our industry’s role in accelerating the climate crisis. They weren’t waiting for change at the top; they were demanding change from below.</p>
  500. <p>Then I thought of the young Kazakhstani engineer. What happens to people like him after we decarbonize? If Chevron and other oil giants cease operations, it would decimate the economy of places like Kazakhstan — places whose dependency on oil has been actively encouraged by those companies, which have in turn profited handsomely from it. Resource extraction is an ancient imperial practice. As tech workers join the movement for climate justice, we must also find ways to undo the legacies of Big Oil’s imperialism, and bring countries like Kazakhstan fairly and safely into a carbon-free future.</p>
  501. <p>But it won’t be easy. When I returned to the US, I learned that Bezos had effectively ignored the demands of over 8,000 of his employees. The open letter was an important first step, but more action will be needed for Amazon to drop its oil partnerships. We have a long fight ahead of us, and the stakes are high. We have, quite literally, a world to win.</p>
  502. </article>
  503. </section>
  504. <nav id="jumpto">
  505. <p>
  506. <a href="/david/blog/">Accueil du blog</a> |
  507. <a href="https://logicmag.io/nature/oil-is-the-new-data/">Source originale</a> |
  508. <a href="/david/stream/2019/">Accueil du flux</a>
  509. </p>
  510. </nav>
  511. <footer>
  512. <div>
  513. <img src="/static/david/david-larlet-avatar.jpg" loading="lazy" class="avatar" width="200" height="200">
  514. <p>
  515. Bonjour/Hi!
  516. Je suis <a href="/david/" title="Profil public">David&nbsp;Larlet</a>, je vis actuellement à Montréal et j’alimente cet espace depuis 15 ans. <br>
  517. Si tu as apprécié cette lecture, n’hésite pas à poursuivre ton exploration. Par exemple via les <a href="/david/blog/" title="Expériences bienveillantes">réflexions bimestrielles</a>, la <a href="/david/stream/2019/" title="Pensées (dés)articulées">veille hebdomadaire</a> ou en t’abonnant au <a href="/david/log/" title="S’abonner aux publications via RSS">flux RSS</a> (<a href="/david/blog/2019/flux-rss/" title="Tiens c’est quoi un flux RSS ?">so 2005</a>).
  518. </p>
  519. <p>
  520. Je m’intéresse à la place que je peux avoir dans ce monde. En tant qu’humain, en tant que membre d’une famille et en tant qu’associé d’une coopérative. De temps en temps, je fais aussi des <a href="https://github.com/davidbgk" title="Principalement sur Github mais aussi ailleurs">trucs techniques</a>. Et encore plus rarement, <a href="/david/talks/" title="En ce moment je laisse plutôt la place aux autres">j’en parle</a>.
  521. </p>
  522. <p>
  523. Voici quelques articles choisis :
  524. <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,
  525. <a href="/david/blog/2018/bivouac-automnal/" title="Accéder à l’article complet">Bivouac automnal</a>,
  526. <a href="/david/blog/2018/commodite-effondrement/" title="Accéder à l’article complet">Commodité et effondrement</a>,
  527. <a href="/david/blog/2017/donnees-communs/" title="Accéder à l’article complet">Des données aux communs</a>,
  528. <a href="/david/blog/2016/accompagner-enfant/" title="Accéder à l’article complet">Accompagner un enfant</a>,
  529. <a href="/david/blog/2016/senior-developer/" title="Accéder à l’article complet">Senior developer</a>,
  530. <a href="/david/blog/2016/illusion-sociale/" title="Accéder à l’article complet">L’illusion sociale</a>,
  531. <a href="/david/blog/2016/instantane-scopyleft/" title="Accéder à l’article complet">Instantané Scopyleft</a>,
  532. <a href="/david/blog/2016/enseigner-web/" title="Accéder à l’article complet">Enseigner le Web</a>,
  533. <a href="/david/blog/2016/simplicite-defaut/" title="Accéder à l’article complet">Simplicité par défaut</a>,
  534. <a href="/david/blog/2016/minimalisme-esthetique/" title="Accéder à l’article complet">Minimalisme et esthétique</a>,
  535. <a href="/david/blog/2014/un-web-omni-present/" title="Accéder à l’article complet">Un web omni-présent</a>,
  536. <a href="/david/blog/2014/manifeste-developpeur/" title="Accéder à l’article complet">Manifeste de développeur</a>,
  537. <a href="/david/blog/2013/confort-convivialite/" title="Accéder à l’article complet">Confort et convivialité</a>,
  538. <a href="/david/blog/2013/testament-numerique/" title="Accéder à l’article complet">Testament numérique</a>,
  539. et <a href="/david/blog/" title="Accéder aux archives">bien d’autres…</a>
  540. </p>
  541. <p>
  542. On peut <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">échanger par courriel</a>. Si éventuellement tu souhaites que l’on travaille ensemble, tu devrais commencer par consulter le <a href="http://larlet.com">profil dédié à mon activité professionnelle</a> et/ou contacter directement <a href="http://scopyleft.fr/">scopyleft</a>, la <abbr title="Société coopérative et participative">SCOP</abbr> dont je fais partie depuis six ans. Je recommande au préalable de lire <a href="/david/blog/2018/cout-site/" title="Attention ce qui va suivre peut vous choquer">combien coûte un site</a> et pourquoi je suis plutôt favorable à une <a href="/david/pro/devis/" title="Discutons-en !">non-demande de devis</a>.
  543. </p>
  544. <p>
  545. Je ne traque pas ta navigation mais mon
  546. <abbr title="Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33.184162340">hébergeur</abbr>
  547. conserve des logs d’accès.
  548. </p>
  549. </div>
  550. </footer>
  551. <script type="text/javascript">
  552. ;(_ => {
  553. const jumper = document.getElementById('jumper')
  554. jumper.addEventListener('click', e => {
  555. e.preventDefault()
  556. const anchor = e.target.getAttribute('href')
  557. const targetEl = document.getElementById(anchor.substring(1))
  558. targetEl.scrollIntoView({behavior: 'smooth'})
  559. })
  560. })()
  561. </script>