Fail Forward!

[...] I change?" Ugh! Why should you look at other languages and frameworks? Because most web applications that are developed in Java are wasteful! Nine hundred and ninety nine web applications out [...]

[...] As someone who has been living in the Java world when it comes to developing web applications, development times have always been ridiculously long. Cycles spent figuring out what should [...]

[...] we did not evaluate other languages/architectures that may be more suited to developing a web application. Groovy on Grails, Ruby on Rails, Python/Django, et al. Because developer preconceptions got [...]

[...] I have been involved in enterprise level Java web application development for the better part of a decade at this juncture. I have deployed applications in [...]

[...] the Rails framework. It's one of the most amazingly productive frameworks for designing your web application, and despite rumors, scales perfectly well. Assuming you know how to write scalable code. [...]

[...] it Matter? I have run across an awful lot of JavaScript code that was clearly written by a Java developer. Over architected and excessively complex code which takes hundreds of times the CPU cycles [...]

[...] requires a certain amount of drive. It's not something you can dabble in. You either are a Java developer or you aren't. You know it or you don't. While that may be a boon in some cases, it can [...]

[...] JavaScript with syntactic sugar: CoffeeScript, Dart, TypeScript... Pretty impressive for a dynamic language! It can be a little scary jumping in to a new pool of knowledge, even if some of your old [...]

[...] , I thought for a very long time that it was going to be almost impossible to go back to a dynamic language, due to how poorly written "all dynamic code" was. Due to my experiences with Perl [...]

[...] and aspect oriented programming. Many of which are a direct result of the need for more dynamic language features in the code. That's just one big code smell. If you want a dynamic language, why [...]

[...] . Something on top of JavaScript to enforce standards and make things more readable. Yes, it's syntactic sugar on top of JavaScript. That's a good thing. JavaScript is half-baked and half-readable- [...]

[...] on top of JavaScript to enforce standards and make things more readable. Yes, it’s syntactic sugar on top of JavaScript. That’s a good thing. JavaScript is half-baked and half-readable- [...]

[...] my predictions of CoffeeScript. There are more options than ever for writing JavaScript with syntactic sugar: CoffeeScript, Dart, TypeScript... Pretty impressive for a dynamic language! It can be a [...]

[...] choose the right materials, tools and techniques. You have to plan in advance. You have to make trade offs about durability, flexibility, and all the other -ilities. Most web sites out there require [...]

[...] code quality. Slower coding rate. Domineering personalities vs submissive ones. It's about the trade offs and being honest with yourself. I found that this particular style of development was not for [...]

[...] than 8gb in memory... I still look back and shake my head. Asynchrony is pure win, but has its trade offs. It comes at the cost of comprehension. It can be harder for the developer to reason through, [...]

[...] of them are trying to drag other paradigms in to the JavaScript world, rather than forcing good JavaScript practices from the very beginning. Things such as appropriate scoping have often alluded even [...]

[...] of them are trying to drag other paradigms in to the JavaScript world, rather than forcing good JavaScript practices from the very beginning. Things such as appropriate scoping have often alluded even [...]

[...] -baked and half-readable- CoffeeScript will make life easier while we're waiting for the next big script level to get to where we can use it regularly (which I'm guessing at somewhere around 2016). [...]

[...] half-readable- CoffeeScript will make life easier while we’re waiting for the next big script level to get to where we can use it regularly (which I’m guessing at somewhere [...]

[...] a production app with it. Stay tuned for my next post: How Java and Ruby made me a better Node developer. [...]

Herein is a partial recounting of the bits and bobs that I have learned passing through different programming languages. Principles and processes that [...]

[...] from the very beginning. Things such as appropriate scoping have often alluded even strong JavaScript developers for a long time. With the advent of CoffeeScript, it makes JavaScript "feel" [...]

[...] from the very beginning. Things such as appropriate scoping have often alluded even strong JavaScript developers for a long time. With the advent of CoffeeScript, it makes JavaScript ”feel& [...]