<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Learning on Markus Löning</title><link>https://www.mloning.com/tags/learning/</link><description>Recent content in Learning on Markus Löning</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2025 Markus Löning</copyright><lastBuildDate>Mon, 06 Jul 2026 18:03:47 +0200</lastBuildDate><atom:link href="https://www.mloning.com/tags/learning/index.xml" rel="self" type="application/rss+xml"/><item><title>Juggling</title><link>https://www.mloning.com/posts/juggling/</link><pubDate>Sun, 12 Apr 2026 19:10:06 +0200</pubDate><guid>https://www.mloning.com/posts/juggling/</guid><description>&lt;p&gt;I first learned to juggle three balls at university, together with a group of friends during our exam period.
During the following summer break, I kept practicing, juggling two balls in one hand while walking and holding my dog’s leash in the other.
When I returned for the next term, I could juggle four balls.
Five balls requires serious practice.
While I’ve felt like I’ve been close at times, I have never quite managed to get the five-ball cascade flowing.&lt;/p&gt;</description></item><item><title>Learning C++</title><link>https://www.mloning.com/posts/learning-cpp/</link><pubDate>Wed, 14 May 2025 08:47:02 +0200</pubDate><guid>https://www.mloning.com/posts/learning-cpp/</guid><description>&lt;h2 id="build-process"&gt;Build process&lt;/h2&gt;
&lt;p&gt;For an introduction to the build process, see &lt;a href="https://github.com/green7ea/blog/blob/master/cpp-build-process/README.md"&gt;The C++ Build Process Explained&lt;/a&gt; and the related &lt;a href="https://news.ycombinator.com/item?id=18454140"&gt;HackerNews thread&lt;/a&gt;.
For a deeper explanation, see &lt;a href="https://www.youtube.com/watch?v=dOfucXtyEsU"&gt;The Bits Between the Bits: How We Get to main()&lt;/a&gt;.
For a real-time visualisation of the build process, see &lt;a href="https://danielchasehooper.com/posts/syscall-build-snooping/"&gt;this post&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Writing well</title><link>https://www.mloning.com/posts/writing-well/</link><pubDate>Sun, 12 Jan 2025 11:54:52 +0100</pubDate><guid>https://www.mloning.com/posts/writing-well/</guid><description>&lt;p&gt;Here are some resources for writing well.&lt;/p&gt;
&lt;h2 id="general-writing"&gt;General writing&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Style: The Basics of Clarity and Grace&amp;rdquo; (3rd Edition) 3rd Edition, by Joseph M. Williams&lt;/li&gt;
&lt;li&gt;&amp;ldquo;The Chicago Manual of Style&amp;rdquo;, 16th Edition Sixteenth Edition, by University of Chicago Press Staff&lt;/li&gt;
&lt;li&gt;&lt;a href="https://matt.might.net/articles/shell-scripts-for-passive-voice-weasel-words-duplicates/"&gt;https://matt.might.net/articles/shell-scripts-for-passive-voice-weasel-words-duplicates/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="technical-docs"&gt;Technical docs&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A Manual for Writers of Research Papers, Theses, and Dissertations, Seventh Edition: Chicago Style for Students and Researchers (Chicago Guides to Writing, Editing, and Publishing) 7th Edition, by Kate L. Turabian (Author), Wayne C. Booth Gregory G. Colomb Joseph M. Williams&lt;/li&gt;
&lt;li&gt;&lt;a href="https://blog.pragmaticengineer.com/scaling-engineering-teams-via-writing-things-down-rfcs/"&gt;https://blog.pragmaticengineer.com/scaling-engineering-teams-via-writing-things-down-rfcs/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.industrialempathy.com/posts/design-docs-at-google/"&gt;https://www.industrialempathy.com/posts/design-docs-at-google/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/joelparkerhenderson/architecture-decision-record/"&gt;https://github.com/joelparkerhenderson/architecture-decision-record/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://surfingcomplexity.blog/2022/11/24/writing-docs-well-why-should-a-software-engineer-care/"&gt;https://surfingcomplexity.blog/2022/11/24/writing-docs-well-why-should-a-software-engineer-care/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://stevelosh.com/blog/2013/09/teach-dont-tell/"&gt;https://stevelosh.com/blog/2013/09/teach-dont-tell/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://medium.com/@apappascs/write-like-an-amazonian-14-tips-for-clear-and-persuasive-communication-e2a11afc7362"&gt;https://medium.com/@apappascs/write-like-an-amazonian-14-tips-for-clear-and-persuasive-communication-e2a11afc7362&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://grantslatton.com/how-to-design-document"&gt;https://grantslatton.com/how-to-design-document&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="tutorials"&gt;Tutorials&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://refactoringenglish.com/chapters/rules-for-software-tutorials/"&gt;https://refactoringenglish.com/chapters/rules-for-software-tutorials/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Learning Rust</title><link>https://www.mloning.com/posts/learning-rust/</link><pubDate>Sat, 11 Jan 2025 12:08:32 +0100</pubDate><guid>https://www.mloning.com/posts/learning-rust/</guid><description>&lt;h2 id="general-resources"&gt;General resources&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Why Rust? See &lt;a href="http://youtube.com/watch?v=DnT-LUQgc7s"&gt;Considering Rust&lt;/a&gt; by Jon Gjengset&lt;/li&gt;
&lt;li&gt;&lt;a href="https://doc.rust-lang.org/book/"&gt;Rust Book&lt;/a&gt; (introductory book)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.goodreads.com/book/show/25550614-programming-rust"&gt;Programming Rust: Fast, Safe Systems Development&lt;/a&gt; (book)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.lurklurk.org/effective-rust/title-page.html"&gt;Effective Rust&lt;/a&gt; (book)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="lifetimes"&gt;Lifetimes&lt;/h2&gt;
&lt;p&gt;As a Rust beginner, I understood lifetimes backwards, thinking &lt;code&gt;&amp;lt;'a&amp;gt;&lt;/code&gt; means I&amp;rsquo;m declaring a lifetime which I then use.
What that actually declares is a placeholder for a lifetime the compiler will attempt to find wherever that variable or function is used, just as it would attempt to find a valid type for a generic type &lt;code&gt;&amp;lt;T&amp;gt;&lt;/code&gt; at the points of usage.
In this sense, lifetimes and generics are similar concepts: code is generic over some lifetimes just as it can be generic over some type (thanks to &lt;a href="https://news.ycombinator.com/item?id=46278224"&gt;wrs&lt;/a&gt; for making me realise this).&lt;/p&gt;</description></item><item><title>Learning French</title><link>https://www.mloning.com/posts/learning-french/</link><pubDate>Tue, 30 Apr 2024 11:17:44 +0200</pubDate><guid>https://www.mloning.com/posts/learning-french/</guid><description>&lt;p&gt;I&amp;rsquo;ve started learning French.
Here are some resources I found useful.&lt;/p&gt;
&lt;p&gt;Also see my post on &lt;a href="https://www.mloning.com/posts/exploring-paris/"&gt;exploring Paris&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="listen"&gt;Listen&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.radiofrance.fr/"&gt;Radio France&lt;/a&gt;, different radio stations and podcasts (e.g. &lt;a href="https://www.radiofrance.fr/franceinter"&gt;France Inter&lt;/a&gt;, &lt;a href="https://www.francetvinfo.fr/en-direct/radio.html"&gt;France Info&lt;/a&gt; or &lt;a href="https://www.radiofrance.fr/franceculture"&gt;France Culture&lt;/a&gt;); for French-only music, see &lt;a href="https://www.radiofrance.fr/fip/radio-sacre-francais"&gt;Fip - Sacré Français&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfi.fr/fr/"&gt;Radio France Internationale&lt;/a&gt;, e.g. &lt;a href="https://francaisfacile.rfi.fr/fr/podcasts/journal-en-fran%C3%A7ais-facile/"&gt;Journal en français facile&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.byte.fm/"&gt;ByteFM&lt;/a&gt; programs &lt;a href="https://www.byte.fm/sendungen/la-france-en-confidence/"&gt;France, en confidence&lt;/a&gt; and &lt;a href="https://www.byte.fm/sendungen/what-the-france/"&gt;What the France&lt;/a&gt; about French music, moderated in German&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For example, here a two Radio France podcasts on the French Revolution:&lt;/p&gt;</description></item></channel></rss>