Category: Uncategorized

Click the photo to see it at full size.

Pictured above: Josh Burke explaining a few of functional programming’s cornerstones at Burlington Code Academy, using a graphic I made a couple of years ago…

It’s based on a tweet by Steven Luscher:

Map/filter/reduce in a tweet:

map([🌽, 🐮, 🐔], cook)
=> [🍿, 🍔, 🍳]

filter([🍿, 🍔, 🍳], isVegetarian)
=> [🍿, 🍳]

reduce([🍿, 🍳], eat)
=> 💩

— Steven Luscher (@steveluscher) June 10, 2016

The graphic got to this class by way of Googler Addy Osmani, who was contacted by Burlington Code Academy co-founder Alex Chaffee about using it in a class. Addy pointed Alex to me and Steven, and we both gladly gave our permission — although really, it’s Steven’s creation; I just turned it into a graphic.

Here’s the Alex’s tweet of the graphic in their class:

😍
(@High_Rigour teaching it tonight while I edited slides in the back of the classroom) pic.twitter.com/5vGx3EdBYz

— Alex Chaffee (@alexch) February 20, 2019

I didn’t want to stop at just making a graphic based on Steven Luscher’s tweet — I wanted to build on it by making it real! So I implemented these emoji functions in Swift…

// Map

func cook(_ item: String) -> String {
  let cookupTable = [
    "🐮": "🍔", // Cow face -> burger
    "🐄": "🍔", // Cow -> burger
    "🐂": "🍖", // Ox -> meat on bone
    "🐷": "🍖", // Pig face -> meat on bone
    "🐽": "🍖", // Pig nose -> meat on bone
    "🐖": "🍖", // Pig -> meat on bone
    "🐑": "🍖", // Sheep -> meat on bone
    "🐐": "🍖", // Goat -> meat on bone
    "🐔": "🍗", // Chicken -> poultry leg
    "🦃": "🍗", // Turkey -> poultry leg
    "🐸": "🍗", // Frog  -> poultry leg (no frog leg emoji...yet)
    "🐟": "🍣", // Fish -> sushi
    "🐠": "🍣", // Tropical fish -> sushi
    "🐡": "🍣", // Blowfish -> sushi
    "🐙": "🍣", // Octopus -> sushi
    "🍠": "🍟", // (Sweet) potato -> French fries
    "🌽": "🍿", // Corn -> popcorn
    "🌾": "🍚", // Rice -> cooked rice
    "🍓": "🍰", // Strawberry -> shortcake
    "🍂": "🍵", // Dried leaves -> tea
  ]
  if let cookedFood = cookupTable[item] {
    return cookedFood
  }
  else {
    return "🍽" // Empty plate
  }
}

let cookedFood = ( ["🐮", "🍠", "⚽️", "🐔", "🌽"].map { cook($0) } )
// cookedFood == ["🍔", "🍟", "🍽", "🍗", "🍿"]


// Filter

func isVegetarian(_ item: String) -> Bool {
  let vegetarianDishes = Set([
    "🍟", // French fries
    "🍿", // Popcorn
    "🍚", // Cooked rice
    "🍰", // Shortcake
    "🍵", // Tea
  ])
  return vegetarianDishes.contains(item)
}

let meatFree = ["🍔", "🍖", "🍟", "🍽", "🍗", "🍿", "🍰"].filter { isVegetarian($0) }
// meatFree == ["🍟", "🍿", "🍰"]


// Reduce

func eat(_ previous: String, _ current: String) -> String {
  let qualifyingFood = Set([
    "🍔", // Burger
    "🍖", // Meat on bone
    "🍗", // Poultry leg
    "🍣", // Sushi
    "🍟", // French fries
    "🍿", // Popcorn
    "🍚", // Cooked rice
    "🍰", // Shortcake
  ])
  if (previous == "" || previous == "💩") && qualifyingFood.contains(current) {
    return "💩" // Poop
  }
  else {
    return ""
  }
}

let aftermath = ["🍔", "🍟", "🍗", "🍿"].reduce("", combine: eat)
// aftermath == "💩"

…and they’re in a Swift playground, which you can copy from this Gist or download here.

