<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Business on WT8P&#39;s Notes to Self</title>
    <link>https://wt8p.com/tags/business/</link>
    <description>Recent content in Business on WT8P&#39;s Notes to Self</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 08 Jul 2023 20:05:36 +0000</lastBuildDate>
    <atom:link href="https://wt8p.com/tags/business/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Notes on Field Day 2023</title>
      <link>https://wt8p.com/notes-on-field-day-2023/</link>
      <pubDate>Sat, 08 Jul 2023 20:05:36 +0000</pubDate>
      <guid>https://wt8p.com/notes-on-field-day-2023/</guid>
      <description>&lt;p&gt;I wrapped up another field day with my friend Paul (W7PEZ) in Eastern Washington. For the two days, I had 204 contacts, broken out roughly as:
&lt;img loading=&#34;lazy&#34; src=&#34;https://wt8p.com/images/image-52.png&#34;&gt;
&lt;em&gt;Yes, I worked SSB. It was kinda Frankfurt United Norway&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://wt8p.com/images/IMG_7671.jpg&#34;&gt;
&lt;em&gt;WT8P is sporting the 6-day salt and pepper look&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Paul worked 200 contacts, nearly all CW. Both are personal records. Neither of us were “running,” which would certainly have bumped up the totals, nor did we operate all the time, because most of the fun of Field Day is Everything Else.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Behind the hiring desk</title>
      <link>https://wt8p.com/behind-the-hiring-desk/</link>
      <pubDate>Mon, 04 Mar 2019 05:00:00 +0000</pubDate>
      <guid>https://wt8p.com/behind-the-hiring-desk/</guid>
      <description>&lt;p&gt;Some time ago, I’d been in hiring mode for a business analyst for my team and “had a few thoughts” that I have kept in draft form for some time.  As this is now an ex-company/team, I feel okay writing about it, but am somewhat lazy about changing present tense.&lt;/p&gt;
