Screencasting Practice & Feedback: 00003

Plan

  • Demonstrate lessons-learned about alternate input methods and redefinition of the Emacs interpretation of modifier keys
  • Utilize a lower-third instead of text-boxes
  • Talk louder

Execution

Preparation

  • Pretend you are going to a job-interview, or on a date, that is recorded for everyone to see, forever
    • Perform all personal preparations that you normally would for example
      • Brush your teeth
  • Applied Revlon PhotoReady Prime + Anti Shine Balm Clear
  • Lights and camera and microphone
    • Set them up
    • Tested them
    • Hooked up camera and turned it on
    • Adjusted white balance
    • Set left light pointed at me; right light pointed at ceiling
    • Adjust left light to give face warmth (versus ghost appearance)
    • Microphone is on and input volume maxed out
  • Turn off HVAC
  • Mute Phone and Pushbullet
  • Close other applications
  • Verify microphone woks
  • Verify recording on correct monitor
  • Write rough script
  • Pour glass of water

Execution

  • Showed off Emacs mug and encouraged FSF support

Screencasting Practice & Feedback: 00002

Plan

  • Demonstrate how I like to quote content in Org-Mode
  • Learn how to use call-outs and text-boxes
  • Learn how to ad-lib content
  • Scripted out location of content and video-recording of presenter to make sense of what is appearing on the screen and where
  • Learn how to use content-music

Execution

  • Made video top right 100% of the top right corner
    • This means scaling it by 50%
  • Remove the dropshadow from the video
    • The video stood out enough already
  • Amplified volume by 200%
  • Added callouts interesting content
  • Added watermwark, 25% scale, 25% opacity, 10 key-presses from bottom and right edge
  • Include the word Screencast in announcement to distinguish between screencast and blog post
  • 6h of effort for 7m of content
  • Posted manually on Reddit
  • Blog published to social sites

Outcome & Feedback

  • Wrote a script; didn’t pay attention to it enough
  • After re-recording it six times, said I would never re-record it again. Instead made corrections using text-boxes positioned over my face.
  • Light was OK
  • Speaking volume was too quiet; content volume was too loud
  • Skin was shiny
  • Looping the banner and jingle at the end was a mistake
  • The 3m monologue about Braille displays was interesting to me and perhaps no one else so don’t include that. 3m is a long time.
  • Use a lower-third intead of text boxes
  • Redditers commented that a blog post would have been more concise and faster. What is the best of both worlds?

Screencasting Practice & Feedback: 00001

Plan

  • Develop a jingle and banner to introduce the videos
  • Learn how to use ScreenFlow on smallest project possible
  • Learn how to publish and monetize on YouTube
  • Learn how to define closed-caption content

Outcome & Feedback

  • YouTube
    • Easy and pleasant process
    • Signing up takes 30m or so
    • Publishing the video offers 20-30 configuration options
  • Forgot to develop a watermark for the videos
  • Closed-captioning is tedious and time-consuming
  • Screenflow project is large; be sure to keep it on a large disk
  • Glad to have worked in a simple project like this to get some practice with Screenflow. It took some trial and error to grok the power of layers in practice.
  • Volume wasn’t loud enough
  • Transitions were OK; can see some blockiness because of how I layered the background

Easily Move Comments to Another Post in WordPress

Sometimes you accidentally double-post the same article. It looks like an easy fix until you notice that people have commented on both articles! It turns out that the solution is pretty easy if you are comfortable with SQL. This post is a work of art concisely explaining what to do and making it simple.

Choosing a WordPress Vagrant Box

I want a Vagrant box on which to configure and develop WordPress. Here are some of the options. I wanted to decide on one. Here is how.

  • Box: name
  • Stars: on GitHub, # stars
  • Ctrb: on GitHub, # contributors
  • Rel: on GitHub, # releases
  • Cmts: on GitHub, # commits
  • Brn: on GitHub, # branches
  • For: Purpose of box
  • Rct: Gut reaction 1
    • +: Like
    • *: Pros and Cons
    • -: Dislike
  • Rt2: Gut reaction 2

Strategy:

  • Identify options
  • Classify them by stars and contributors
  • Get a gut reaction whether to dig deeper or not
  • Review them again
Box Stars Ctrb Rel Cmts Brn For Rct Rt2
VVV 2323 72 13 1178 4 WP Dev +  
Vagrnt-Press 696 17 0 107 5 Gen dev + ++
vipquickstart 242 23 3 562 9 Gen dev +
Primary-Vgrnt 103 7 15 399 3 Gen dev + na
wp-nginx-hhvm 28 2 0 20 1 Gen dev + na
MonkeyRocket 13 1 0 5 2 Gen dev + na
Chassis 330 17 0 274 7 Gen dev * na
wp-vagrant 110 1 0 17 2 Reg sup * na
vccw 382 20 45 343 3 Gen dev * na
genesis 674 10 83 384 42 Gen dev * na
VVV-site-wizard 373 5 0 70 2 Cfg VVV na
vvv-reviewer 69 3 4 23 2 Rvw na
VAW 78 2 0 31 1 Gen dev na
WP Machine 14 1 0 17 1 LAMP na
wpkickstart 32 9 0 44 1 DigOcn na

VVV seems to be the best place to start.