I’ve had the great pleasure of working with some other local Ruby developers to reignite NewHaven.rb over the last few weeks. Our second official event is a “Ruby, White, and Blue Hackfest” tomorrow, July 1st. It’s going to run from 6-9 pm at Blue State (the Wall St location). Everyone is welcome — don’t worry about skill level! You bring a laptop, we bring the community.
Right now, the plan is to get together and work on a few projects that group members are interested in, including our upcoming website. I’d also like to talk about what we should do for our next event.
I spent some time over the last few weeks pulling together lots of command line tools that I’ve written over the last few years. I’ve shared them on GitHub.
Some fill in gaps that I wish *nix systems would have by default (such as prune vs uniq or reverse vs rev). Others just script things that I do commonly or are just tedious to do (such as backups2git, github-init, timestamp, latest-migration-path, and std-timestamps). Some are just there for fun (such as is-computer-on). Most of them are written in Ruby, but some are plain old Bash scripts. Lots of the Ruby scripts make heavy use of ARGF, which is awesome for writting shell scripts if you’ve never used it.
I also spent some time documenting (and remembering) how they worked. (Most of it was just shuffling comments around.) Almost every command has a --help option that prints usage information and a short synopsis now. I hope you find them useful!
I’ve long been aware that “constants” in Ruby (i.e., variable names that are capitalized) aren’t really constant. Like other programming languages, a reference to an object is the only thing stored in the variable/constant. (Sidebar: Ruby does have the facility to “freeze” referenced objects from being modified, which as far as I know, isn’t an ability offered in many other languages.)
So here’s my question: when you re-assign a value into a constant, you get a warning like so:
I’ve been working hard on redesigning this site. You can see what it used to look like, above. It’s been a fun ride: I took this opportunity to learn more about HTML5 and CSS3. I’m pleased with what I’ve made. The result of my work is the custom WordPress theme you see now. I learned a lot in redesigning this site (mostly HTML and CSS, but a little PHP too). Over time, I’ll be rolling out some summaries of what I learned in blog posts.
Geek section: As it’s just a personal site, I’ve been experimenting with new HTML5 features and semantic tags, keeping the markup as minimal as possible, and applying visual effects only through CSS. As a result, there are very few images (all the gradients, shadows, rounded corners, and animation are pure CSS3) and the design degrades elegantly for older browsers. It even looks decent in the 9-year-old IE6. I’m preferring the new video and audio tags instead of Flash or other plugins as much as possible. The site even works (and looks) great on my iPhone. HTML5 and CSS3 still have problems, but the future of the web looks bright.
I also took the time to pull together some old content from other sites. There are still some gaps, but there are posts going all the way back to 2002. (I cringe a little reading some of it, but it’s interesting to see how much I have—and haven’t—changed.) Some posts have only been living on a hard drive for the last 8 years, but others have been on other services like Blogger. I’ve done my best to redirect links here.
Please let me know what you think in the comments.
This morning I was awoken by my alarm clock powered by electricity generated by the public power monopoly regulated by the U.S. Department of Energy. I then took a shower in the clean water provided by a municipal water utility. After that, I turned on the TV to one of the FCC-regulated channels to see what the National Weather Service of the National Oceanographic and Atmospheric Administration determined the weather was going to be like, using satellites designed, built, and launched by the National Aeronautics and Space Administration.
I watched this while eating my breakfast of U.S. Department of Agriculture-inspected food and taking the drugs which have been determined as safe by the U.S. Food and Drug Administration.
At the appropriate time, as regulated by the U.S. Congress and kept accurate by the National Institute of Standards and Technology and the U.S. Naval Observatory, I get into my National Highway Traffic Safety Administration-approved automobile and set out to work on the roads build by the local, state, and federal Departments of Transportation, possibly stopping to purchase additional fuel of a quality level determined by the Environmental Protection Agency, using legal tender issued by the Federal Reserve Bank. On the way out the door I deposit any mail I have to be sent out via the U.S. Postal Service and drop the kids off at the public school.
After spending another day not being maimed or killed at work thanks to the workplace regulations imposed by the Department of Labor and the Occupational Safety and Health administration, enjoying another two meals which again do not kill me because of the USDA, I drive my NHTSA car back home on the DOT roads, to my house which has not burned down in my absence because of the state and local building codes and Fire Marshal’s inspection, and which has not been plundered of all its valuables thanks to the local police department. And then I log on to the internet — which was developed by the Defense Advanced Research Projects Administration and post on Freerepublic.com and Fox News forums about how SOCIALISM in medicine is BAD because the government can’t do anything right.