Great, so now I have this whole new site with a fresh layout and an more efficient way of adding stuff. Why not make use of it. There’s often too many small things that I wouldn’t want to highlight or write as a single short blog post (what, me being short?! when has that ever happened?) so here I was thinking (yes, it happens, on occasion!) why not combine those small bits into a more regular update post. I can’t predict what these (hopefully) regular updates will contain but you’ll just have to wait and see. In this post; development bits, home office bits, photography bits, and some world news that’ll make you either laugh or shake your head.
My colleague Bruce just asked me why there weren’t any pictures from my home office versions prior to what I call “version 5”. Good question. Probably because the pictures aren’t too great and I don’t actually have all that many. I can’t even find a single decent (or indecent!) image from back in the earlier days of the office. But I did find a few older ones that predate the “version 5” so I’ve given them a nice little page of their own. Don’t ask me what the specs were on the systems that were there at the time since most of these date back to, I believe, between 1999 and 2001. So yeah, these are a decade old and most of them were shot with an Olympus E-10, one of the first digital SLR’s on the market back then. For those who pay attention, yes, there were still a fewAmiga’s around at the time but even in the 1999 period I didn’t use them. A friend once said I only used those Amiga’s to keep dust of my desks and in a way he was right about that. My use of Amiga’s died off sometime around 1991-1992.
I think Aware Bear Computer Repair (i.e. Andre Leite Alves) may have been pushed from its coveted number one position in the office thieves’ hall of shame by a company called Innovative Consulting Group (using the domain name groupiconsulting.com), founded and co-owned by the very unreliable and suspicious Ihtisham (Shami) Ul Haq. For the record, I have nothing to do with this fraudulent and illegally operating international ‘company’ called ICG, nor do I have any stake in any activity that either promotes, endorses, or encourages the outsourcing of software development (or any other such) activities.
When using the Mac along with the other systems I just pull it forward a little so it’s in easier reach. The little rolling desk was a recent addition because there just wasn’t any way I could fit a big 27″ screen into the current setup and doing an overhaul was not part of the plans I had, certainly not in the current space and certainly not in its current location. The next overhaul will be huge and will be “elsewhere”. Insiders will know what I’m talking about. Anyone else, you can just keep guessing what I mean by that.
Yes, it’s true. Get over it already. I bought an Apple Macintosh. A 27 inch 2.93Ghz Quad Core i7 with 8GB RAM, 1TB HD, and HD5750-1GB. I understand this has caused several people to exhibit signs of severe confusion because I’m really mostly known as a “Windows Guy” (more appropriately, a .NET guy). For a little while I’ll refrain from posting any pictures, though. Wouldn’t want people to die from either laughter or heart-attacks.
If you’ve ever needed to frequently rebuild multiple corridors in Autodesk Civil 3D because they are out of date but don’t want to go hit the rebuild menu item for each single corridor then here’s the solution. The following microscopic addon/plugin for Civil 3D 2010 allows you to rebuild all corridors or rebuild all out of date corridors, at once. Unzip the DLL to a location of your choice and you can use netload and load the Civil.RBC.dll (or if you want the functions available, hook it up in the acad2010.lsp file like this…
Over the past year I’ve received quite a few questions from people wondering how I manage all the windows that must be all over the place on all the various screens and systems. The standard answer is that “I’ve got my own little tool that I developed for managing window layouts” (on single as well as multiple systems simultaneously). However, that standard answer seems to result in even more questions as to how it works and what it does. Since I’m a firm proponent of code re-usability I’m also a firm believer in not wasting too much time answering the same questions over and over again so I’ve decided to answer the question in detail, once and for all. What I’m using for my windows and layout management is the Window Layout Manager, or WiLMA for short (hey, as developers we’re allowed to invent a dozen new acronyms each day and we like that little perk!)
The result is that I am finding it very annoying and painful on the eyes. But not so much the color schemes using a dark background themselves, but rather the practical implications when using it while doing actual work. The dark background allows for better highlighting of code, no doubt about that, but in a practical situation I often have other applications running on the screens which include things like help files, CHM’s and PDF’s with developer documentation and API docs, Outlook, OneNote, Visio, and many other development tools, etc. and almost all of these applications will use a light or white background as a basis.
I’ve recently been really getting into PowerShell and investigating its potential as a new automation and scripting platform for the countless command line based processes I’m running all the time. The first thing I did was purchase a copy of PowerShell Analyzer, which I think is one of the most valuable tools for anyone getting serious about digging into PowerShell’s object paradigm. And while you’re checking out PowerShell Analyzer, check out what the Shell Tools guys are working on; PowerShell Plus. Amazing stuff.
What do you mean you’ve never heard of those groundbreaking development methodologies? Well, perhaps you haven’t but I do think you should check them out if you’ve got a minute so Scott Berkun can explain these to you in detail. I would like to add, OOCDD, Out Of Control Driven Development. Unlike most methodologies, it’s an encapsulated methodology that derives from all others. Especially considering how out of control development gets, regardless of methodology.