Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.helava.com/feed/atom/

  1. <?xml version="1.0" encoding="UTF-8"?><feed
  2. xmlns="http://www.w3.org/2005/Atom"
  3. xmlns:thr="http://purl.org/syndication/thread/1.0"
  4. xml:lang="en-US"
  5. >
  6. <title type="text">six seven six</title>
  7. <subtitle type="text">Assorted Nonsense</subtitle>
  8.  
  9. <updated>2024-04-27T03:33:49Z</updated>
  10.  
  11. <link rel="alternate" type="text/html" href="https://helava.com" />
  12. <id>https://helava.com/feed/atom/</id>
  13. <link rel="self" type="application/atom+xml" href="https://helava.com/feed/atom/" />
  14.  
  15. <generator uri="https://wordpress.org/" version="6.5.2">WordPress</generator>
  16. <entry>
  17. <author>
  18. <name>helava</name>
  19. <uri>https://helava.com</uri>
  20. </author>
  21.  
  22. <title type="html"><![CDATA[Friends Are Terrible Co-Founders]]></title>
  23. <link rel="alternate" type="text/html" href="https://helava.com/2024/04/26/friends-are-terrible-co-founders/" />
  24.  
  25. <id>https://helava.com/?p=3481</id>
  26. <updated>2024-04-27T03:33:49Z</updated>
  27. <published>2024-04-27T03:33:24Z</published>
  28. <category scheme="https://helava.com" term="Uncategorized" />
  29. <summary type="html"><![CDATA[With all the layoffs, there are going to be a lot of folks who decide that this is their chance to take a swing at being an #entrepreneur and forming a #startup. If that&#8217;s you, fantastic. Here&#8217;s the single most important piece of advice I can give you: When you look for a #cofounder (and &#8230;]]></summary>
  30.  
  31. <content type="html" xml:base="https://helava.com/2024/04/26/friends-are-terrible-co-founders/"><![CDATA[
  32. <p>With all the layoffs, there are going to be a lot of folks who decide that this is their chance to take a swing at being an #entrepreneur and forming a #startup. If that&#8217;s you, fantastic. Here&#8217;s the single most important piece of advice I can give you:<br><br>When you look for a #cofounder (and you should), you want to find someone whose skills *complement* yours that you HAVE WORKED WITH in STRESSFUL SITUATIONS before.<br><br>It&#8217;s tempting to start a company with people you like. I get it. But here&#8217;s the catch: if you haven&#8217;t worked with your friend &amp; potential co-founder before, you don&#8217;t actually know what they&#8217;re like when stuff goes crazy at work. And in startups, things will be crazy all the time.<br><br>I founded a company with someone I&#8217;d lived with for a few years before. I knew them as someone who was smart, considerate, gentle, empathic, and reliable. What I discovered was instead that they were self-centered, egotistic, a terrible, borderline abusive manager, and so catastrophically flaky they any time something exploded and got genuinely difficult, the only thing I could rely on them for was to not be there when we should have been working on things together.<br><br>Starting a company with someone isn&#8217;t like being friends. It&#8217;s like being the ne plus ultra of coworkers &#8211; a comparison I like a lot more than the common &#8220;it&#8217;s like being married&#8221;. It&#8217;s not like being married. It&#8217;s like being tied together hanging off a bridge with anvils around both of your ankles. You need to work together under intense and constant pressure or you&#8217;re both screwed.<br><br>So look around. That person who was there with you when you had an impossible deadline to meet? The one who you always turn to when you have problems? The quiet person that folks often overlook who does all the actual hard shit? These are the kinds of people you want to be thinking about, not the office entertainer/fun person that everyone thinks is hilarious.<br><br>Your co-founders should come from the strongest, most effective of your work relationships. Most startups fail. And they fail for all kinds of reasons. But the most common reason I&#8217;ve seen is that co-founder relationships fall apart. Friends become bitter enemies. It&#8217;s happened to me, and it&#8217;s happened to a lot of people I know. The co-founder relationships that are most likely to succeed are the ones forged under the shared pressure of having worked together in difficult circumstances.</p>
  33. ]]></content>
  34. <link rel="replies" type="text/html" href="https://helava.com/2024/04/26/friends-are-terrible-co-founders/#comments" thr:count="0" />
  35. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/04/26/friends-are-terrible-co-founders/feed/atom/" thr:count="0" />
  36. <thr:total>0</thr:total>
  37. </entry>
  38. <entry>
  39. <author>
  40. <name>helava</name>
  41. <uri>https://helava.com</uri>
  42. </author>
  43.  
  44. <title type="html"><![CDATA[One Great Idea, Steal Everything Else]]></title>
  45. <link rel="alternate" type="text/html" href="https://helava.com/2024/04/26/one-great-idea-steal-everything-else/" />
  46.  
  47. <id>https://helava.com/?p=3477</id>
  48. <updated>2024-04-27T03:33:11Z</updated>
  49. <published>2024-04-27T03:33:11Z</published>
  50. <category scheme="https://helava.com" term="Uncategorized" />
  51. <summary type="html"><![CDATA[There&#8217;s gonna be a lot of #startups in the wake of all the recent #layoffs. The most valuable advice I can give is around really understanding that people want what you are trying to build. And that&#8217;s a long, complicated discussion. The tl;dr there is you need to validate with real users that there is &#8230;]]></summary>
  52.  
  53. <content type="html" xml:base="https://helava.com/2024/04/26/one-great-idea-steal-everything-else/"><![CDATA[There&#8217;s gonna be a lot of #startups in the wake of all the recent #layoffs. The most valuable advice I can give is around really understanding that people want what you are trying to build. And that&#8217;s a long, complicated discussion. The tl;dr there is you need to validate with real users that there is actual demand for your product. Nothing else you do is more important than that, and everything you do is meaningless if you get that wrong.<br /><br />BUT. That&#8217;s a long discussion. Here&#8217;s a shorter one, and it&#8217;s the 2nd-most valuable piece of advice I have.<br /><br />Keep your product focused around one simple idea, and rip off everything else you can directly from other products.<br /><br />Yeah, I know &#8211; this sounds like I&#8217;m telling you to just blatantly copy everything other than your core idea from other folks.<br /><br />I am.<br /><br />No, I&#8217;m not telling you to *ship* something that&#8217;s ripped off entirely from other sources.<br /><br />Here&#8217;s the thing &#8211; you want to minimize the number of variables that you&#8217;re working with. Everything you don&#8217;t know explodes your risk exponentially. So there&#8217;s some part of your product that you can&#8217;t know &#8211; that&#8217;s the brand new thing you&#8217;re doing. Almost everything else you can likely crib from something that&#8217;s already established. And rather than innovate on it, I&#8217;m telling you to just ape it directly.<br /><br />Why?<br /><br />Because it minimizes risk. Let&#8217;s say you want to have a character in a side-scrolling platformer jump. Make them jump exactly like Mario. Same height, same timing, same forward distance, same air control, etc. etc. etc. Because that becomes 20 variables that you don&#8217;t need to worry about, and more importantly, you know it will feel right to your audience, because it is familiar.<br /><br />Now, as you focus on your one really new idea, you&#8217;ll find that it naturally bleeds out into other things. Maybe your &#8220;new idea&#8221; is to have a game where a character can dash. That dash will affect the jump. When can it happen? How far does it travel? How does it change animations? Level layouts?<br /><br />Because it interacts with jumping, it will change jumping. And as you tweak the new thing, you&#8217;ll find that you will likely also tweak the &#8220;stolen&#8221; bits. And you&#8217;ll do that enough that the starting point (Mario) will be totally unrecognizable by the end.<br /><br />But if you had to tweak all the elements of dashing with all the elements of jumping and it was all unknown, you&#8217;d have a problem with hundreds of variables, none of which were set in stone when you started. This huge complexity with no constraints leads to chaos.<br /><br />So start by eliminating all the variables you can by taking things that already exist and doing exactly that. Then as your new stuff comes online, experiment and evolve all the systems that you ripped off, and they&#8217;ll evolve into something new, but starting from a point where the results are known, and feel good to the end user.<br /><br />By the end, you&#8217;ll have spent all your time focusing on the new thing, and by limiting complexity, you&#8217;ll actually be able to finish &#038; ship.]]></content>
  54. <link rel="replies" type="text/html" href="https://helava.com/2024/04/26/one-great-idea-steal-everything-else/#comments" thr:count="0" />
  55. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/04/26/one-great-idea-steal-everything-else/feed/atom/" thr:count="0" />
  56. <thr:total>0</thr:total>
  57. </entry>
  58. <entry>
  59. <author>
  60. <name>helava</name>
  61. <uri>https://helava.com</uri>
  62. </author>
  63.  
  64. <title type="html"><![CDATA[Arrival]]></title>
  65. <link rel="alternate" type="text/html" href="https://helava.com/2024/04/21/arrival/" />
  66.  
  67. <id>https://helava.com/?p=3478</id>
  68. <updated>2024-04-22T01:11:42Z</updated>
  69. <published>2024-04-22T01:11:42Z</published>
  70. <category scheme="https://helava.com" term="Uncategorized" />
  71. <summary type="html"><![CDATA[How it&#8217;s taken me this long to finally watch Arrival I&#8217;ll never know. I&#8217;m a huge fan of Ted Chiang&#8217;s writing, and Denis Villeneuve&#8217;s work (Dune 1&#38;2 + BR2049). I thought the movie was brilliant. Took a really neat story, and for me, many of the decisions they made improved things. Not that they&#8217;re necessarily &#8230;]]></summary>
  72.  
  73. <content type="html" xml:base="https://helava.com/2024/04/21/arrival/"><![CDATA[<p><img decoding="async" class="sFlh5c pT0Scc iPVvYb" src="https://play-lh.googleusercontent.com/DURxIJ66jaSy1Gl0FtjSugq9ffxphNUJ631mrLdcte8k68vACNg_U3Ijm4s64ZBbU34" alt="Arrival – Films sur Google Play" aria-hidden="false" /></p>
  74. <p>How it&#8217;s taken me this long to finally watch Arrival I&#8217;ll never know. I&#8217;m a huge fan of Ted Chiang&#8217;s writing, and Denis Villeneuve&#8217;s work (Dune 1&amp;2 + BR2049).</p>
  75. <p>I thought the movie was brilliant. Took a really neat story, and for me, many of the decisions they made improved things. Not that they&#8217;re necessarily better than the OG, just that they&#8217;re better <em>for the medium</em> than a more literal translation of the book. If you haven&#8217;t seen it, I highly recommend it. I don&#8217;t want to write much more just because I don&#8217;t want to spoil it &#8211; but man, the end (even though I recalled it from the story a while before the revelation) was just one of those things that sat with me for hours afterwards.</p>
  76. ]]></content>
  77. <link rel="replies" type="text/html" href="https://helava.com/2024/04/21/arrival/#comments" thr:count="0" />
  78. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/04/21/arrival/feed/atom/" thr:count="0" />
  79. <thr:total>0</thr:total>
  80. </entry>
  81. <entry>
  82. <author>
  83. <name>helava</name>
  84. <uri>https://helava.com</uri>
  85. </author>
  86.  
  87. <title type="html"><![CDATA[Pressure and Meta]]></title>
  88. <link rel="alternate" type="text/html" href="https://helava.com/2024/02/20/pressure-and-meta/" />
  89.  
  90. <id>https://helava.com/?p=3469</id>
  91. <updated>2024-02-21T04:34:02Z</updated>
  92. <published>2024-02-21T04:34:02Z</published>
  93. <category scheme="https://helava.com" term="Uncategorized" />
  94. <summary type="html"><![CDATA[One of the things I find incredibly challenging as a parent is knowing how hard to “push” my kids. As the child of a fairly traditional “Asian Mom”, who was under immense pressure throughout my childhood to “excel”, I hated everything about it. I hated music, I hated most sports, I hated school. It wasn’t &#8230;]]></summary>
  95.  
  96. <content type="html" xml:base="https://helava.com/2024/02/20/pressure-and-meta/"><![CDATA[<p>One of the things I find incredibly challenging as a parent is knowing how hard to “push” my kids. As the child of a fairly traditional “Asian Mom”, who was under immense pressure throughout my childhood to “excel”, I hated everything about it. I hated music, I hated most sports, I hated school. It wasn’t until I was in my mid-thirties when I realized that I didn’t hate all those things, I hated the pressure I felt, and the constant criticism and pummeling of my self-esteem that it all meant.</p>
  97. <p>So with the kids, this is something I genuinely struggle with.</p>
  98. <p>This morning, something came up, and I responded in a way that felt more like “my parents” and not “what I want to do”, and I struggled with that internally for a while, and then just talked to my older son specifically about *why* I responded the way I did, the specific pressure and difficulty of trying to walk this fine line of “push so that you butt up against your comfort zone and learn new things,” and “let you discover things that you love and build skill on your own”.</p>
  99. <p>It was one of the first times that I’ve had this “meta” conversation about parenting with J &#8211; that it wasn’t the conversation about the actual thing, but the conversation about the pressure I felt as a parent and how difficult it was to navigate. And then we talked about what *he* wanted, and what his motivations were, and we reached a genuinely great conclusion.</p>
  100. <p>And it reminded me of a time when our game, Fleck, was really struggling to stand on its own. At the time, I didn’t know whether to put on a brave face and power through it with positivity, or whether to have the frank discussion about the state of the game &amp; the business side of things. The same kind of “meta” conversation about the game with the team.</p>
  101. <p>I was shocked. People *wanted* that insight &#8211; they wanted to contribute at that level, and they responded incredibly well to an honest, open talk about vulnerability, the struggles we faced, etc. Everyone *knew* things weren’t peachy-keen, but I’d been told that the leader needs to be positive, help folks get through obstacles, etc.</p>
  102. <p>I think the lesson I take from this is that in general, folks don’t mind the meta conversation. You don’t have to “play the game” and hope to get the right results with all the mechanics hidden away behind the scenes. If folks know how the machine works, you can all play the game together.</p>
  103. ]]></content>
  104. <link rel="replies" type="text/html" href="https://helava.com/2024/02/20/pressure-and-meta/#comments" thr:count="0" />
  105. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/02/20/pressure-and-meta/feed/atom/" thr:count="0" />
  106. <thr:total>0</thr:total>
  107. </entry>
  108. <entry>
  109. <author>
  110. <name>helava</name>
  111. <uri>https://helava.com</uri>
  112. </author>
  113.  
  114. <title type="html"><![CDATA[Apple Vision Pro]]></title>
  115. <link rel="alternate" type="text/html" href="https://helava.com/2024/02/20/apple-vision-pro/" />
  116.  
  117. <id>https://helava.com/?p=3467</id>
  118. <updated>2024-02-21T01:58:44Z</updated>
  119. <published>2024-02-21T01:58:44Z</published>
  120. <category scheme="https://helava.com" term="Uncategorized" />
  121. <summary type="html"><![CDATA[The Apple Vision Pro is a weird duck. As a piece of technology, it’s extraordinary &#8211; the pass through is great, the hand/pinch gesture sensitivity is great, the hardware feels nice and is (mostly) comfortable. The big thing for me is the forward-heaviness of it, which is almost instantly mitigated by just tucking the battery into &#8230;]]></summary>
  122.  
  123. <content type="html" xml:base="https://helava.com/2024/02/20/apple-vision-pro/"><![CDATA[<p>The Apple Vision Pro is a weird duck. As a piece of technology, it’s extraordinary<b> </b>&#8211; the pass through is great, the hand/pinch gesture sensitivity is great, the hardware feels nice and is (mostly) comfortable. The big thing for me is the forward-heaviness of it, which is almost instantly mitigated by just tucking the battery into the rear strap. I get that they wanted strap options, and that they want you to comfortably rest your head while using the headset, but a well-designed counterweight strap would make this a LOT more comfortable with almost no downside. I don’t get why Apple didn’t learn this lesson. It’s not weight that matters in a VR/AR headset &#8211; it’s where the center of balance is. If you put the weight directly over the neck, it can be much heavier, and still totally comfortable. The big problem is forward-heavy headsets exert pressure on your cheeks that eventually becomes intolerable. But I can hold that same weight easily on the top of my head for hours. So that’s weird.</p>
  124. <p>I’m struggling a bit to figure out what this is for, to be honest. I’m trying it with a keyboard and trackpad to use as a general computing device (writing this post, even) &#8211; and for that, it’s nice. But with limited battery life, and as delicate as it is, it can’t compare with a laptop. As a home-use device, it’s also weird &#8211; at home there’s usually people around, and “shutting them out” with the headset feels awkward and isolating &#8211; even with the pass through. The eyes on the outside of the device are so utterly bizarre in practice I’m kind of baffled that they released it this way. Cutting the external display would have saved weight and allowed the device to be quite a bit thinner, and that definitely would have been a trade off I’d have made. Vs. how the eyes are *supposed* to look, maybe it’s better &#8211; but as it is currently, it’s almost zero value.</p>
  125. <p>I think the biggest thing for me is this emphasizes how important robust object recognition and tracking is for a device like this. I need to be able to “attach” virtual objects to real objects and have them move in total lockstep. Apple tries to do this a bit with the Magic Keyboard and a little virtual widget they attach to it, and it’s neat to see the widget track the keyboard in space, but there’s a significant delay, and the object locking is quite … imprecise. That said, it’s a hell of a lot better than anything else trying to do the same thing I’ve seen.</p>
  126. <p>There’s also some weirdness to VisionOS, and I’m sure this kind of thing will be improved as time goes on &#8211; but I find that I want apps to “snap to object/surface” by default. I don’t want random windows floating in midair most of the time &#8211; I want them to snap to cabinet doors, or wall surfaces, or to lock to my (physical) desk top. Being able to “pull” windows off of physical objects would be necessary, and being able to have them float in space is obviously a must &#8211; but by *default*, I want windows to snap to objects and be tied to physical things.</p>
  127. <p>Still &#8211; the pass through makes “doing things” in the Vision Pro WAY more comfortable than in VR, or even with the Quest 2’s low-fi B&amp;W pass through. I can look at my phone, or a clock, or see someone approach &#8211; and all those things make AVP feel way less isolating than any headset I’ve tried before. But there are a LOT of straightforward improvements that are almost certain to come, and the gen-3 version of this thing will be incredible. I’m still struggling to think of something to make for AVP &#8211; for the most part, my personal lack of understanding about how object-recognition might work on a platform like this hamstrings my understanding of what’s possible. I should probably dive into the SDK’s documentation or something. But the other big thing is, “How are users going to use this platform?” And that’s something I still don’t really have an answer for.</p>
  128. <p>This is definitely an interesting platform. It’s incredible tech. It’s just that I can’t easily imagine when I would naturally put this thing on and dedicate time to be in AVP, vs. using a laptop or iPad, and having unfettered access to reality. I think it’s clear that that’s the end goal &#8211; that this pass through solution is a placeholder. But this is an interesting start, and it’s nice to see what feels like a significantly different take, with a very different focus, on AR/VR that’s not Meta. If that’s literally all the AVP accomplishes, it’ll still be worth it.</p>
  129. ]]></content>
  130. <link rel="replies" type="text/html" href="https://helava.com/2024/02/20/apple-vision-pro/#comments" thr:count="0" />
  131. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/02/20/apple-vision-pro/feed/atom/" thr:count="0" />
  132. <thr:total>0</thr:total>
  133. </entry>
  134. <entry>
  135. <author>
  136. <name>helava</name>
  137. <uri>https://helava.com</uri>
  138. </author>
  139.  
  140. <title type="html"><![CDATA[Some Recent Photos]]></title>
  141. <link rel="alternate" type="text/html" href="https://helava.com/2024/02/11/some-recent-photos/" />
  142.  
  143. <id>https://helava.com/?p=3455</id>
  144. <updated>2024-02-11T23:12:55Z</updated>
  145. <published>2024-02-11T23:12:04Z</published>
  146. <category scheme="https://helava.com" term="Uncategorized" />
  147. <summary type="html"><![CDATA[Some photos of a recent trip to Oahu.]]></summary>
  148.  
  149. <content type="html" xml:base="https://helava.com/2024/02/11/some-recent-photos/"><![CDATA[<p>Some photos of a recent trip to Oahu.</p>
  150. <p><a href="https://helava.com/wp-content/uploads/2024/02/IMG_3375-scaled.jpeg"><img fetchpriority="high" decoding="async" class="alignnone size-medium wp-image-3461" src="https://helava.com/wp-content/uploads/2024/02/IMG_3375-300x225.jpeg" alt="" width="300" height="225" srcset="https://helava.com/wp-content/uploads/2024/02/IMG_3375-300x225.jpeg 300w, https://helava.com/wp-content/uploads/2024/02/IMG_3375-1024x768.jpeg 1024w, https://helava.com/wp-content/uploads/2024/02/IMG_3375-768x576.jpeg 768w, https://helava.com/wp-content/uploads/2024/02/IMG_3375-1536x1152.jpeg 1536w, https://helava.com/wp-content/uploads/2024/02/IMG_3375-2048x1536.jpeg 2048w" sizes="(max-width: 300px) 100vw, 300px" /></a></p>
  151. <p><a href="https://helava.com/wp-content/uploads/2024/02/IMG_1782-scaled.jpeg"><img decoding="async" class="alignnone size-medium wp-image-3460" src="https://helava.com/wp-content/uploads/2024/02/IMG_1782-300x225.jpeg" alt="" width="300" height="225" srcset="https://helava.com/wp-content/uploads/2024/02/IMG_1782-300x225.jpeg 300w, https://helava.com/wp-content/uploads/2024/02/IMG_1782-1024x768.jpeg 1024w, https://helava.com/wp-content/uploads/2024/02/IMG_1782-768x576.jpeg 768w, https://helava.com/wp-content/uploads/2024/02/IMG_1782-1536x1152.jpeg 1536w, https://helava.com/wp-content/uploads/2024/02/IMG_1782-2048x1536.jpeg 2048w" sizes="(max-width: 300px) 100vw, 300px" /></a></p>
  152. <p><a href="https://helava.com/wp-content/uploads/2024/02/IMG_1764-scaled.jpeg"><img decoding="async" class="alignnone size-medium wp-image-3459" src="https://helava.com/wp-content/uploads/2024/02/IMG_1764-300x225.jpeg" alt="" width="300" height="225" srcset="https://helava.com/wp-content/uploads/2024/02/IMG_1764-300x225.jpeg 300w, https://helava.com/wp-content/uploads/2024/02/IMG_1764-1024x768.jpeg 1024w, https://helava.com/wp-content/uploads/2024/02/IMG_1764-768x576.jpeg 768w, https://helava.com/wp-content/uploads/2024/02/IMG_1764-1536x1152.jpeg 1536w, https://helava.com/wp-content/uploads/2024/02/IMG_1764-2048x1536.jpeg 2048w" sizes="(max-width: 300px) 100vw, 300px" /></a></p>
  153. <p><a href="https://helava.com/wp-content/uploads/2024/02/IMG_3338-scaled.jpeg"><img loading="lazy" decoding="async" class="alignnone size-medium wp-image-3458" src="https://helava.com/wp-content/uploads/2024/02/IMG_3338-300x225.jpeg" alt="" width="300" height="225" srcset="https://helava.com/wp-content/uploads/2024/02/IMG_3338-300x225.jpeg 300w, https://helava.com/wp-content/uploads/2024/02/IMG_3338-1024x768.jpeg 1024w, https://helava.com/wp-content/uploads/2024/02/IMG_3338-768x576.jpeg 768w, https://helava.com/wp-content/uploads/2024/02/IMG_3338-1536x1152.jpeg 1536w, https://helava.com/wp-content/uploads/2024/02/IMG_3338-2048x1536.jpeg 2048w" sizes="(max-width: 300px) 100vw, 300px" /></a></p>
  154. <p><a href="https://helava.com/wp-content/uploads/2024/02/GOPR0334-scaled.jpg"><img loading="lazy" decoding="async" class="size-medium wp-image-3457" src="https://helava.com/wp-content/uploads/2024/02/GOPR0334-300x225.jpg" alt="" width="300" height="225" srcset="https://helava.com/wp-content/uploads/2024/02/GOPR0334-300x225.jpg 300w, https://helava.com/wp-content/uploads/2024/02/GOPR0334-1024x768.jpg 1024w, https://helava.com/wp-content/uploads/2024/02/GOPR0334-768x576.jpg 768w, https://helava.com/wp-content/uploads/2024/02/GOPR0334-1536x1152.jpg 1536w, https://helava.com/wp-content/uploads/2024/02/GOPR0334-2048x1536.jpg 2048w" sizes="(max-width: 300px) 100vw, 300px" /></a></p>
  155. ]]></content>
  156. <link rel="replies" type="text/html" href="https://helava.com/2024/02/11/some-recent-photos/#comments" thr:count="0" />
  157. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/02/11/some-recent-photos/feed/atom/" thr:count="0" />
  158. <thr:total>0</thr:total>
  159. </entry>
  160. <entry>
  161. <author>
  162. <name>helava</name>
  163. <uri>https://helava.com</uri>
  164. </author>
  165.  
  166. <title type="html"><![CDATA[RIP, Laralyn]]></title>
  167. <link rel="alternate" type="text/html" href="https://helava.com/2024/02/11/rip-laralyn/" />
  168.  
  169. <id>https://helava.com/?p=3453</id>
  170. <updated>2024-02-11T23:06:18Z</updated>
  171. <published>2024-02-11T23:06:18Z</published>
  172. <category scheme="https://helava.com" term="Uncategorized" />
  173. <summary type="html"><![CDATA[I recently read that Laralyn McWilliams passed away. I only met her online &#8211; we had a small number of chats something on the order of a decade ago, and I’d loosely followed her on various channels since, and … dammit. Go poke her profile page and check out her history. She was an absolute &#8230;]]></summary>
  174.  
  175. <content type="html" xml:base="https://helava.com/2024/02/11/rip-laralyn/"><![CDATA[<p>I recently read that <a href="https://www.linkedin.com/in/ACoAAAAFM2IB-oovrzKc2_E3dXVoCr_n-4sqdmI" data-attribute-index="0" data-entity-type="MINI_PROFILE">Laralyn McWilliams</a> passed away. I only met her online &#8211; we had a small number of chats something on the order of a decade ago, and I’d loosely followed her on various channels since, and … dammit.</p>
  176. <p>Go poke her profile page and check out her history. She was an absolute titan of the game industry, and among many other things that would define anyone’s career, she led the design of Full Spectrum Warrior, which was such a discombobulatingly novel take on something that looked like it should be a cliche that I’m still genuinely dazzled that they pulled it off.</p>
  177. <p>But the thing I wish I could have expressed my gratitude toward her for was her kindness. The times we chatted, she’d reached out because she saw me going through a hard time. There was absolutely no reason she should have cared, but she did.</p>
  178. <p>Every single thing I ever saw from her in the ensuing decade, whether it was about teaching or talking about game design, about her constant and unrelenting health challenges &#8211; the level of positivity and kindness and thoughtfulness she put into every exchange she ever had with *anyone I ever saw* was … It was astonishing. And it wasn’t some facade of perfection. You could see the struggle. And the optimism. And the bravery.</p>
  179. <p>And dammit &#8211; it’s so cliche to talk about folks having health challenges as being brave. But facing down terrible odds, and wanting to continue to help others, to continue to create things, and in the face of everything, never giving in to nihilism and cynicism and self-absorption? If that’s not brave, I don’t know what bravery is.</p>
  180. <p>She’s always going to be someone whose outlook and resilience and positivity I will strive to emulate. I’m gutted for her friends and family, and for the game industry as a whole.</p>
  181. <p>RIP, and thank you.</p>
  182. ]]></content>
  183. <link rel="replies" type="text/html" href="https://helava.com/2024/02/11/rip-laralyn/#comments" thr:count="0" />
  184. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/02/11/rip-laralyn/feed/atom/" thr:count="0" />
  185. <thr:total>0</thr:total>
  186. </entry>
  187. <entry>
  188. <author>
  189. <name>helava</name>
  190. <uri>https://helava.com</uri>
  191. </author>
  192.  
  193. <title type="html"><![CDATA[A Few Books]]></title>
  194. <link rel="alternate" type="text/html" href="https://helava.com/2024/02/11/a-few-books/" />
  195.  
  196. <id>https://helava.com/?p=3451</id>
  197. <updated>2024-02-11T23:05:34Z</updated>
  198. <published>2024-02-11T23:05:34Z</published>
  199. <category scheme="https://helava.com" term="Uncategorized" />
  200. <summary type="html"><![CDATA[A few books I’ve been reading: Eric Nehrlich’s You Have a Choice &#8211; I’ve been reading this since years before he started writing it, in his various blog posts, newsletters, and talking with him in person. We’ve been friends since my college days, and over the last 20 years, he’s grown tremendously, in every way, &#8230;]]></summary>
  201.  
  202. <content type="html" xml:base="https://helava.com/2024/02/11/a-few-books/"><![CDATA[<p>A few books I’ve been reading:</p>
  203. <p><a href="https://www.linkedin.com/in/ACoAAAACwycBqYEQ9Aj6Qb2d1SJct1DAhdNaBCc" data-attribute-index="0" data-entity-type="MINI_PROFILE">Eric Nehrlich</a>’s You Have a Choice &#8211; I’ve been reading this since years before he started writing it, in his various blog posts, newsletters, and talking with him in person. We’ve been friends since my college days, and over the last 20 years, he’s grown tremendously, in every way, as a person. Professionally, personally &#8211; but the biggest thing is that he took concrete steps to create the life he wanted, and the biggest, hardest thing he had to do (IMO) was realize he could define his own direction. In his book, he talks about that process, and he’s helped dozens (hundreds?) of people take similar steps. The book isn’t just refined because he’s done it himself. It’s because he’s also taken these lessons and already applied them to the people he coaches. So the book is great. But it’s worth putting in there that *he* is also great. His ideas are deeply explored and considered, are based on a wealth and breadth of experience, and his desire to help other people is genuine. If you’re finding yourself “succeeding”, but still kinda miserable or frazzled, this is *the* book for you.</p>
  204. <p><a href="https://www.linkedin.com/in/ACoAAAARwbMBjBe_u396eedaIt4Jr1s4ywnhJd8" data-attribute-index="2" data-entity-type="MINI_PROFILE">Wagner James Au</a>’s Making a Metavese That Matters &#8211; for all the garbage hype around Meta’s foray in the metaverse (and the absurd investor FOMO whiplash freakout and faceplant), this is a book written by someone that *cares* deeply about the metaverse, and has for longer than most of the people claiming to be “metaverse experts” have been aware of its existence. His writing is personal, and interesting and even if you’ve been metaverse-aware since Snow Crash and Second Life, this is a more definitive chronicle of its development than I’ve seen anywhere else. Like Eric’s book above, what drew me to this was its authenticity and depth. In a field that’s full of snake-oil salesmen, this is a book with real knowledge and wisdom.</p>
  205. <p><a href="https://www.linkedin.com/in/ACoAAAA3kpkBEk6a0Yv5Iyz0iAOlLogiayc5eoQ" data-attribute-index="4" data-entity-type="MINI_PROFILE">Kim Nordstrom</a>’s dn UMOP dn &#8211; Oh, wait. it’s Up Down Up. I met Kim through <a href="https://www.linkedin.com/in/ACoAAAAFdisBW0NVj3Y9hcivkGQH5_zIbIMIqQ0" data-attribute-index="6" data-entity-type="MINI_PROFILE">Paul Tozour</a> (whose book The Four Swords is worth a read if you’re interested in diving into what seems like a satirical exaggeration/parody of the game industry’s worst tendencies, but to someone who’s seen it all, reads more like an account of any random Tuesday) a while back, and I had a chance to read an early copy of the book. Been going through the print version as well, and it’s a great read. He interviews a *gazillion* folks who’ve built &amp; led successful (and not successful) game companies, and consolidates their collective experience into a book that I wish was mandatory reading for folks starting game studios. It’s obviously not a formula for success, but the point of it is all these interviews land on a number of recurring points, and seeing the echoes of the same sounds in all the stories begins to show you the shape of what it’s like to run a successful team. Having been through that wringer, it’s a book I wish I had before I’d started out, and I hope it’ll save new founders from a lot of pain.</p>
  206. ]]></content>
  207. <link rel="replies" type="text/html" href="https://helava.com/2024/02/11/a-few-books/#comments" thr:count="0" />
  208. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/02/11/a-few-books/feed/atom/" thr:count="0" />
  209. <thr:total>0</thr:total>
  210. </entry>
  211. <entry>
  212. <author>
  213. <name>helava</name>
  214. <uri>https://helava.com</uri>
  215. </author>
  216.  
  217. <title type="html"><![CDATA[The Obvious Solutions]]></title>
  218. <link rel="alternate" type="text/html" href="https://helava.com/2024/02/11/3448/" />
  219.  
  220. <id>https://helava.com/?p=3448</id>
  221. <updated>2024-02-11T22:51:04Z</updated>
  222. <published>2024-02-11T22:50:07Z</published>
  223. <category scheme="https://helava.com" term="Uncategorized" />
  224. <summary type="html"><![CDATA[In sixth grade, I watched a show on PBS about MIT’s 2.007 robot competition, and I knew that was what I was going to try do in college. I wanted the challenge of solving some problem, building a machine to do it, and compete using both my wits and my engineering skill. And in 1997, &#8230;]]></summary>
  225.  
  226. <content type="html" xml:base="https://helava.com/2024/02/11/3448/"><![CDATA[<p>In sixth grade, I watched a show on PBS about MIT’s 2.007 robot competition, and I knew that was what I was going to try do in college.</p>
  227. <p>I wanted the challenge of solving some problem, building a machine to do it, and compete using both my wits and my engineering skill. And in 1997, I got to take the class and live out a childhood dream.</p>
  228. <p>I love building things with my hands. I don’t do it as often as I’d like these days, but I find that that’s when I feel like my mind and body are fully engaged. Part of the challenge is figuring out the rules &#8211; what to build, and then executing in real time during the competition.</p>
  229. <p>The year I took the class, the design of the competition… was terrible.</p>
  230. <p>The goal was to get balls into your bin. They fell from a “waterfall” mechanism that triggered a few moments after the competition. There was a ramp from the starting position near the waterfall and your bin down to a central arena where the balls would land.</p>
  231. <p>The problem with the rules is that there was one very clear, very obvious solution. An arm that would extend and redirect the balls directly into your bin was the clear answer, and the winner would simply be the person who built the fastest, most robust arm that couldn’t be deflected out of position.</p>
  232. <p>That was it. The best strategy by far required zero human interaction &#8211; in fact, human interaction would make it *worse*. If you wanted to build the most robust arm, that’d take all your material and space. You’d build the strongest, fastest arm you could, and hope that you could beat everyone else to the punch. If someone built a stronger, faster arm, you were screwed, but here’s the thing &#8211; if you built *literally anything else* you were even more screwed.</p>
  233. <p>I didn’t build an arm.</p>
  234. <p>I decided that even though the rules had a clear solution, this isn’t what I wanted out of the competition. I wanted to build an RC robot that relied on my control, that gave me options and flexibility, where I could construct a strategy on the fly and do interesting things. So I built a little bulldozer thing with skids and wheels that could Hoover up balls into a front cage, dump them into a hopper in the back, and then the hopper could extend up from the central arena and dump balls into the bin. I could theoretically use the extending hopper to also block anyone else from dumping balls into the bin. It was really maneuverable and quite fast. I practiced any strategy I could think of over and over again.</p>
  235. <p>But I knew that if I went up against even a marginally competent extending arm, I’d lose.</p>
  236. <p>I don’t have strong memories of the competition or its results. I think the winner in the end was an extending arm. As for me, despite hours and hours of practice, the thing that undid me in the end was a small screw protruded from the bottom of the machine, and in what felt like one-in-a-zillion odds, when I turned off the ramp into the central arena one round, that screw caught on the ramp and “beached” the machine.</p>
  237. <p>I was proud of that machine, though. Aside from the protruding screw, a mistake that was easily fixable with iteration, it was a fairly robust, well-built, flexible machine. It did what I’d hoped it would do, and I got to play the competition the way I wanted to.</p>
  238. <p>And I think that there are really strong parallels to my professional career.</p>
  239. <p>When I look at mobile gaming, there are lots of people who “build the arm”. They look at the current winning strategy, and think they can build the best arm.</p>
  240. <p>I *hate* building arms. I’ve never done it. I’ve never believed that the next hit looks exactly like an iteration of the last hit. I’ve never wanted to work on solved problems. My focus has always been on making things that are flexible, and “broad” re: strategic options, and have attempted to wield that breadth in interesting ways.</p>
  241. <p>And it’s weird &#8211; until this afternoon, I never realized *how* strong the parallel was between my experience with 2.007 and the rest of my career.</p>
  242. <p>But I think that “strategic weirdness” is why I love working with a broad range of multidisciplinary people. It’s why I love working on new things. It’s why I hate the kind of “iterate until optimal” business model of highly derivative games.</p>
  243. <p>Back at a job long ago, we made a bingo game, under some amount of pressure from the company that’d acquired our team. The obvious thing they wanted us to do was ape the leading bingo game, and they’d market it aggressively and hope to do something. I kept kicking the can down the road, until one day we figured out how to do something interesting with powerups in bingo, where teams could collectively bring powerups to the game, and trigger them in fun, synergistic ways.</p>
  244. <p>It was a system that created a huge potential for interesting gameplay, because it wasn’t just about *your* powerups and what they’d do for your cards, it was what you could do for the *other* players on your team. It made bingo a wild cooperative team game, and the results were delightful.</p>
  245. <p>The game didn’t succeed in the end. I believe it still could have, given the “possibility space” of the system we’d created. The company basically said, “Welp, dislodging players from (whatever game was winning the bingo category at the time) is too expensive.” And while I think we’d have gotten to a point where we’d have a better game and those costs would have come down, they decided to pull the plug (there’s a lot I’d say here about judgment and necessary courage, but…)</p>
  246. <p>But to me, the point is that fighting the winning bingo game with a clone of the winning bingo game was a sure fire recipe for disaster. It’d have been trying to “build a better arm” when the arm you’re fighting has 100x your budget, 100x your size &amp; weight, and is *already deployed*.</p>
  247. <p>We didn’t have an option to build a better arm. We could only build something new. And I think there are some situations and companies that are foundationally only about “building arms”. They’re not for me, and never will be.</p>
  248. <p>Work is many things, and depending on circumstance, you can’t always think this way. What I have is a luxury. But work, to me, is about the joy of creation, and building things with other people. The most joy comes not from building arms, but from building new weird shit with strategic breadth and the possibility of wielding that breadth in shocking and interesting ways.</p>
  249. <p>And it’s weird that I’d already known that back in 1997 when building a robot for a class.</p>
  250. <p>&nbsp;</p>
  251. ]]></content>
  252. <link rel="replies" type="text/html" href="https://helava.com/2024/02/11/3448/#comments" thr:count="0" />
  253. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/02/11/3448/feed/atom/" thr:count="0" />
  254. <thr:total>0</thr:total>
  255. </entry>
  256. <entry>
  257. <author>
  258. <name>helava</name>
  259. <uri>https://helava.com</uri>
  260. </author>
  261.  
  262. <title type="html"><![CDATA[Too Much is Too Much]]></title>
  263. <link rel="alternate" type="text/html" href="https://helava.com/2024/01/24/too-much-is-too-much/" />
  264.  
  265. <id>https://helava.com/?p=3445</id>
  266. <updated>2024-01-25T00:04:32Z</updated>
  267. <published>2024-01-25T00:04:31Z</published>
  268. <category scheme="https://helava.com" term="Uncategorized" />
  269. <summary type="html"><![CDATA[I have too many interests. I want to spend time: I mean, that’s just the tip of the iceberg. And I know that everyone’s got a huge variety of hobbies. And one thing that’s different, is that more than most people, I have time. I don’t take that for granted at all. But what it &#8230;]]></summary>
  270.  
  271. <content type="html" xml:base="https://helava.com/2024/01/24/too-much-is-too-much/"><![CDATA[
  272. <p>I have too many interests.</p>
  273.  
  274.  
  275.  
  276. <p>I want to spend time:</p>
  277.  
  278.  
  279.  
  280. <ul>
  281. <li>Making a game</li>
  282.  
  283.  
  284.  
  285. <li>Simracing</li>
  286.  
  287.  
  288.  
  289. <li>Making music</li>
  290.  
  291.  
  292.  
  293. <li>Spending time with the kids</li>
  294.  
  295.  
  296.  
  297. <li>Boardgaming</li>
  298.  
  299.  
  300.  
  301. <li>Videogaming</li>
  302.  
  303.  
  304.  
  305. <li>Reading comic books &amp; Sci-Fi</li>
  306.  
  307.  
  308.  
  309. <li>Wingfoiling</li>
  310.  
  311.  
  312.  
  313. <li>Biking</li>
  314.  
  315.  
  316.  
  317. <li>Paddleboarding</li>
  318.  
  319.  
  320.  
  321. <li>Archerying</li>
  322.  
  323.  
  324.  
  325. <li>Drawing</li>
  326.  
  327.  
  328.  
  329. <li>Playing old games I never got around to on what are now “retro” platforms</li>
  330.  
  331.  
  332.  
  333. <li>Cooking</li>
  334.  
  335.  
  336.  
  337. <li>Organizing and fixing stuff up around the house</li>
  338.  
  339.  
  340.  
  341. <li>Making pottery</li>
  342.  
  343.  
  344.  
  345. <li>Swimming</li>
  346.  
  347.  
  348.  
  349. <li>Writing (Resume stuff, novel, leadership/game design book)</li>
  350.  
  351.  
  352.  
  353. <li>Blacksmithing</li>
  354.  
  355.  
  356.  
  357. <li>Learning arbitrary new stuff</li>
  358.  
  359.  
  360.  
  361. <li>Getting in better shape</li>
  362. </ul>
  363.  
  364.  
  365.  
  366. <p>I mean, that’s just the tip of the iceberg. And I know that everyone’s got a huge variety of hobbies. And one thing that’s different, is that more than most people, I have <em>time</em>.</p>
  367.  
  368.  
  369.  
  370. <p>I don’t take that for granted at all. But what it causes is this kind of persistent analysis paralysis and inability to focus on one thing and go <em>deep</em> to the degree that’s necessary for me to improve at anything. And sometimes, worse, that analysis paralysis prevents me from doing ANY of these things out of a weird kind of FOMO that I might pick something and then have an opportunity to do something better.</p>
  371.  
  372.  
  373.  
  374. <p>And I think that served me alright when the kids were small, or time was more scarce. But now, I have a bit of time where I could “go deep”, and find myself constantly pulled in different directions. There’s another bad impulse, which is, “I’ll do this when I have it all set up “right”.” Which sometimes is “the right gear”, which is almost always the <em>incorrect</em> impulse. Do the thing, get better to the point where you’re limited by the gear, then change the gear. But “new gear” <em>feels</em> like progress, and it often serves as a proxy for real progress. This is bad, and I’ve come to be better at recognizing it in myself.<br><br>But in any case, the thing is, it’s too much. That whole list of shit above? No one could be great at all that stuff. No one could even be <em>competent</em> at most of that stuff simultaneously. It’s just too much. Getting good at any two or three of those things would be the work of a lifetime.<br><br>I love getting “competent” at things, though, and I like that I’ve had the opportunity to dabble in a LOT of things, and become … not “fluent”, but maybe “conversant” in a ton of weird shit. But I would like to get <em>better</em> at a few things &#8211; probably making music (though narrowing it down between guitar and generalized music production is hard), and getting in better shape are the two things that I’d like to focus on the most that aren’t “explicitly spend time with friends and family”.</p>
  375.  
  376.  
  377.  
  378. <p>Maybe that’s just the goal in 2024. To figure out how to put the rest of things *aside* for a year, and just focus on those two things.</p>
  379. ]]></content>
  380. <link rel="replies" type="text/html" href="https://helava.com/2024/01/24/too-much-is-too-much/#comments" thr:count="0" />
  381. <link rel="replies" type="application/atom+xml" href="https://helava.com/2024/01/24/too-much-is-too-much/feed/atom/" thr:count="0" />
  382. <thr:total>0</thr:total>
  383. </entry>
  384. </feed>
  385.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.helava.com/feed/atom/

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda