Saturday, September 25, 2010
Friday, September 24, 2010
If the results of your efforts to hand-crank HTML and CSS were trifling before this "nifty" tool, chances are rather high that your results after the new tool will be trifling. Just because it now looks like every other site using the same development tools doesn't mean that any of those sites look particularly good. For starters, for a site to stand out, it has to be both good and unique. You can't stand out by looking like everyone else.
In the end, junk is junk. All that the various design tools do is make it easier for junk to be thrown out there.
Thursday, September 23, 2010
Wednesday, September 22, 2010
Today, we had our weekly project-team meeting at work. It's a fairly large team and there were some new people in the meeting. I'm not real good keeping track of names - I'm more a visual person (i'll remember faces forever but can never match to a name, somehow).
At any rate, the meeting is a long one and runs well into the normal "lunch hour". So, after the meeting ended, several of us headed out in search of sustenance. As is often the case, after meetings are over, they remain a topic of conversation (usually related to frustrations due to the meetings - such as from their content and their length). One of our lunch group was making reference to another person who'd spoken in the meeting. I was drawing a blank on who they were referring to (we all talk in this meeting, at some point, even if only briefly). To try to clarify for me, I was told, "it was the guy with the unique hair." Now, given the some of the people I hang out with (and some of my own past hair "experiments"), I couldn't recall anyone in the meeting who had particularly notable or unique hair. I didn't recall anyone with any particularly radical hairdos. I didn't recall anyone with any particularly unnatural hues in their hair.
In essence, the point of reference clarification was about as useful as being told "look for the guy in black" at one of the concerts or clubs I go to. Oh well...
This is why I'm glad that I can generally telecommute. I could probably do so nearly every day, but, it's good to get at least two days of "yes, I'm still alive and working here: don't steal my desk" time at the office each week.
Fortunately, the trip home, most evenings, I can take the highway route and it only takes 30-40 minutes, on average (again, with the two miles closest my house and office taking the bulk of the time).
Tuesday, September 21, 2010
Monday, September 20, 2010
Ugh. Always best to try to set aside the things that are out of your control. Only way to help keep the bitterness at bay.
Ok, so, for whatever reason, Microsoft likes to make things painful when you want to do remote server administration from your Windows desktop. It used to be, if you were running XP, or even vista, you just installed the Server 2003 Adminpak and you were pretty much "good to go". Why they didn't just make this part of Windows - particularly the "pro" versions - I'll never know. It's just a headache you had to put up with.
Apparently, Microsoft didn't think that this was enough of a headache for people that wanted to remotely administer Windows systems from a Windows 7 system. They made it even more of a pain in the ass:
- Go to the Microsoft website and download the appropriate MSU file. One would think this would be rather straight-forward. However, they start fucking with you, even here. If you're a 32bit x86 user, everything's pretty simple as far as which file to download: you just grab the "x86fre_GRMRSAT_MSU.msu" file. If you're running an AMD CPU, things are also pretty simple: you just grab the "amd64fre_GRMRSATX_MSU.msu" file. However, if you're using Intel 64bit, it's a little less straight forward. Most other vendors, they either have a specific x86_64 file or both the 32bit and 64bit files are in the x86-named package. However, Microsoft, in their infernal wisdom, puts all 64bit versions into the "amd64fre_GRMRSATX_MSU.msu". And, because that file's named "amd..." you assume, "oh, this is the version for AMD-based CPUs and download the x86 one, instead. FMEH
- Run the MSU and install the binaries.
- Wonder to yourself, why the hell the 222MB file you just downloaded and installed appears to have not actually installed anything
- Google around to figure out where the fuck your admin tools are
- Discover that, Microsoft, in their infinite bloody-mindedness, has decided to make you jump through hoops to actually be able to see and use the files
- Open up the "Control Panel"
- Navigate to the "Programs and Features" option
- Click on the "Turn Windows Features On or Off"
- Search through the available features to turn on until you get to the RSAT tree
- Click on the top-level option
- Go to find your tools and still find them not there
- Go back to the "Turn Windows Features On or Off" and discover that clicking on the top-level box actually did nothing and that you had to actually individually click on each and every function you want enabled.
- Go to find your tools are now findable with the search bar but still not in your Start menu
- Google around some more and find out, "Oh, in addition to the braindead way that I have to enable each and every feature, I also have to tell my damned system 'please to be displaying these tools in my program menus'
- Go in and enable the items to show up in my start menu.
- Finally be able to access and use the remote administration tools that should have been part of the freaking OS in the first damned place
Fuck you, Microsoft. I just shouldn't be that involved to get access to these tools.
Sunday, September 19, 2010
At least I can see the commercials in full size, though: