My co-worker (Jeff) and I were discussing the disparity between people who say “LOL” in IM but are, in fact, not laughing out loud. He suggested that it was really laughing internally loudly, so I suggested LiL. I then told him that when I do so, I am laughing uproariously in the machine world.
Jeff then coined this term: LUITMW. Go forth and copy Interwebs!
Being health-conscious in 2009 apparently boils down to saving yourself from H1N1. Since many health efforts are rooted in fear of H1N1, I’m saying that Google is the new H1N1 plan. Substitute H1N1 for health in this Dilbert comic: http://dilbert.com/2007-02-18.
While discussing recent physics work that involves quasiparticles and the apparent observation of magnetic monopolism with Chris Arnold, I thought it was appropriate to reduce the description of said research to “near-zero-K quantum voodoo”. It seems quite appropriate.
Source: http://physicsworld.com/cws/article/news/40302
I came up with an idea this afternoon for a source code visualizer for Enterprise solutions. Basically it would provide a source code cloud built from files and their dependencies. Each cloud would be a logical block (function, if-statement, loop, etc.) and the user would be able to zoom in/out to any level as needed. You would then work on an application as a whole rather than on a set of files. Everything would still be saved out to standard files, but the entire application would be accessible in a visual manner that wouldn’t require lots of commands to open and close said files.
Basically I want to be able to quickly move between parts of a project using the Mac OS X Expose feature, but without subjecting myself to Mac OS X. I also want seamless integration with VIM. CloudVIM if you will…
The app would also tie into another idea I had a while back: multi-history versioning for files. Basically I want to be able to view the state of a file at any given point during my editing session, even if that means branching into multiple edit histories. Combining these ideas into CloudVIM would allow a developer to easily navigate to any source code at any time within a specified timespan. Coupled with SVN for storage this would provide a powerful debugging model I think.
We need a good use for 1TB hard disks anyway.