| 1. Monolithic applications and architectures can vary in their monolithness. This is an under-specified description. | |
| 2. Microservice applications and architectures can vary in their microness. This is an under-specified description. | |
| 3. Microservices and monolithic architectures have both benefits and disadvantages. | |
| 4. Organizations will exploit those benefits while working around any weaknesses. | |
| 5. Success of the business is a large influence on the exploitation of benefits and implementation and costs of workarounds. | |
| 6. All benefits and work arounds are context-sensitive. Meaning that they are both technically and socially constructed by the organization that navigates them. | |
| 7. Path dependency is a thing. History matters and manifests in these architectural decisions and evolution in an organization. | |
| 8. Patterns exist to inform practice, not dictate it. Zealous adherence to an architectural pattern brings peril when it is to the exclusion of cultural context in actual practice. | |
| 9. Architectural patterns w |
For iPhone app developers. Emphasis on getting the fastest app store approval. Everything stated as suggestion made into an imperative. When "violating" these imperatives, you can check for yourself what the caveats are. Generally speaking, deviating will more likely cause your app to be hung up in approval.
You can read this entire document in about 20 minutes. This is faster than reading and understanding the entire Human Interface Guidelines.
| diff -r 9bfe12150c5e include/draw.h | |
| --- a/include/draw.h Mon May 05 22:28:03 2014 -0400 | |
| +++ b/include/draw.h Fri May 16 13:31:14 2014 +0200 | |
| @@ -54,6 +54,13 @@ | |
| #define DGreyblue 0x005DBBFF | |
| #define DPalegreyblue 0x4993DDFF | |
| #define DPurpleblue 0x8888CCFF | |
| +/* Custom colors */ | |
| +#define ZGrey 0x444444FF | |
| +#define ZLightGrey 0x999999FF |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
This document is a collection of concepts and strategies to make large Elm projects modular and extensible.
We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:
| """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" | |
| " Set leader key & Python bin " | |
| """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" | |
| let g:python3_host_prog = '~/.virtualenvs/neovim/bin/python' | |
| let g:python_host_prog = '~/.virtualenvs/neovim.old/bin/python' | |
| let mapleader="\<Space>" | |
| """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" | |
| " vim-plug " |
| Lightning talk on PyCon 2013: | |
| http://www.youtube.com/watch?feature=player_detailpage&v=1vui-LupKJI#t=975 | |
| Boston Python Meetup (January 2013) | |
| http://www.youtube.com/watch?v=ulekCWvDFVI | |
| PyCon Canada 2013 | |
| http://www.youtube.com/watch?v=n8i2f6X0SkU | |
| PyCon France 2013 |
| HTTP status code symbols for Rails | |
| Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings. | |
| Status Code Symbol | |
| 1xx Informational | |
| 100 :continue | |
| 101 :switching_protocols | |
| 102 :processing |
A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."
