Introduction Take a look at the following piece of code. Whats wrong with it? myAwesomeFunction = (objects) -> isGreat = false for item in objects if not item.isImportant continue if item.isGreat isGreat = true break return isGreat Does it go through all the items? No but, man, is that break on the last line easy [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/wmfLXJfDv8U/

Introduction Take a look at the following piece of code. Whats wrong with it? myAwesomeFunction = (objects) -> isGreat = false for item in objects if not item.isImportant continue if item.isGreat isGreat = true break return isGreat Does it go through all the items? No but, man, is that break on the last line easy [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/32_9hPjlifA/

One of the many frustrations things about developing extensions for Internet Explorer is that certain seemingly essential capabilities are completely lacking. For example, you can see the headers being send with an HTTP request using the BeforeNavigate2 event. But you cant modify the headers. Whats more, this event is only received for page or frame [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/DidZ5-McV8w/

One of the many frustrations things about developing extensions for Internet Explorer is that certain seemingly essential capabilities are completely lacking. For example, you can see the headers being send with an HTTP request using the BeforeNavigate2 event. But you cant modify the headers. Whats more, this event is only received for page or frame [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/0-OXYnF7jmQ/

Heres a confession  over time I have come to like services that expose their data via a RESTful API. Its scalable, its understandable and quite importantly  its elegant. Working with REST is a breeze, right? Well, a few weeks ago, I found myself facing a rather mundane task  retrieving all the information about [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/kFUaaTWc7Lg/

Heres a confession  over time I have come to like services that expose their data via a RESTful API. Its scalable, its understandable and quite importantly  its elegant. Working with REST is a breeze, right? Well, a few weeks ago, I found myself facing a rather mundane task  retrieving all the information about [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/3WTtQ6-CUVQ/

My natural inclination is to be skeptical of anything billed as a software development methodology. I still remember my early years as a professional developer in France in the early 902s when the Merise methodology was ubiquitous. To me it seemed like an excuse to spend tons of time on process documentation and other bureaucracy [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/7fCS1y3fBNU/

My natural inclination is to be skeptical of anything billed as a software development methodology. I still remember my early years as a professional developer in France in the early 902s when the Merise methodology was ubiquitous. To me it seemed like an excuse to spend tons of time on process documentation and other bureaucracy [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/7J1jjlhNyyY/