Explore >> Select a destination
|
You are here 
|
jayperry.works | ||
| | | | |
blog.typekit.com
|
|
| | | | | ||
| | | | |
journaloulipo2014.wordpress.com
|
|
| | | | | Reblogged on WordPress.com | |
| | | | |
www.typewolf.com
|
|
| | | | | In response to Monotypes recent acquisition of FontShop, Ive created a list of the 24 best independent font foundries that Monotype doesnt own (yet). | |
| | | | |
enterprisecraftsmanship.com
|
|
| | | Hard coding is often considered an anti-pattern. Having values that can change over time hard-coded in the source code requires recompilation every time these values actually change. While this statement is true, I think that hard coding should be the default choice when developing an application. Hard coding vs configuration file When you work on a project or feature, there always are some magic numbers or strings that potentially can change in future. | ||
