Skip to content

Posts from the ‘Diverse’ Category

A Story About Stats on Your Pretend Personal Dev Blog

February 15th, 2021

olavea

We’ll pretend you are doing some GatsbyJS-style work on your personal dev blog. And we’ll pretend you ask yourself:

«Self, what would happen if you stopped collecting gobs of personal data about your dev friends with google analytics?»

Let’s say you installed Benedicte’s Fathom Plugin. Then you could open a single Fathom dashboard and at a glance see your top content.

«Pop! Pop!»

Into your head pops two good ideas for blog posts. You decide to go with Idea Number One, because you just FEEL Idea Number One is a better idea for your dev friends. Your gut feeling is based on stats because your top content is right before your eyes and this new Idea Number One «rhymes» with som of it.

Why don’t you take Benedicte’s Fathom Plugin for a spin around your dev blog and see if it gives you clarity?

This next story is aaalmost without pretend in it.

A Story About Benedicte Using Fathom To Focus on Her Real Work And Not Being Distracted By Distracting Data

This time I will tell you a story aaalmost without pretend in it. A story about developer-Benedicte using her own Fathom Plugin and I will tell you in advance what the pretend part is. This story is based on a real website. The website has a real product, POW! the bleh bleh. The product has real customers. Pretend Alert! I will give one of the real customers a fake identity, because …. reasons. The fake identity is Princess Lizabeth (17), I hope you can handle a little sprinkle of glittery royalty 👑. 😺 If so, let’s go!


### A Long Time Ago,
### By a Bridge Far, Far Away ….

Princess Lizabeth (17) is sunning her white face and red hair on the pink deck of her sister smart little ship. Lizabeth is writing away in her end-to-end encrypted journal mostly about her menstrual cycles. But she is also writing about toxic relationships, like her hateful sister Mary. Now dear reader, instead of going into these powerfully personal details, I will urge you to ask yourself ONE question about data.

#### Question 1:
«Self, how much data is being reported back to developer-Benedicte by Fathom about Princess Lizabeth’s current writing activity?»

#### Answer 1:
«Nothing.»

#### Question 2:
«Nothing?»

#### Answer 2:
«Nothing.»

And nothing is Just Enough, because.

#### Question 3:
«What »

Did Han Zapier Zap First?

January 18th, 2021

olavea

A is for zAp

B is Brew

C is Call for Glide from your Zap

D is «Did Han Zap First?»

E

F

D is «Did Han Zap First?»

Zap-3_D is «Did Han Zap First?»_MAKE_A_ZAP-3-1
Zap-3._Lager_1_Zap_oversikt-3-14

1.1

Zap-D_MAKE_A_ZAP_Choose_app-3-2

1.3

Zap-D.1.3_Trigger_Event-3-3

1.4

Zap-D.1.4_Choose_Account_Size631x446-3-4

1.5

Zap-D.1.5_Test Trigger_Size_631x446-3-6

How I Prepped To Get A Badass Code Review On My .env File

January 9th, 2021

olavea

First we’ll look at the tasks I did in 8 steps, then we’ll look at why and when I do Code Reviews in our indie hacker webapp and in my programming play projects. My main inspiration comes from observing my father captaining his traditional Norwegian wooden sail ship with a crew of girls and boys, in the summers of my boyhood and early manhood. That is why I call it:

Skipper-Ola’s Code Review Tasks

  1. Prepares 
  2. Calls Tom Erik
  3. Listens up!
  4. Takes notes
  5. Ships my website in SMS link
  6. Says “Tell me what you are doing” 
  7. Shows my code in shared screen link
  8. Explains what I did with .env
  9. Do EVERYTHING Tom Erik suggest I do, right now
  10. Says “Thank you”
  11. Makes Tom Erik SketchNotes from notes, Right now for 90 minutes

8. is the most important to spend time on. I spent 90 minutes on 8 and 90 minutes on the other seven.

