Measuring In the moment happiness (InMoHap) with moodles (Mu)

This post is in progress to help me flesh out my progress -- feedback please! 

TL;DR:  Moodles, abbreviated Mu, is a measure of in the moment  happiness" (InMoHap), which is extremely helpful when exploring positive computing. 

The case for moodles. 

The goal of positive computing is to make users happier, which means we need to measure happiness to tell if users are happier.   The current methods to measure happiness have limitations (details on request) , so we'll define a new ideal unit for in the moment happiness (InMoHap)  called the moodle, abbreviated Mu.

The properties of the Mu is it can be objectively measured at any moment of time with minimal  user interruption.    For example, just as a fit bit can transparently count your steps through the day, a Moodle-O-Meter can measure your InMoHap throughout the day.

Examples of using moodles. 
To get a good understanding of InMoHap and moodles the following graphs show some typical events through the day -- I'll flesh the below out with InMoHap graphs

Example #1: going through your day and getting triggered when you get a nasty gram from your Ex wife

Example #2: going through a normally grinding day

Example #3: Getting a surprise love letter from your partner.


The things that make InMoHap confusing: 
Even though moodles are a step up from our current measures, they have a few confusing properties:

First, the relationship between moodles and satisfaction is complicated (details on request).  For example, you might spend an entire vacation doing nothing but being drunk, this may high moodles, but does not improve satisfaction.

Second, moodles are the measure of an experience at a point in time.   The moodles a situation produces for the experiencing self, may be different from the moodles as experienced by the remembering self. The remembering self uses the  peak end rule 

For example, imagine today at 5pm Bob is running and in pain, having a low Mu.  Tomorrow when Bob remembers the run as a great experience and remembering the experience of running he has a high moodle count. 


Approximating Moodles with existing tools and measures
Sadly, moodles don't yet exist. However we have some ability to measure happiness which I'll describe here.

Comments

Post a Comment

Popular posts from this blog

Finding CLR exceptions without visual studio

(If you want to understand what exception code 0xe0434352 is, read this post ) Often exceptions are thrown and caught and you don't see them. You probably know how to debug this in Visual Studio, so let me show you how to do it in cdb. Sample Code: class Program { static void Main(string[] args) { foreach (var x in Enumerable.Range(0,2000)) { Thread.Sleep(TimeSpan.FromSeconds(1)); Console.WriteLine("Hello World"); ThrowAndCatchException(); } } private static void ThrowAndCatchException() { try { throw new NotImplementedException(); } catch(Exception) { } } } Output of the application: Hello World Hello World Hello World Nothing about an exception, but you're sure it's happening behind the covers -- fire up cdb: C:\Program Files\Debugging Tools for Windows (x64)>cdb -pn consoleapplication3.exe <SNIP> ModLoad: 000007fe`f7e90000 000007fe`f7eb4000 C:\Windows\Mi...
Read more

Why do I keep getting exception code e0434352?

If you want to know how to debug CLR exceptions using cdb then read this post . Exception code e0434352 is the exception code used internally by the CLR to represent most exceptions(*). Regardless of if you throw a System.NullReferenceException or a System.ArgumentException in C#, you'll throw a SEH exception e0434352 under the covers. A fun way to validate this theory is to watch what happens to the CLR exceptions settings in cdb. Fire up cdb, and see the state of clr exceptions: 0:000> .shell -ci "sx" findstr clr clr - CLR exception - second-chance break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Now, set the exception handler for exception number e0434352 and recheck the value of the clr exception handler: 0:000> sxe e0434352 0:000> .shell -ci "sx" findstr clr clr - CLR exception - break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Armed with ...
Read more

Powershell script to enable windows to capture localhost traffic in wireshark

If you want to understand why the following scripts work read this post . Otherwise just paste the following into an elevated powershell window: Setup windows networking to allow localhost capturing in wireshark: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "You don't have 1 default gateway, your network configuration is not supported" } # Route local IP address via the default gateway route add $defaultAdapter.IPAddress[0] $defaultAdapter.DefaultIPGateway Write-Host "Start capturing on localhost by connecting to $($defaultAdapter.IPAddress[0])" Return windows networking to normal configuration: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "Y...
Read more