When you say “scripting language” these days, most programmers think of Perl, Python, Ruby, PHP, ASP, or JavaScript. But the history of scripting languages starts much earlier than any of these.
Code-commenting is so basic and so universal that every programmer, regardless of the language that they practise, thinks that they know all there is to know and that their way is the only sensible approach (I am no different in this respect). I guess that’s why there are so many blog postings offering advice on commenting (you can add this one to the list).
Over the past two years, I've written numerous articles as part of The Agile Developer column. Most of these articles have been focused, specialized pieces explaining an agile practice or team dynamic that helps increase agility. Throughout, I've always shared a small piece of my agile development experience, occasionally cross-referencing the material. Until now, however, I haven't shared insight to how everything fits together.
As the New York Times has noticed, big corporations are starting to get with the web work program. But they’re mostly doing it in a big corporation sort of way, with fancy (and expensive) telepresence systems. While this approach may indeed offset the rapidly-rising price of travel, those of us who are long-term web workers may roll our eyes at this narrow-minded perception of the best way to remotely work.
The question came up in the ALT.Net group, and it seems like a good idea to post my thought about it. You can see my overall default design for most just about any system. No, this isn't the end all be all design dogma, it is just something that has served me well in a wide number of applications. This architecture has only one thing at its code, it is focused on clearly defining responsibilities between different parts of the application.
know, Ruby languages always fascinated you with many of its great features and Rails always added, lots of smile to it.
Its time to smile more with IronRuby, for various reasons
Today Firebug Lite 1.2 was released. This new version was built by Azer Koçulu, creator of pi.debugger. Azer joined the Firebug Working Group, morphed the GUI to look like Firebug, and added it to the Firebug code base.
I built a loop benchmarking test suite for different ways of coding loops in JavaScript. There are a few of these out there already, but I didn't find any that acknowledged the difference between native arrays and HTML collections. Since the underlying implementations are different (HTML collections for example lack the pop() and slice() methods), benchmarks that don't test against both are probably missing important information.
Apress's newest Django offering, Practical Django Projects by James Bennett, weighs in lightly at 224 pages of actual tutorial content, but trust me, they're dense pages. Filled with pragmatic examples which directly address the kinds of development issues you will encounter when first starting out with Django, this book makes an important addition to the aspiring Django developer's reference shelf. In particular, the book's emphasis on demonstrating best practices while building complete projects does an excellent job of accelerating an understanding of Django's most powerful features — in a realistic, pragmatic setting — and which a developer will be able to leverage in very short order.