My thanks to Steven Luscher for starting the whole thing, Addy Osmani for helping make the connections, and Alex Chaffee and Josh Burke for using the graphic! I’d also like to thank everyone involved for helping to make map, filter, and reduce easier to understand for new programmers — they can be strange concepts at first.

For those of you who enjoyed “Conference call bingo” from yesterday’s collection of links, here it is, rendered as a bingo card from days gone by. Looking at it, you can almost smell the cigarette smoke!

Over the past few years, I’ve managed to accumulate a ridiculously large backlog of links that I’d been meaning to blog about here on Global Nerdy. It’s time for me to do some spring cleaning, so from time to time, you’ll see these posts where I unload the links that are still good, both in the sense of still being online and still being valid and useful. Enjoy!

You may also want to see this earlier collection of links.

Things I Was Unprepared For As A Lead Developer (September 7, 2017)

Here’s Pascal de Vink at WebCamp Zagreb (2017) talking about the non-coding things that a lead developer does: delegating, culture building, mentoring, planning, meetings, dealing with upper management, and more.

On company culture

• It’s not an asshole problem — it’s a bystander problem (December 31, 2014): Cate Huston writes that the real problem that women in tech face isn’t the assholes, but the bystanders, who allow the assholes to continue with their ways.
• Ten unmistakable signs of a fear-based workplace (March 7, 2017): If you haven’t worked at a place where management practices rule by fear, consider yourself fortunate! Here’s how you spot these places before you get trapped in one — go and read the full article, but here’s my quick summary of those 10 signs:
  1. Everyone’s focused only on their immediate goals.
  2. Managers and HR specialize in assigning work, measuring results, punishing infractions and maintaining order.
  3. People are afraid to tell the truth because they already know no one wants to hear it.
  4. All people talk about is who’s in management’s “good books” and “bad books”.
  5. Employees wonder if they’ll have a job next week.
  6. Following rules and avoiding blame are top priorities.
  7. Managers pay lip service to collaboration and out-of-the-box thinking, but no one takes them seriously.
  8. Employees disappear without warning.
  9. It’s not the smartest and most capable employees who get promoted — it’s the ones who most wholeheartedly embrace the fear-based culture.
  10. No humor or humanity.
• In 2017, your internal culture is your brand (August 7, 2017): Written not long after James “Google Manifestbro” Damore wrote his terrible (and justifiably career-limiting) screed, this article explains that a company’s culture is now the story it tells about itself to the outside world.

The software developer’s sketchbook (January 1, 2015)

James Hague suggests that one of the problems with working on a few big projects is that this approach limits your expertise: “Someone who does roof work on fifty houses a year looks a lot more the expert than someone who needs two years to ship a single software project.”

To counter this, he suggests that developers could start building up a sketchbook, the way artists and crafters do:

This sketchbook of implemented ideas isn’t a paper book, but a collection of small programs. It could be as simple as a folder full of Python scripts or Erlang modules. It’s not about being right or wrong; many ideas won’t work out, and you’ll learn from them. It’s about exploring your interests on a smaller scale. It’s about playing with code. It’s about having fun. And you might just become an expert in the process.

The Programming Talent Myth (April 12, 2015)

In his keybote at PyCon 2015, Django co-creator and Heroku Director of Platform Security Jacob Kaplan-Moss describes himself as “At best, an average developer”. He talks about the myth of the “10x programmer” and how the dichotomy between the rock star programmer and the “average” developer is a false one.

Also worth checking out:

• In Praise of the Average Developer (May 8, 2015): An article inspired by the talk above.
• You are not a 10x developer (September 23, 2013): This article says that yes, 10x developers exist, but that’s largely because all human talent — from number of academic papers published, to Emmy nominations, to NBA career points, and yes, even programming — follows a power law distribution that looks like this:…which makes all but a very fortunate few below average.
• The mythical 10x programmer (February 28, 2017): Read this for the list of qualities that you can try to cultivate to be a more productive programmer.

The Myth of the Genius Programmer (Google I/O 2009):

Conference call bingo (September 19, 2017)

Found via Amy Wilson: