Continuing my recent theme of utilities and the like that I can’t do without…
For as long as I’ve been programming, I’ve built up a junk drawer of useful functions that I carry from project to project. The Ruby iteration of this is currently implemented as a Rails plugin that is one of the first things I add to each new project.
Here are a few of the utensils that I keep jammed in the back of the drawer.
Read more »
Today I gave a presentation on why Git makes sense for an agile consultancy like ours. It was more challenging than I initially imagined; there are many, many blog posts out there discussing why Git is technically superior to Subversion. But when I searched for posts discussing the business merits of Git I came up short. Git is faster, branches better, it has a local copy of the repository, it’s small and cheap, but these are points that sell an engineer. What sells the administrators, the business analysts, the project managers?
I came up with a few cool scenarios to illustrate why we, as a business, should adopt Git — essentially, why it makes not only my life easier, but why it will make the decision makers incredibly happy too. Then my colleague Jason Sendelbach and I gave a short talk on not only the why of the Git, but how we can start using it. Here I’ll summarize our presentation. If you want to use Git in your company, but you have problems selling it to the administration, feel free to crib liberally. These points worked great for me.
Read more »I like it. Give me more browser improvements! With the news of Firefox 3.1′s JIT JavaScript beasty TraceMonkey, is it too much to hope that IE8 Beta 2 has some similar improvements under the hood?
First you have to find the appropriate page among the 300 or so flogging IE8 Beta 2 in the MS redundaverse. Drilling down into performance, you find the terse:
…the script engine in Internet Explorer 8 is significantly faster than in previous versions, minimizing the load time for webpages based on JavaScript or Asynchronous JavaScript and XML (AJAX).
OK. Faster. Faster how? How much faster?
It used to be that JavaScript engines were so slow that benchmarks served mostly to show that they weren’t suitable for anything serious (slow and slower). It’s time for some head-to-head benchmarks. Stay tuned.
I was expecting the next major advance in JavaScript for Firefox to come from replacing SpiderMonkey with Tamarin, Adobe’s donated VM for ECMAScript 4. In fact, Tamarin can already do some JIT.
Now surprise, surprise — SpiderMonkey can do JIT as well, as Brendan Eich, Mozilla’s CTO describes in his blog. The technique used in both Tamarin and SpiderMonkey is called tracing, where during code execution, each hotspot (code that is executed a whole lot) is traced and compiled, so the next time it is executed, the compiled version is used. The beasty is called TraceMonkey and boasts several orders of magnitude improvements over the old SpiderMonkey.
Since this JIT involved actual compilation, you have to look at which architectures TraceMonkey supports. Again from Brendan’s blog:
We have, right now, x86, x86-64, and ARM support in TraceMonkey. This means we are ready for mobile and desktop target platforms out of the box.
Sweet. I guess that means the Intel Macs are supported.
There are still some bugs, of course, but this is great news for sophisticated Ajax apps on Firefox. Will Microsoft respond? Is a JavaScript JIT upgrade in the works for IE? This is an arms race I can get excited about.
Update: John Resig of JQuery has some more details and demos about TraceMonkey.
In last week’s post, I introduced the linked multiselect widget I was asked to implement on a tight deadline for an unexpected project assignment. I showed some demo code in action and discussed the user experience issues that shaped my requirements. This week, I’ll walk through the actual code – or at least my first pass at it.
Like a lot of developers who should know better, I sometimes shirk the technical design phase on quick projects, then regret it later. The code I handed off for this project got the job done, but it wasn’t very DRY or elegant. Luckily, I’ve continued to refine it into something I’m not ashamed to blog about. Next week, I’ll show off the final, refactored code and try to draw some conclusions about the entire experience. But first – the original, unrefactored code:
Read more »Can we talk about REST?
It’s been about two years since the Simply RESTful plugin was added to Rails edge core, in that time I think I’ve learned the following two things:
I think you are going to have one of three responses. I’m betting on the middle one:
So here’s where I get into RESTful trouble…
Read more »
This example covers how to build a simple 360 degrees gauge Flex component. It has public properties that allow you to easily adjust the appearance of the component for colors, size, font size, guideline thickness and such. It also fires a custom “angleChanged” event that helps you integrate it with the rest of your app.
Read more »
Today on the program, I’m going to discuss a few Rails development tools that I’ve had the pleasure of using recently.
If you’re like me, you like starting paragraphs with the phrase “if you’re like me”. You also used to use the TextMate footnotes plugin, then got frustrated with it in the Rails 2.0 timeframe when it didn’t get updated for a while. Every now and then you’d sigh, and remember the days when you could click on a stack trace in your browser and open the associated file.
Read more »
Last week I spent a couple of days lashing together a UI widget for a project that needed a little Ajax assistance. As always, I looked for an opportunity to learn something along the way, so I got signoff on using jQuery and some plugins I hadn’t previously employed.
The result? A down-and-dirty mini-project that let me test drive Color Animations, jqModal and Low Pro for jQuery while employing tried-and-true solutions such as jQuery Templates and Live Query. What’s more, the requirements for the widget itself left room for some careful consideration of user experience design.
In the end, I built a client-side demo in just a few days and handed it off to the project lead for integration with a complex back end. Now I’m free to refine my deadline-constrained code into something a little more OO and share the results.
This week, I’ll talk about the project’s complex usability requirements and Pathfinder’s user-centered solution to those requirements. Next week, I’ll walk you through our first pass at building custom code, roping in open-source libraries and making it all work together on a tight deadline. Finally, I’ll walk you through the refactoring process so you can see the final, properly factored and reusable version.
Read more »
(Image comes from the Rails Envy MVC public service announcements — and I hope they don’t mind)
Here’s the question:
And the followup:
This is part of the standard phone screen we give to potential Rails developers. The expected answer goes something like this:
MVC stands for Model, View, Controller, each of which represents a section of the application. The model manages data and often persistence, the view manages presentation, and the controller mediates between user actions and associated models and views. Each of these three subsystems should have as little interaction with the others as possible. Complex business logic should go in the model, since that is the section that deals with business objects.
If your doing a phone screen with us after this, at least have the decency to phrase that in your own words…
I don’t think of that as particularly controversial, although I suppose you could pick at the wording and details to taste. Interestingly, or oddly, or something, the recent stretch of phone interviews has had a nearly unanimous answer to the followup question: Controller (sometimes, to be fair, the answer would be controller and model, but with controller as the primary answer).
After a brief time-out to check my sanity and calibrate with some other people (like the video with guys from the picture), I came out of the process with the following few thoughts:
Read more »
