Saturday, August 22, 2015

Time.Ltd:Mortality Software

*This post is a work in progress, in the madman/architect phase, if you'd like to help flesh it out, I'd love the help.  please add comments or ping me.*

Why mortality software?

To be satisfied we need to live in accordance with the person we want to be.

Unless we know who we want to be, and act deliberately to achieve it, our satisfaction will be infrequent, and often accidental.

Mortality software helps you understand who you want to be, and supports you in being that person. In a nutshell, making your satisfied.

The first step for mortality software is helping you figure out the person you want to be and your values.

Who do you want to be? What are your values?

To figure out who you want to be, write your eulogy.  To make it easier, figure out the roles in your life. Imagine the person who would speak to each role of your life during your funeral.  What would you want each person to say?   That eulogy is the person you want to be.

Now imagine how you'd want people to remember the way you acted, especially during ambiguity, challenges and crisis.   Those behaviors are your values.

Your roles, how you balance your between them,  and your values are the person you want to be, your north star.

What else should mortality software do?

Becoming the person you want to be starts, by figuring out who that person is. Next it decomposes becoming that person into at different levels of abstraction and time scales.  Here's an example:

Time Horizon
What
How
Life
Eulogy and Roles
Values
Two year
Supporting  Projects/Accomplishments
Supporting Behaviors/Habits
Quarter -> Month
Decompose above into reasonable chunk
How to allocate time between roles
Decompose above into reasonable chunks
How to allocate time between habits/behaviors
Month -> Week
Milestones
Habits
Week -> Day
Tasks
Skill/Habit Practice Schedule

Mortality software will be both forward and backwards facing. By this I mean it will help you plan what you need to do to achieve your eulogy, and also help evaluate how effectively you are achieving your goals.   It will help you reflect, often helping you realize your initial eulogy requires change, or your behaviors require change.

Why call it Time.Ltd?

I conceived of mortality software when I realized my life is finite, and thus limited. I initially named my future mortality software package Life.ltd, but that did not feel actionable.  Instead of thinking our life is limited, we  should think our time is limited, and thus we should make sure we are using it
well.  Thus, I renamed my future mortality software Time.Ltd.

Thursday, July 23, 2015

A richer model of happiness - Pleasure/Flow/Satisfaction

Happiness is a coarse term, and often leads to cumbersome discussion and confusion. Martin Seligman provides a more granular model of happiness: pleasure, flow and satisfaction.   This model will be useful as we discuss positive computing. 

Pleasure is the happiness of doing what feels good in the moment.  It's the happiness of consumption.  Eating, drinking, buying something.  Pleasure is easy to achieve, but the happiness is lost within minutes. 

Flow is the happiness of being engrossed in a a challenging, enjoyable task.   It's the happiness of production. Making art,  baking cookies, working on a project.  Flow takes effort to get started, but the happiness last the length of the task, often lasting hours.

Satisfaction is the happiness of  being the person you want to be.  It's the happiness of identity.  This happiness is deeply personal, for me it's being a deliberate person who can put a smile on a strangers face.  Satisfaction takes significant effort, but the happiness can be unshakable and permeate your being. 

Positive computing will need to address each of these aspects of happiness to best serve our users. 

Wednesday, July 08, 2015

Cool Tools: DVD Burning

Last time I tried to burn a DVD, finding the right software was a mess and I gave up. This time, I found a tool called imgburn and it just works.  

The default installer bundles malware with the download, so be sure to use the custom installation options, or use chocolatey to install.

Monday, July 06, 2015

Soft Skills: Writing as Madman, Architect, Carpenter and Judge

Writing breaks down into 4 distinct phases:  brainstorming, organization, writing and editing. To  reinforce the distinctness of these  phases, think of writing as four distinct jobs:  Madman, Architect, Carpenter and Judge.   Maximize your efficiency by doing each job, distinctly, deliberately and serially.

Each  job has a specific goal,  and  that goal should be your  sole focus during while doing that job.  Do not do the next job, and do not go back to previous jobs.  To reinforce the distinctness of each job, consider using a different tool, and physical reminders of each job.

As madman, your job is brainstorming.  Take your brain's musings and get them down on paper. Maximize creativity, find as many interesting ideas as possible. As madman don't waste time "arguing" or "revising" what you're spitting out.  Personally, I use pen and paper when  I'm the mad man to prevent  myself from revising, editing, or organizing my thoughts.

As architect, your job is organizing. Take the madman's ramblings and distill them into an outline. Decide what you want to say, who your audience is then, produce a model and outline via aggressive triaging. As architect don't waste time on "how it sounds" or "how it looks".  Personally, I use point form lists in OneNote when I'm the Architect as it allow me to  easily see and organize the structure of my writing.

As carpenter, your job is writing the paragraphs, sentences and words.  Take the architects outline and turn it into to paragraphs and sentences.  Decide the tone, the examples, and start writing. As carpenter don't waste time on spelling, grammar, or excessive rewriting. Personally, I turn off the spell checker when I'm the Carpenter as to prevent me from fixing typos that I'll likely rewrite anyway.

As judge, your job is editing.  Take the carpenters masterpiece and make it consistent, and error free.  Make sure everything is correct and be critical.  Personally, I turn the spell check on at this phase, but I'm terrible at judge, and usually enlist the help of others when doing this job.

By splitting out the different jobs of writing, your writing should get clear, faster, and more rewarding.

Tuesday, June 02, 2015

Startupville: Reading list

Books I recommend:

Start small stay small  - How to build a realistic software business.  
Business Model Canvas and Value Proposition design - Value prop, and business is king. This book is a must read.  Be sure to by the print book as it's full of pictures and diagrams. 
V is for vulnerable - A cute book on the attitude you need to survive as an entrepreneur.  
Lean startup - The book that kicked off how to run a startup
Traction - A treatise on customer aquistion strategies or how to get traction.

Books I'm reading now:

Zero to one - In progress looks great. 

Blogs/Articles

In progress
Paul Graham - Paul is the founder of y-combinator and his writings defined the startup industry.
Brad Feld - One of the other best loves VC's. Often talks about funding, very interesting.
We don't sell saddles here - A treatise from the founder of Slack.

Commonly recommended books I could not finish:

Startup Owners Manual - Steve Blank - Steve is a smart guy (Mentor of Lean Startup Guy) and arguably the inventor of customer development,. However, I find his writing and this book meandering. I wanted to read this book but could not finish.

Friday, May 29, 2015

Soft Skills: How to communicate effectively

To be successful, you must communicate your ideas. The heart of communication is a story which must be written. Emma Coats wrote stories for Pixar, and tweeted a series of “story basics”. Most of these are applicable to communicating, and I’m posting them here to remind myself how to communicate better.

What do you want to say?

  • Why must you tell THIS story? What’s the belief burning within you that your story feeds off of? That’s the heart of it.
  • Come up with your ending before you figure out your middle. Seriously. Endings are hard, get yours working up front.
  • What’s the essence of your story? Most economical telling of it? If you know that, you can build out from there.

How you want to say it?

  • You gotta keep in mind what’s interesting to you as an audience, not what’s fun to do as a writer. They can be v. different.
  • Discount the 1st thing that comes to mind. And the 2nd, 3rd, 4th, 5th – get the obvious out of the way. Surprise yourself.
  • Simplify. Focus. Combine characters. Hop over detours. You’ll feel like you’re losing valuable stuff but it sets you free.
  • Trying for theme is important, but you won’t see what the story is actually about til you’re at the end of it. Now rewrite.
  •  Once upon a time there was ___. Every day, ___. One day ___. Because of that, ___. Because of that, ___. Until finally ___.

How do you stay motivated as a writer?

  • Putting it on paper lets you start fixing it. If it stays in your head, a perfect idea, you’ll never share it with anyone.
  • Finish your story, let go even if it’s not perfect. In an ideal world you have both, but move on. Do better next time.
  • When you’re stuck, make a list of what WOULDN’T happen next. The material to get you unstuck often shows up.
  • No work is ever wasted. If it’s not working, let go and move on - it’ll come back around to be useful later.
  • You have to know yourself: the difference between doing your best & fussing. Story is testing, it testing not optimizing.

How to become a better writer:

  • Pull apart the stories you like. What you like in them is a part of you; you’ve got to recognize to use it.
  • Take the building blocks of a movie you dislike. How d’you rearrange them into what you DO like?

Thursday, May 28, 2015

What positive computing approach are you taking in your designs?

The positive computing book lays out a simple model for the approach your designs can be taking, I summarize it here:

Approach Description Example
None Happiness ignored Most applications today - no attempt to make users happy
Passive (reactive) As issues are found which effect happiness, features are redesigned Comment systems allowing anonymous comments. As anonymous comments filled with negativity, comment systems evolved to allow enforcing a user identity, and to block "bad" users. [TBD: Get a better example]
Active Augmenting existing features to make users happier Bing home page - displaying beautiful images that makes users happy.
Deliberate The goal of the feature is user happiness exclusively Happify- a tool to train users ot be happier