The point of this kind of usability testing is clarity. To make the 1-Job-Prototype clear for the one tester I am testing on, Martin G. So that Martin G. can go in, do the 1 job he is supposed to do without becoming distracted. And that is hard. It is suuuper hard to make a prototype that is easy-to-use. (

What Are the Eight Tasks of Usability Testing?

Let’s go to 1. Prepares.

1. Prepares 

Skipper-Ola’s Preparation Tasks For Usability Testing:

  • Sends warning to Martin G.
  • Finds two test dates.
  • Invites Martin G.
  • Writes a short script.
  • Tests 1-Job-Prototype on his own iPhone. (17:46)
  • Reminds Martin G.

2. Calls Martin G.

  • Calls
  • Smalltalks
  • “Are you alone?”
  • ” … and put your headset on.”

3. Listens Up!

  • Hearing accurate input
  • Listens actively
  • Gives UNDIVIDED attention
  • Immerses his mind in:
    • Voice and silences
    • Noises like a low “Grrrh!”

4. Takes Notes

Shuts up and writes down

5. Ships my prototype

  • I send SMS with a link to Marita’s prototype
  • “Did you click that SMS link?”

6. “Tell Me What You Are Doing.”

  • “I will read my script.”

7. Says “Thank You!”

  • Martin G. knows: VERY Valuable

8. Re-Works My Martin-G.-Notes

I sit and observe my thoughts on:

  • What Martin G. did
  • Remove:
    • Choices.
    • Distractions.
  • Make my 1-Job clearer for Martin G.

First thing: for 90 minutes:

  • I re-work my notes.
  • I capture fresh ideas.
  • I see my next task, so:

TODO: First find two good testing dates in your calendar

Why Usability Testing?

Benedicte has limited time and treasure.

So without doing usability testing timely, Benedicte cannot build to DONE. (See upcoming blog post on how I define DONE.)

Because nothing beats a real human trying to use Benedicte’s 1-Job-Prototype. To flush out ideas that don’t work.

When To Do Usability Testing?

  • As
  • Soon
  • As humanly
  • Possible

Feel Ready?

How Usability Testing Can Help You Closer to DONE

December 13th, 2020

olavea

First we’ll look at the tasks I did in 8 steps, then we’ll look at why and when we do usability testing in our family business.

Skipper-Ola’s Usability Testing Tasks

  1. Prepares 
  2. Calls Martin G.
  3. Listens up!
  4. Takes notes
  5. Ships his prototype in SMS link
  6. Says “Tell me what you are doing” 
  7. Says “Thank you”
  8. Makes MartinG SketchNotes from notes, Right now for 90 minutes

8. is the most important to spend time on. I spent 90 minutes on 8 and 90 minutes on the other seven.

The point of this kind of usability testing is clarity. To make the 1-Job-Prototype clear for the one tester I am testing on, Martin G. So that Martin G. can go in, do the 1 job he is supposed to do without becoming distracted. And that is hard. It is suuuper hard to make a prototype that is easy-to-use. (

What Are the Eight Tasks of Usability Testing?

Let’s go to 1. Prepares.

1. Prepares 

Skipper-Ola’s Preparation Tasks For Usability Testing:

  • Sends warning to Martin G.
  • Finds two test dates.
  • Invites Martin G.
  • Writes a short script.
  • Tests 1-Job-Prototype on his own iPhone. (17:46)
  • Reminds Martin G.

2. Calls Martin G.

  • Calls
  • Smalltalks
  • “Are you alone?”
  • ” … and put your headset on.”

3. Listens Up!

  • Hearing accurate input
  • Listens actively
  • Gives UNDIVIDED attention
  • Immerses his mind in:
    • Voice and silences
    • Noises like a low “Grrrh!”

4. Takes Notes

Shuts up and writes down

5. Ships my prototype

  • I send SMS with a link to Marita’s prototype
  • “Did you click that SMS link?”

6. “Tell Me What You Are Doing.”

  • “I will read my script.”

7. Says “Thank You!”

  • Martin G. knows: VERY Valuable

8. Re-Works My Martin-G.-Notes

I sit and observe my thoughts on:

  • What Martin G. did
  • Remove:
    • Choices.
    • Distractions.
  • Make my 1-Job clearer for Martin G.

First thing: for 90 minutes:

  • I re-work my notes.
  • I capture fresh ideas.
  • I see my next task, so:

TODO: First find two good testing dates in your calendar

Why Usability Testing?

Benedicte has limited time and treasure.

So without doing usability testing timely, Benedicte cannot build to DONE. (See upcoming blog post on how I define DONE.)

Because nothing beats a real human trying to use Benedicte’s 1-Job-Prototype. To flush out ideas that don’t work.

When To Do Usability Testing?

  • As
  • Soon
  • As humanly
  • Possible

Feel Ready?

Lillian (5.5 🦄 ) Built a Backseat Prototype For Mum’s New Electric Cargo Bike

Featured

What do you do, when you want to go «Whee!» on mum’s new bike, but your back seat has yet to be delivered? Can Lillian (5.5 🦄 ) prototype the back seat instead?

Yes. She. Can!

Lillian (5.5 🦄 ) built a do-it-yourself saddlebag backseat prototype on mum’s new electric cargo bike. Because that’s how we roll our no-code prototyping in our family.

A Good Idea For The Prototype

Dad’s original idea was to fasten the saddlebags with gaffer’s tape. Lillian (5.5 🦄 ) had a better idea: String!
So we used string which leaves no marks on the bike.

Black Gaffer’s tape, 8 long strips, 8 short strips (bought: Jernia Carl Berner by Mommo and Lillian (5.5 🦄 )
Lillian (5.5 🦄 ) had a better idea: String! So we used string which leaves no marks.

Questions About Electric Cargo Bike Rental

What did daughter and father learn today? The answer comes further down, but first a few questions to you, dear reader. If you can answer yes to one of these questions, please send me a flag signal ola {@} olavea.com.

  1. Does your city have an electric cargo bike rental service like we have in Oslo, Norway?
  2. Do you have an electric cargo bike from a rental service? (And maybe you have a few tips for us.)
  3. Do you own an electric cargo bike? (And maybe you have a few tips for us.)
  4. Have you built a bike related prototype? (And maybe you want to share your story with us.)
  5. Have you guessed what movie an/or actor inspired this sketchnote of Lillian (5.5 🦄 ) sitting on the saddlebags?

(illustration CLOSE UP coming)

Today Lillian (5.5 🦄 ) Practiced No-Code Prototyping

-Cutting gaffer’s tape with siccors
-Cutting string tape with siccors

Today Dad Practiced No-Code Prototyping


-Bending and cutting cardboard
-Using gaffer’s tape with cardboard
-Taking photos from bike (😅)

Today Dad Learned About No-Code Prototyping


-Spend more time on building the actual prototype
-Spend less time on making drawings and notes about the prototype before building it. Because we never got time to measure ONE single thing.