Explore >> Select a destination
|
You are here 
|
blog.nojaf.com | ||
| | | | |
www.softdevtube.com
|
|
| | | | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | |
| | | | |
www.thepolyglotdeveloper.com
|
|
| | | | | I'll be speaking at the Android Developer Conference (AnDevCon) in Santa Clara, California in December 2015. Check it out to learn cool Android tricks. | |
| | | | |
adamsilver.io
|
|
| | | | | Cool front-end developers are always pushing the envelope, jumping out of their seat to use the latest and greatest and shiniest of UI frameworks and libraries. However, there is another kind of front-end developer, the boring front-end developer. Here is an ode to the boring front-end developer, BFED if you will. | |
| | | | |
lincolnmullen.com
|
|
| | | Recently I've been writing a fair bit of code in Go for a project I am working on. There is a lot to like about the language. But the thought occurred to me that maybe I like Go because it fits my (unjustifiably) beleaguered sense of self. If I used to like Ruby because it was fun, then maybe I like Go now for these reasons: Go is a minimalist language. I would prefer that we just get down to work without any fuss. Go is a high performance language for concurrency. There is too much to do and it all has to be done at once, so I guess we better do it quickly. Go is strongly typed. Please tell me what you expect up front, then stick to it. Go makes you check for errors explicitly (if err != nil). Bad things will inevitably happen, so I guess we better plan for them up front and do our best to deal with them. | ||
