Skip to content

Instantly share code, notes, and snippets.

View a-maas's full-sized avatar

Adam Maas a-maas

  • Custom Ink
  • United States
View GitHub Profile

1.3 The Act of Design

With the discovery and propagation of common design principles and patterns, all OOD problems would appear to have been solved. Now that the underlying rules are known, how hard can designing object-oriented software be?

Pretty hard, it turns out. If you think of software as custom furniture, then principles and patterns are like woodworking tools. Knowing how software should look when it’s done does not cause it to build itself; applications come into existence because some programmer applied the tools. The end result, be it a beautiful cabinet or a rickety chair, reflects its programmer’s experience with the tools of design.

1.3.1 How Design Fails

The first way design fails is due to lack of it. Programmers initially know little about design. This is not a deterrent, however, as it is possible to produce working applications without knowing the first thing about design.

@a-maas
a-maas / AAFAPI.rb
Created February 10, 2019 21:21
GraphQL AAF Team Roster from https://api.platform.aaf.com
require "graphql/client"
require "graphql/client/http"
module AAFAPI
# Configure GraphQL endpoint using the basic HTTP network adapter.
HTTP = GraphQL::Client::HTTP.new("https://api.platform.aaf.com/v1/graphql") do
def headers(context)
# Optionally set any HTTP headers
{ "User-Agent": "Tony Britt's Spotter Charts (spottercharts.com)" }
end