<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated></updated>
  <generator>https://njump.me</generator>

  <title>Nostr notes by </title>
  <author>
    <name></name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://njump.me/npub102tuv6c8ahufpx0qcw2wasalsklw05h23f25agn05r2asleqhk3sjuf9ae.rss" />
  <link href="https://njump.me/npub102tuv6c8ahufpx0qcw2wasalsklw05h23f25agn05r2asleqhk3sjuf9ae" />
  <id>https://njump.me/npub102tuv6c8ahufpx0qcw2wasalsklw05h23f25agn05r2asleqhk3sjuf9ae</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://njump.me/nevent1qqsxtf8luyw329735venr0qj2l4vgtzwatw5sa05s6rznsuaue6jyhczypaf03ntqlkl3yyeurpefmkrh7zmae7ja2992n4zd7sdtkrlyz76x25rnch</id>
    
      <title type="html">A surge of Do iOS newsletter signups The Do iOS newsletter had a ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsxtf8luyw329735venr0qj2l4vgtzwatw5sa05s6rznsuaue6jyhczypaf03ntqlkl3yyeurpefmkrh7zmae7ja2992n4zd7sdtkrlyz76x25rnch" />
    <content type="html">
      A surge of Do iOS newsletter signups&lt;br/&gt;&lt;br/&gt;The Do iOS newsletter had a couple of thousand subscribers. Then, on October 22, Apple featured the conference in the Meet with Apple newsletter. The subject was “Upcoming events: Explore iPhone Duo in new cities.” Apple does not publish that email on the web. I kept a short scroll through it on Mastodon. The community-events section of the mail is the same list as Apple’s community events page, where Do iOS is listed. More than 18,000 people joined.&lt;br/&gt;I mailed them twice. The first send bounced hard enough that Amazon SES put the account under review. The second send was clean. Together they sold a handful of tickets.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://appforce1.net/blog/a-surge-of-newsletter-signups&#34;&gt;https://appforce1.net/blog/a-surge-of-newsletter-signups&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;#rss #feeds #linksharing #qwibbit
    </content>
    <updated>2026-10-30T02:47:33Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqszn24423q7z7edmgny2qgjwscytjz22mxkuwwzsf4w05fn4j4pmygzypaf03ntqlkl3yyeurpefmkrh7zmae7ja2992n4zd7sdtkrlyz76xux504p</id>
    
      <title type="html">Fail the build when a translation goes stale A missing Dutch ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqszn24423q7z7edmgny2qgjwscytjz22mxkuwwzsf4w05fn4j4pmygzypaf03ntqlkl3yyeurpefmkrh7zmae7ja2992n4zd7sdtkrlyz76xux504p" />
    <content type="html">
      Fail the build when a translation goes stale&lt;br/&gt;&lt;br/&gt;A missing Dutch string should fail the build on the machine that introduced the English one. A catalog entry Xcode has marked stale should fail it too. So should a %d that survived in English and disappeared in French. I would rather see that in the build log than as a raw key, or a crash, on a phone in another language. And yes, this is another little gem from iOS app I work on at Dawn Technology.&lt;br/&gt;UI copy lives in string catalogs. A Settings bundle still uses .strings files, because Apple does not take a catalog there. English is the source. The sample below requires nl, de, and fr as well. Add any other locale you ship by putting it in projectLocales. The check runs on every local build and on Xcode Cloud, because it is a Run Script phase on the app target, not a step that exists only in CI.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://appforce1.net/blog/fail-the-build-when-a-translation-goes-stale&#34;&gt;https://appforce1.net/blog/fail-the-build-when-a-translation-goes-stale&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;#stale #english #dawntechnology #xcode #runscript #french #cloud&lt;br/&gt;&lt;br/&gt;#rss #feeds #linksharing #qwibbit
    </content>
    <updated>2026-10-18T03:31:44Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqs9txtvkdukjzqrpe07lh9zxd3kdaqwuzvjgxhj86wz4d5ayq37f2szypaf03ntqlkl3yyeurpefmkrh7zmae7ja2992n4zd7sdtkrlyz76x4lg5v5</id>
    
      <title type="html">Five and a half years of Being a Lead Software Developer I ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqs9txtvkdukjzqrpe07lh9zxd3kdaqwuzvjgxhj86wz4d5ayq37f2szypaf03ntqlkl3yyeurpefmkrh7zmae7ja2992n4zd7sdtkrlyz76x4lg5v5" />
    <content type="html">
      Five and a half years of Being a Lead Software Developer&lt;br/&gt;&lt;br/&gt;I published a new edition of Being a Lead Software Developer on 13 October 2026. The first edition went out on 18 March 2021. That is five and a half years of adding to the same book.&lt;br/&gt;It is still the book I wanted when a manager told me I was the lead. I was the senior developer on a team at an insurance company, and then the extra work showed up: planning, meetings, and fewer hours for code. I looked for something practical. I found a chapter here, a peer there, and a lot of &amp;#34;I guess you just lead.&amp;#34; So I wrote down what I was learning. Then I kept writing it down.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://appforce1.net/blog/lead-developer-2026&#34;&gt;https://appforce1.net/blog/lead-developer-2026&lt;/a&gt;
    </content>
    <updated>2026-10-16T02:54:52Z</updated>
  </entry>

</feed>