<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud on NotNil Blog</title><link>https://notnil.org/en/tags/cloud/</link><description>Recent content in Cloud on NotNil Blog</description><generator>Hugo</generator><language>en-US</language><copyright>© Matthieu Moreau</copyright><lastBuildDate>Mon, 12 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://notnil.org/en/tags/cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>Why bet on Google in the generative AI race</title><link>https://notnil.org/en/posts/20-betongoogle/</link><pubDate>Mon, 12 Feb 2024 00:00:00 +0000</pubDate><guid>https://notnil.org/en/posts/20-betongoogle/</guid><description>&lt;figure&gt;&lt;img src="https://notnil.org/images/posts/betOnGoogle/feature.png"&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;p&gt;I don&amp;rsquo;t want this post to be interpreted as an advertorial in favor of Google, just a cold analysis of what I see around me and on our clients&amp;rsquo; projects at &lt;a href="https://coddity.com"&gt;Coddity&lt;/a&gt;. It will inevitably evolve with the progress and the maturity of OpenAI or Mistral (and their API 🇫🇷).&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;[DISCLAIMER1]&lt;/strong&gt; I&amp;rsquo;m taking Meta and Mistral out of the equation, my point being about the use of LLMs via API.&lt;/p&gt;</description></item><item><title>Cloud and skills, part 2</title><link>https://notnil.org/en/posts/7-competences2/</link><pubDate>Sun, 04 Dec 2022 00:00:00 +0000</pubDate><guid>https://notnil.org/en/posts/7-competences2/</guid><description>&lt;figure&gt;&lt;img src="https://notnil.org/images/posts/comp2/giscard_punk_feature.jpg" width="600"&gt;&lt;figcaption&gt;&#10;&#9;&#9;&#9;&lt;h4&gt;The France that wins&lt;/h4&gt;&#10;&#9;&#9;&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;p&gt;This article follows on from a &lt;a href="https://notnil.org/en/posts/4-competences1/"&gt;previous&lt;/a&gt; one, in which I talked about building individual skills, taking as an example a developer who deploys an application on PaaS rather than deploying it on a server, at least once.&#10;In this post, I mean to let that line of thought drift toward how skills get built at the scale of our country.&lt;/p&gt;&#10;&lt;p&gt;Watch out, this is going to go far!&lt;/p&gt;</description></item><item><title>Cloud and skills, part 1</title><link>https://notnil.org/en/posts/4-competences1/</link><pubDate>Sun, 06 Nov 2022 00:00:00 +0000</pubDate><guid>https://notnil.org/en/posts/4-competences1/</guid><description>&lt;h1 id="prelude"&gt;Prelude&lt;/h1&gt;&#10;&lt;p&gt;What follows is the start of a broader reflection on how computing skills are managed in the age of cloud-everything, whether individual or collective, at the scale of a company, or even of a country.&lt;/p&gt;&#10;&lt;h1 id="the-famous-side-project"&gt;The famous &amp;ldquo;side project&amp;rdquo;&lt;/h1&gt;&#10;&lt;p&gt;In recruiting I meet about one junior dev a week, from every kind of background: engineering school, DUT/BUT, short program, bootcamp, or even self-taught.&lt;/p&gt;&#10;&lt;p&gt;On this kind of profile, we are obviously interested in the projects the candidate has built, and all the more in the ones built on their own time, which very often give a better read on the candidate, their skills, their expectations, and what drives them.&lt;/p&gt;</description></item></channel></rss>