erratic

hoe, factory girl, rack, naked_rack, deepthroat, punch, shnork, rubbr, beer, pony, strap-on, cheeba, babygitter, backnob, badger, syckle, birdfeed, hosebird, grackle, hammock, sunspot, birdie, hubris, corrupt, gambler, paranoia, peeping, statwhore, slubydoo, slug, crack, ragweed, wee, grudge, inquisition, honkster-jelly, harker, tinkerbell, jacker, mockery, bullshit, i_dont_give_a_shit, monkey_shield, biomass, ass, massive-nancy, sassafras, clingwrap, scraper, castronaut, feedbag, bullet, snailgun, railgun, cap_gun, railgun, shotgun, punch, throat-punch, one_inch_punch, puny, shadow_puppet, hightimes, tadpole, hobosupport, runt, fugit, stammer, curly_mustache, rasta,crazy_ivan, floobs, loofah, boogaloo, mole, syrup, featherdust, grit, crow, pangea, panda, sunspot, japanese_av_actress, hurl, watcher, obsidian, glue, disguise, needle, junebug, jungle, petticoat_junction, juggernaut, jello, honkster-jelly, wizardly, crocodile, stump, burn, fire-hydrant, homeschool, fast_hammer, dutchfaker, fabricator, facade, fattr, profanalyzer, masochism

Got this error when loading a rails site served under my local apache" I updated my passenger gem and regenerated the apache passenger module, updated the httpd.conf at it was all good after that.

rspec controller specs: YourClass.should_receive(:find).with() really cares about argument order and does not accept a hash of values where the params[:key] is named like the key in the hash key => value so: Yes, I know about hash_including(). For some reason it failed because ":action => '_controller_action_', :only_path => true" was being included in the with() arguments hash and it made the should_receive fail - even though hash_including is supposed to deal with this. It may be a rspec_rails thing. I have not dug into the rspec code very deep to see what I was doing wrong or if it's a bug or if the universe just hates me.

In irb: get a listing of files/sym/hard links in my home directory

In ruby script: Return the result of a command line operation. Without back-ticks ruby will just return true or false from the exit of the issued command. [wikipedia backticks - computer related]

Ruby Docs have massive amount of info about ERRNO (whatever the fuck it is - i'm guessing errors and such but haven't learned it yet). These error objects matter greatly and I think ruby has them wrapped up in a rubish way, but as I said I'm ignorant at the moment. I guess there is shorthand for error objects: $! - last exception; $@ - backtrace; There are many more of these. (whimper!)

Oh boy do I suck like a black hole. My bird flu typo theme had some major issues in the default.rhtml. So if you've downloaded it grab it again and trash the old one. Now Working: RSS Feeds; ajax comments; ajax admin menus...

Error handling in rails is very technical. The TextMate Backtracer Plugin has been invaluable to me in my development in recent days, yet it only gets me to the file(s) when something is amiss in the code.

Building and running tests is one way of confirming the functionality of your application, and I’m learning the power of good testing, be it quite slowly and with a lot of errors.I’ll get there.

Here is a short list of things I had to consider when flopping from code to browser during development and things kept blowing up in my face:

• Ruby/Rails has RESERVED WORDS. If you have a class/table that isn’t playing nice make sure you aren’t naming it with one of these. This is tantamount to pouring sugar in your gas tank. And then driving in reverse at full speed. While wearing a blindfold. With your hair on fire.

• Column names in your tables need to change with alterations to any class/model names, as well as any has_many/belongs_to associations along with any model inclusions in your controllers. If you’re not to invested in the code it’d probably be easier to regenerate a fresh app with the correct model/controller name. Running ./script/destroy (the arch nemesis of ./script/generate) can help in crime scene clean up, but you still have all those pesky symbols/variables/methods with the poison name throughout your app patiently waiting to spurt their demonic ire. Exterminate them with aggression.

• An objects information will carry from request to request in the session but you still have to stuff it into an instance variable inside whatever controller method is being called upon. I have a tingling sensation in my unmentionables that suggests session customization and databases can smooth out this bumpy road, but this strains the withering tethers of my sanity upon contemplation. I can only learn so much each day.

• Getting compile errors means you’re trying to bake a duck with a hammer on a string in a pail of kittens. It won’t work. Ruby/Rails doesn’t know or particularly care what you are trying to do, but how you are going about doing whatever it is you are trying to do will never, ever work no matter what. Get rid of whatever you added since the last time it worked and try again. Remember when you went to grandmas house and you had to take off your shoes and you weren’t supposed to go out into the field because you’d get muddy? Yeah, Rails has grandma rules that sometimes take all the fun out of life and make your feet cold.

Throwing away code is a part of development, just as throwing away designs is a part of being a designer. Having the willingness to let go of what’s not working makes room for what will. Even if what that is is nowhere to be seen at the moment.

Cleverness makes me giddy. When you can't innovate - imitate! idiotis.ms Cleverness or me-too fanboy wanna be like the cool kids chaff? In any case it is deliberate and useful to at least one person.

I have models and controllers and database tables and :has_many and :belongs_to all tying it together with ActiveRecord but I wanted to take one column of data from each row that was related to one of my other models through a has many relationship. Boy did I make it a lot harder than it needed to be.

Every time I challenge the silicon gods by installing yet another demanding software package on my powerbook G3 I always start by consciously dismissing the age and condition of the laptop. The machine is 6 years old, has 386mb of ram, a 9 gig hard drive, a 500mHz processor, and a first generation airport card. After installing tiger and developer tools there is a little under 2gb of disk space left.

There is a ghost impression of the keyboard etched into the surface of the LCD screen from the oil left on the keys by my fingers. I have dropped, sat on, stepped on, rolled over, spit on, slammed shut, forced open, poked, prodded, wedged, and pried loose this poor machine during the 6 years, 2 SXSW’s, many business trips, not as many vacations, and 6 operating system upgrades of it’s life.

Every time I do something beyond surf the web on grandpa pismo and it doesn’t start smoking or tell me to hold the power button down in 5 different languages I experience a trepid euphoria not unlike that experienced by a man who only hears the metallic click of the firing pin during a game of russian roulette.

Around minute 30 of hour 2 of installing mod_ruby using darwin ports (just to see if I could) I started to get nervous. I was using a wireless connection, the elderly (original) battery was at 50% and sinking and I was having a hard time staying awake. it was 2:30 a.m. which is actually 3:30 am to my internal clock seeing as we’re only a few days in to the daylight savings time switch.

Being the dedicated, task focused person I am I… fell asleep.

I have yet to assess the outcome of this latest haphazard command line escapade.