&lt;p&gt;How I think the process should have worked:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Hiring manager (me) transforms needs into requirements.&lt;/li&gt;
&lt;li&gt;Human Resources (HR) discusses it with me then initiates a search.&lt;/li&gt;
&lt;li&gt;HR is the gatekeeper, protecting the interests of the company and doing first-level screening.  Potentially-qualified candidates are forwarded to the me for review.&lt;/li&gt;
&lt;li&gt;If there’s interest, HR will set up a meeting between the candidate and me.&lt;/li&gt;
&lt;li&gt;If the results are positive, an interview may be scheduled with an extended group.&lt;/li&gt;
&lt;li&gt;If the results are positive, there is a verbal discussion of terms.  If an agreement is reached, a formal offer is generated.&lt;/li&gt;
&lt;li&gt;Employee and employer have a productive relationship&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;How it actually worked:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Email patterns</title>
      <link>https://wt8p.com/email-pattern/</link>
      <pubDate>Mon, 23 Jul 2012 13:35:01 +0000</pubDate>
      <guid>https://wt8p.com/email-pattern/</guid>
      <description>&lt;p&gt;Despite a concerted effort to keep my inbox tamed, it’s now back above 30 undealt-with emails.  While falling behind, I’ve noticed some recurring – and annoying – behavioral patterns.  I’m sure the list is incomplete, so feel free to share!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;“The two-for”&lt;/strong&gt; – a person who always — &lt;em&gt;always&lt;/em&gt;— sends a second mail with the attachment they forgot to include the first time.   I can’t tell if the person is genuinely a flake or if they’re just pining for the return of corporate instant messaging.  One wants to post a sign on their monitor: always wait at least 30 minutes after eating receiving the first message before swimming responding.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;“I must copy my manager on everything”&lt;/strong&gt; – the sender wants to ensure their manager knows they’ve made a token effort to be “proactive.”  Note the air quotes.  (It’s also possible the sender’s manager “wants to be kept in the loop for minutiae” (cough: micromanages) or needs a high message count to justify her &lt;a href=&#34;http://na.blackberry.com/eng/&#34;&gt;Crackberry&lt;/a&gt;.)  I used to whittle the Cc list down, but have since decided that it’s best to keep the list going.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;“I must copy your  manager on everything, too.”&lt;/strong&gt; – If I’m the sole entry on the “To:” list, the sender is implying I won’t respond to their request by overtly creating an audit trail.  Their manager is copied, too, as if to say, “See, I &lt;em&gt;warned&lt;/em&gt; them to check their blood pressure / Beware of the &lt;a href=&#34;http://news.nationalgeographic.com/news/2004/03/0311_040311_idesmarch.html&#34;&gt;Ides of March&lt;/a&gt; / &lt;a href=&#34;http://www.amazon.com/Soylent-Green-Charlton-Heston/dp/B0016I0AJG?ie=UTF8&amp;amp;tag=jimcarson-20&#34;&gt;Soylent Green&lt;/a&gt; is people — but &lt;em&gt;they did not listen.&lt;/em&gt;”  What usually happens is my over-detailed, super-helpful response will usually elicit a walk over for the executive summary.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;strong&gt;&lt;strong&gt;&lt;strong&gt;&lt;strong&gt;“The Escalating Cc:”&lt;/strong&gt; – two people in an email discussion have differing opinions.  Instead of, like, actually walking down the hall and having a conversation, they start adding additional people to the discussion.  Sometimes this will devolve into the passive aggressive tone. Paraphrasing an exchange that might hypothetically have gone out to an entire department:&lt;/strong&gt;&lt;/strong&gt;&lt;/strong&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;“I don’t want to blame anybody, I want to fix the problem.”  [three sentences later] “[…] but &lt;strong&gt;Bob&lt;/strong&gt;was the last one to touch it.  I will ask &lt;strong&gt;Bob&lt;/strong&gt;when &lt;strong&gt;Bob****comes in&lt;/strong&gt; what &lt;strong&gt;Bob&lt;/strong&gt;did to cause the system to become &lt;strong&gt;hopelessly broken&lt;/strong&gt;.”&lt;/p&gt;</description>
    </item>
    <item>
      <title>Disruptive technologies</title>
      <link>https://wt8p.com/disruptive-technologies/</link>
      <pubDate>Sun, 06 Mar 2011 05:33:20 +0000</pubDate>
      <guid>https://wt8p.com/disruptive-technologies/</guid>
      <description>&lt;p&gt;Supercomputing 2010’s keynote was Clayton Christensen, the author of &lt;a href=&#34;http://www.amazon.com/gp/product/0060521996?ie=UTF8&amp;amp;tag=jimcarson-20&amp;amp;linkCode=as2&amp;amp;camp=1789&amp;amp;creative=390957&amp;amp;creativeASIN=0060521996&#34;&gt;The Innovator’s Dilemma&lt;/a&gt; (and its numerous follow-ons), whose research, studying the demise of companies over time, is utterly fascinating (to me) and I can’t believe I hadn’t read before.&lt;/p&gt;
&lt;p&gt;He has studied the demise of companies over time — think Digital Equipment Corporation (&lt;a href=&#34;http://en.wikipedia.org/wiki/Digital_Equipment_Corporation&#34;&gt;cut up into bite-sized chunks in 1998&lt;/a&gt;, the rest of which was eaten by Compaq, which was eaten by HP), SGI (a darling when Jurassic Park came out, but ultimately &lt;a href=&#34;http://en.wikipedia.org/wiki/Silicon_Graphics&#34;&gt;liquidated in 2009&lt;/a&gt;, assets bought by Rackable systems), and Sun (bought by Oracle).  He’s observed recurring patterns of market disruption.  For example, in the case of DEC, their rise was predicated on being cheaper than mainframes.  As they gained more experience, the minicomputers became more reliable, but were still in the $100k range.  DEC itself was subject to PCs meeting a nascent market need willing to tolerate PCs being utter crap (early-on), but at a far different price point.  As PC technology evolved, it became compelling enough that few were buying VAXen.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Today is a good day to PLOT!</title>
      <link>https://wt8p.com/today-is-a-good-day-to-plot/</link>
      <pubDate>Sat, 13 Mar 2010 17:42:09 +0000</pubDate>
      <guid>https://wt8p.com/today-is-a-good-day-to-plot/</guid>
      <description>&lt;p&gt;Mister Peabody, set the Wayback Machine to three years ago, pick a spot during a really long product release cycle.  Partly out of boredom, but mostly to mess with development manager at the time, I had asked one of the developers to swap out the splash screen.  The product logo was thus modified:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;  **Official**

  **Battle-ready!**
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Appropriate text was substituted, changing our tagline from “Enjoy the view” to “Today is a good day to PLOT!”  Laughs were had, and it was removed before alpha testing several months later.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Get versus 529 redux</title>
      <link>https://wt8p.com/get-versus-529-redux/</link>
      <pubDate>Mon, 01 Feb 2010 09:50:15 +0000</pubDate>
      <guid>https://wt8p.com/get-versus-529-redux/</guid>
      <description>&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://cdn.wt8p.com/tamper1-07.gif&#34;&gt;
In April of ought six, I &lt;a href=&#34;https://www.wt8p.com/2006/get-versus-most-529-plans/&#34;&gt;pondered two options&lt;/a&gt; for saving for my kids’ college: the 529-plan I have and Washingon State’s 529 program, Guaranteed Education Tuition (“&lt;a href=&#34;http://get.wa.gov/&#34;&gt;GET&lt;/a&gt;“). At the time, I concluded my existing 529 would have a better expected return because the expected returns over my relatively short investment horizon (10 years) would not be enough to offset the better expected return, but 20% front-end load of the GET.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GET versus MOST – 529 plans</title>
      <link>https://wt8p.com/get-versus-most-529-plans/</link>
      <pubDate>Sun, 02 Apr 2006 05:20:55 +0000</pubDate>
      <guid>https://wt8p.com/get-versus-most-529-plans/</guid>
      <description>&lt;p&gt;&lt;strong&gt;&lt;em&gt;(See &lt;a href=&#34;https://www.wt8p.com/2010/get-versus-529-redux/&#34;&gt;my update&lt;/a&gt; on this topic.)&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We have a &lt;a href=&#34;http://en.wikipedia.org/wiki/529_plan&#34;&gt;529K&lt;/a&gt; college savings program set up for my kids through the &lt;a href=&#34;http://www.missourimost.org&#34;&gt;State of Missouri&lt;/a&gt; program administered by TIAA-CREF, soon-to-be Vanguard. Its investment options are turnkey bundles based on age ranges. In the initial years, the investment selection is aggressive. As college-time nears, the portfolio’s mix shifts from stocks to bonds.&lt;/p&gt;
&lt;p&gt;The program’s return has varied. From 2000 through 2003, it did poorly, like &lt;a href=&#34;https://www.wt8p.com/a/2004/08/airplane_owners_1.shtml&#34;&gt;everything else I owned&lt;/a&gt;. The last two years have been very strong, negating those losses and then some. Overall, I’d estimate its average return has been about 6.5% over the period we’ve had it. While not bad for a retirment portfolio (especially during that time period), it &lt;em&gt;is&lt;/em&gt; less than &lt;a href=&#34;http://money.cnn.com/2004/05/18/pf/college/tuition_increases/&#34;&gt;college tuition&lt;/a&gt;. I really need a way to invest into “tuition futures.”&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fomplicated</title>
      <link>https://wt8p.com/fomplicated/</link>
      <pubDate>Fri, 25 Mar 2005 13:30:30 +0000</pubDate>
      <guid>https://wt8p.com/fomplicated/</guid>
      <description>&lt;p&gt;I’m coining a new term, &lt;strong&gt;fomplicated&lt;/strong&gt;, to describe a product that requires deliberate intervention and expertise from a customer beyond what any sane human being would consider reasonable. The word is a contraction of a well-known English expletive rhyming with firetrucking and the word “complicated.”&lt;/p&gt;
&lt;p&gt;Although it’s applicable to a variety of things, I’ve been seeing it a lot related to my computer. For example, this morning I had a minor fomplication. While poring through some mailing-list email, I saw that &lt;a href=&#34;http://kmtt.com&#34;&gt;KMTT&lt;/a&gt; 103.7FM has an online stream. The Mountain Music Lounge is great stuff, but I don’t get good reception indoors. I had an unsatisfactory experience with a pay-for service that claimed to have the station, but really only played a pre-selected “best of” 20 songs. (&lt;a href=&#34;https://www.wt8p.com/2005/maybe-its-time-to-simplify-life/&#34;&gt;Cancelling&lt;/a&gt; that service was unnecessarily fomplicated, too.) KMTT’s option would not only serve it live, but would also be free. And it claimed to run on my Linux and Windows machines. Score!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Airplane ownership</title>
      <link>https://wt8p.com/airplane-ownership/</link>
      <pubDate>Mon, 16 Aug 2004 13:21:27 +0000</pubDate>
      <guid>https://wt8p.com/airplane-ownership/</guid>
      <description>&lt;p&gt;For you newly-minted pilots who have asked me, “should I buy an airplane?” I offer a quick rule of thumb, based on my ten years in general aviation, four years of ownership, and MBA: &lt;strong&gt;No.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://cdn.wt8p.com/i/elvis_stamp.jpg&#34;&gt;&lt;/p&gt;
&lt;p&gt;Okay, now that we’ve gotten that formality out of the way, here is some insight into the costs of acquisition and ownership, so you can make the inevitable decision.&lt;/p&gt;
&lt;p&gt;You have no doubt heard the fairytale that you should consider ownership if you fly more than 100 hours a year because &lt;em&gt;airplanes are an investment&lt;/em&gt;. It’s true that my airplane outperformed 11 of my 12 stocks, but if you look at the numbers closely, you’ll notice that buying postage stamps or stuffing the money into a mattress for those four years would have beaten everything.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
