dissolved

# -----------------------------------------------
# For the subject line:
#   * Use 50 characters maximum.
#   * Do not use a sentence-ending period.

# --skip-ci

# ---------------------------------------------------------------------
# For the body text:

dissolved

Blocking vs Non-Blocking

A real world example

Let's say you have the following chores to do:

• Balance your checkbook
• Do 3 loads of laundry
• Cook a pie

If we did all of these tasks synchronously it would take a very long time. Balancing the checkbook might take 30 minutes, each load of laundry will need to go through a wash cycle (30 minutes), and a dry cycle (45 minutes), and cook a pie (15 minutes prep, 30 minutes baking). If we blocked on each task, it would go like this:

dissolved

Cargo Culting Ruby's freeze

Years ago you rarely saw frozen Ruby objects, but it is very much popular now. There are good reasons to freeze. Take this commonly cited example:

MOVIE = "Not Frozen"
MOVIE << " II" # note no warning because MOVIE is not reassigned, but rather the string is mutated
puts MOVIE # "Not Frozen II"

dissolved

Not a Bird

Status

• Works on Chrome without any much error handling.
• Doesn't work on Firefox (yet)

Installation

1. Optionally minify the code (can do that here)
2. Create a bookmark, start it with javascript: then append the code

dissolved

I was helping out my friend who’s rubocop was complaining on ABC complexity on a method to format a range where either the lower or upper bound or both might be absent. Here was my solution that finally solved it, but here is where I simply wonder if the hoops we jump through to make static code analyzer’s happier isn’t always leading to more readable/maintainable code. You tell me, which is better?

The examples have been simplified to remove implementation details not important to this discussion. example.rb satisfies Rubocop while original.rb gets flagged for ABC complexity.

dissolved

class Board():
    """A Tic-Tac-Toe board.

    Internal representation by 1-dimensional list visualized as:
     0 | 1 | 2
    -----------
     3 | 4 | 5
    -----------
     6 | 7 | 8
    """

dissolved

Verifying that +dissolved is my blockchain ID. https://onename.com/dissolved

dissolved

dissolved

Data Source Information

This CSV file was created using Google interactive query interface BigQuery to access the Github Archive. The query used to generate this file is:

SELECT
  repo.name,
  COUNT(repo.name) AS total_events,
  SUM(CASE WHEN type = 'CommitCommentEvent' THEN 1 ELSE 0 END) commit_comment_count,
  SUM(CASE WHEN type = 'CreateEvent' THEN 1 ELSE 0 END) create_count,
 SUM(CASE WHEN type = 'DeleteEvent' THEN 1 ELSE 0 END) delete_count,

dissolved

Keybase proof

I hereby claim:

• I am dissolved on github.
• I am dissolved (https://keybase.io/dissolved) on keybase.
• I have a public key whose fingerprint is 00FB 9059 26D3 37B8 14BF 85F2 08EE 8911 FBE1 DD2A

To claim this, I am signing this object: