Journal

As someone who steadfastly charges hourly for freelance work I try to avoid creating unnecessary code challenges for myself while in the design phase because when it comes time to code I'll either have to compromise the design or decide to put in extra un-billed hours because I want to solve the problem for personal reasons, but that would be bad business if I were doing freelance sites for a living rather than as a hobby to work on my design skills.

posted by Nils T. Devine  # 8:41 AM 0 Comments

posted by Nils T. Devine  # 8:18 AM 0 Comments

posted by Nils T. Devine  # 7:43 AM 0 Comments

posted by Nils T. Devine  # 2:34 PM 0 Comments

Location

From the 101, 7.9 miles up Kanan Road (becomes Kanan Dume Road at Mulholland Hwy) park right before the 3rd tunnel. Head west down the trail into the canyon.

Misadventure

This trail fucking kicked my ass. I walked the bike halfway back up out of the canyon sweating profusely. There are plenty of excuses, the heat, the washout from this spring's heavy rain, but it all comes back to that I'm horribly out of practice biking and horribly out of shape. Oh well, I'll get there.

I think I'd better go back to Las Virgines and Malibu Creek and get a little better at this biking thing before trying the Backbone Trail again.

posted by Nils T. Devine  # 6:58 PM 0 Comments

posted by Nils T. Devine  # 12:26 PM 0 Comments

"I can't reproduce the bug you entered. Clear your cache, you must have the old version of that javascript file."

I don't know how many times I've had to say this as a front-end developer. But the problem of cached outdated JavaScript files is only going to get worse as we get better at separating Structure from Presentation from Behaviour. And it's also worse when you are doing more frequent updates to a production environment (just a dream when it comes to secure apps, but maybe a possibility for ongoing development of internal-facing apps). The biggest problem is that users can't be expected to know how to clear their caches. Things will just break and magically fix themselves if the user even has the patience to wait around until their cached file gets updated.

I googled around and found a theoretical answer in a forum somewhere. Based on what I found here is the solution that Josh and I put into practice:

<script type="text/javascript" src="/js/webLibrary.js
?buildtime=@BUILD_TIMESTAMP@"></script>

...where @BUILD_TIMESTAMP@ is a variable to be replaced by the back-end language / build script of your choice. Here are the issues that this solves:

• Browser does not pull the JS file from cache when there has been a new deployment.
• Browser cache continues to function as it should in between builds (speeding up page loads)

posted by Nils T. Devine  # 12:11 PM 3 Comments

posted by Nils T. Devine  # 10:24 AM 0 Comments

posted by Nils T. Devine  # 8:35 AM 0 Comments

posted by Nils T. Devine  # 8:45 PM 0 Comments

posted by Nils T. Devine  # 8:58 PM 0 Comments

posted by Nils T. Devine  # 5:53 PM 0 Comments

posted by Nils T. Devine  # 10:36 AM 0 Comments

Line breaks, carriage returns, new lines, form feeds, whatever you might think of them as, browsers have their own ideas. I'm talking specifically about the character(s) produced when you hit Enter within a textarea and then try to manipulate the value of that textarea with JavaScript using regular expressions.

IE (internet explorer) on a PC

\r\n

Firefox (mozzilla) on a PC

\n

So, if you wanted to replace all the "line feeds" in a variable whose value was pulled from a textarea with a single space this is the code you would need:

val = val.replace(/\r\n/g," ");
val = val.replace(/\n/g," ");

On a related note, IE also has a funny idea about what character a single space is represented by when written to the page from a database (but not when typed with the space bar). If you want to strip out all of the spaces from a field in IE try this bit of hex:

val = val.replace(/[\xA0]/g,"");

That concludes this geeky interlude. Now back to our regularly scheduled nerdiness.

posted by Nils T. Devine  # 2:36 PM 0 Comments

posted by Nils T. Devine  # 1:38 PM 0 Comments

Had a dream about knot tying last night. Ok, so I'm a rather obsessive about the things I do; on the nerd side of geek. Today I digitized the knot book that I wrote in 1998-99 and uploaded them to flickr. I'll update this post as I add descriptions and category tags (bend, loop, hitch). I also plan to update the knots page on this site with highlights of the most practical knots and their applications.

So take a look at my photos tagged with "knot", but stay tuned for better organization and more information.

Update: I've updated my Knots Page to feature the best knots for a variety of purposes. But sorry, I still haven't done anything about improving the quality of the knot photos themselves. Someday I'll bust out the drawing tablet and the camera and do it all up proper like, but not today.

posted by Nils T. Devine  # 5:01 PM 0 Comments

posted by Nils T. Devine  # 10:17 PM 0 Comments

posted by Nils T. Devine  # 10:03 PM 0 Comments

I have nothing good to say about this lazy piece of rocking shit. Both of them. Probably designed by whoever did the C.

posted by Nils T. Devine  # 7:45 AM 0 Comments

posted by Nils T. Devine  # 7:39 AM 0 Comments

posted by Nils T. Devine  # 7:25 AM 0 Comments