Andy Behrens has got to be my favorite fantasy baseball writer ever. His predictions aren't necessarily any more accurate than other writers', but they are hilarious. The following is probably my favorite baseball-related quote ever:
"I'd like to point out that the White Sox team OPS is .671, which is actually two points lower than Tony Womack's career OPS. So the White Sox' lineup is basically eight Tony Womacks and one guy who isn't quite that good." --Andy Behrens, June 26th, 2007
Fantasy baseball time! I'm no expert, but I have done relatively well these past few years in private leagues. This year I've stepped up to three leagues total: Garrett Anderson League (GAL), comprised of friends from college; Bain Fantasy League (BFL), my work league; and Tampa3 Rays of Death (TRD), a league of mostly of friends of a coworker (Caf). I'm most concerned about the TRD, because I spent a fair amount of time discussing strategy with Caf last season, and now I'm not going to be able to do that without tipping my hand.
Draft strategy has always been my weakest point; after reviewing my last four drafts, I'm surprised I ever finished above .500. My failure rate (number of draftees nor appearing on my final roster) is around 50% each season (my numbers for last season are obscured because I went crazy with roster moves in the playoffs to maximize various stats). I'm especially bad in the later rounds: for the last 8 rounds, I'm 0-8 in '05, 1-8 in '06 (Eric Brynes in the 18th), and 2-8 in '07 (Ian Snell in the 20th and Shane Victorino in the 21st). I don't expect 100% success with those last picks, but come on! 12.5% is pretty damned lame. So while it's fun to focus on the first 10 rounds, I'll be focusing on the last 10 rounds for my draft prep .
First of all, let me get this out of the way: GIANTS WIN! GIANTS WIN! GIANTS WIN! GIANTS WIN! GIANTS WIN! GIANTS WIN! GIANTS WIN! GIANTS WIN! GIANTS WIN!
OK, now that I got that out of the way, I can get to my main point. I am so glad the Giants won. Not because I dislike the Patriots. Not because I'm a Giants fan (I'm not; I'm a Jets fan, but the Giants are my #2). But because Pats fans have become so smug these past few months. People were talking about the Superbowl parade as if it was a done deal. Now I can get some peace at work.
(cross posted on Yankee Fan In Boston)
Make sure to save your receipt from Gamestop! I bought an XBox 360 Black Wireless controller from them recently, and it was defective. I threw out the receipt (very uncharacteristic of me, but I figured I could exchange it if it was defective), but apparently you need a receipt even for an exchange, these days. When I got home, I attempted to find their in-store return policy online without success. I finally found an old receipt (for Halo 3 actually), so I've copied the policy below for your benefit. Note: Best Buy and Circuit City also require receipts for all returns/exchanges these days.
"Receipt required for returns/exchanges. Unopened new items can be returned/exchanged w/in 30 days. Opened new video games, new PC games & new systems can be exchanged for the identical item w/in 7 days. Opened accessories & all used items can be returned/exchanged w/in 7 days."
The Giants utterly dominated Green Bay last night. The Packers had nothing against them. They couldn't run at all, and while they certainly got some yards in the air, the Giants' secondary came away with two pics. Jacobs and Bradshaw split the carries and each got over 60 yards. All in all, a smackdown!
All I'll say is this; if the Giants can pressure Tom Brady up the middle (think Strahan-Osi stunts behind the DTs) they'll have a shot.
I spent about two hours last night installing Slackware on my Celeron 350 Compaq. I got it booted up, everything working, fired up Lynx to verify that Apache was running, and was all set. "Allright," I said to myself, "now I just need to connect it to the network and I'll be in fat city!" I looked around the room for a network cable, and then said "... fuck" because my basement isn't wired. So here are my options:
So you see, I'm boned.
I use iTunes for my music player on my computer mostly because it does the few things I want well (smart playlists, ratings, sharing). But I hate it. So bloated, always starting "iTunesHelper.exe" and "iPodService.exe", and cancelling a system shutdown if another user is connected to my share; the arrogance of Apple shines pretty brightly through iTunes for Windows.
But I found another punch in the face from Apple today. My iTunes stopped working for some reason or another. Fine, I'll repair the installation. No dice? OK, I'll install the latest on top. Still not working? Ok, I'll uninstall/reinstall. "You must reboot the system to put these changes into effect." Yeah yeah, "cancel", I know what I'm doing. But on installation, I get this:
DO NOT WANT
If you don't have an iPod (like me), iTunes is a music-player program. I don't know what the hell that is, but it's clearly not something I want going on for a basic MP3 player. Sucks.Eric recently mentioned that he and his coworkers were debating the merits of the following two ruby code snippets.
if object
if object.nil?
If object is nil, both of these expressions will evaluate to false. The question was, should the former be allowed? I've had my thoughts on this before, but I stopped myself this time and thought about the issue at a higher level. We're talking about six characters here. What's the big deal? The first time a Ruby developer encounters this issue, he'll ask his buddy, Mr. Tubes, who will tell him the answer. Then he's good forever in that language. So we're really talking about the extra typing (ignoring the fact that if object represents a boolean, then we might have issues). But then this was said:
FxBx: but otherwise, yeah, im all for if object referring to its mere existence
KxDx:Yeah, it's intuitive
Eric dropped the I-word. The programming blagoblog has been abuzz lately about intuition (here and here (yeah I know one of them, is old, but it was recently recirculated)). Some people think intutive means familiar; that viewpoint is at least partially true. Tech reviewers and regular joes criticized Microsoft Office 2007's new interface, the ribbon, because it wasn't intuitive. What they really meant was that it was different and they couldn't figure it out. The QWERTY keyboard and mouse are only intuitive because we're familiar with them. Jef Raskin has said that the word "intuitable" makes more sense than "intuitive" because a user will either intuit an interface or not.
An interface designer has to balance introducing new concepts with existing ideas, using the old patterns to bridge to the new ideas. A completely new system would frustrate many users who would be unable to intuit the system, while a completely familiar system would add no new value.
Anyway, I get fired up about intuition and interfaces, but the point I'm trying to make is that spending time worrying about coding convention similar to the one above is wasted time. Unless you're marketing your product to a very specific subset of users who will only understand one way to do things, then just pick your favorite and move on.
I just briefly checked my Google Analytics and it seems that most of the people viewing this blog are looking for information about the XBox 360 Wireless Adapter and Verizon FiOS's ActionTec router. I don't have any more information about a potential fix; I emailed ActionTec again (since they were the only one of the three companies actually acknowledging the problem) and got the same form letter response. Great.
I did successfully nest my two wireless routers to allow me to get online with an open NAT. First I connected my 360 to my extra D-Link wireless router. I logged into the D-Link with my laptop, set the 360 to a static IP address, then made that IP address the DMZ. Then I plugged the D-Link's WAN port to the ActionTec's LAN, logged into the ActionTec, made the D-Link static and DMZ. Bam, open NAT and hello Halo 3.
A friend suggested an alternative to this that ideally would be even easier to set up. If I connected the D-Link's LAN to the ActionTec's LAN, then the two networks would be at the same level, and ideally you could use either wireless network to connect to the same network. I tried this, and for some reason the D-Link wasn't playing nice. To be fair, it was the cheapest wireless router I could find three years ago, so maybe if you have some better equipment, you'll have better luck.
Real-time strategy on the DS? Impastabowl! But they did it. Despite the massive dissapointment of Children of Mana (the first in this "World of Mana" series that takes place in the same universe as Secret of Mana but managing to leave all the good bits out), I decided to add this game to my wishlist and give it a swing. I mean, RTS. It has to be good, right?
1/2/08: I've played maybe four two hours so far, and I kinda wish I hadn't. You control a ship that's a carrier of sorts. You build your buildings inside of it, so you don't ever have to worry about space or power or that stuff. There are two resources, Gaia and Treant (which you might remember from CoM if you were unfortunate enough to have played it), and your one worker unit can gather them. You control a series of hero units with equipable items and talents. You can bring three of the heroes on to the battlefield, and the rest provide you with a "Support Aura" bonus of some sort. You can select units by tapping them with the stylus, or by tapping the "group select" button, which pauses the game and allows you to band-box select a group of units. It works... sorta. My hand cramps up while playing HoM on the train. Combat is simple; there is a "balance of power" of sorts where each unit type has another type it's strong against and one it's weak against. Anyways, I'm going to play more and see if it gets any better.
1/3/08: Adjusted the play time above from 4 to 2 hours; apparently time goes really slowly. I noticed a few things in my 30 minutes of HoM on the train this morning. The control scheme is actually quite useful ONLY if you always deselect the units (tap the "C" button on screen) when you're done ordering them around. This is because, unlike a mouse, you only have one control action (tapping), so there's no right or left click to deselect units like a PC RTS. Also I noticed most resource sources only have something like 5-10 of the resource in them, meaning that you have to move your ship around a lot or have your gatherer units (rabbites!) travel far.
I received three video games for Christmas: Mass Effect, Lego Star Wars 2, and Heroes of Mana. I plan to create posts for each and update them as I play the game. So, without further ado, my log of Mass Effect begins here.
1/2/08: Log started. Perhaps a little late, as I am already about 12-20 hours into the game. Still, there appears to be plenty of the game left. Love the game; stayed up until about 2AM playing last night. I like what BioWare kept from KOTOR (varying degrees of depth of dialouge, mostly free range of movement) and what they added (separate meters for goodness and evilness, actual real-time control of your character, a usable journal, an ignorable "codex"). Plus my ship is so much cooler than the KOTOR ships. So that's good.
1/3/08: Two things are really friggin annoying. When you die, the camera looks down on your corpse from above while rotating and the screen goes to a red tint. The problem is that you have to look at your corpse for a good 5 seconds before you can select "Resume", "Load", or "Quit". Resume loads from your last save, so that's nice. Also, you can carry a max of 150 items, but any item can be sold to a merchant or converted to "omni-gel" (a resource that you always have more than enough of) to make room. Items are only viewable where you can use them: weapons/armor on the equipment screen, upgrades on the upgrade screen (those are the only items). Of course, this means to find and get rid of your weakest/worst items, you have to go to multiple places. And just to be mean, the upgrades are sorted by level in descending order, but when you convert one, the current selection jumps back to the top (this doesn't happen when selling to a merchant, thank god). The worst part of this inventory management is when you reach the limit and acquire some new items. You have to choose which of the new items (or possibly all of them) you want to convert; you cannot choose any of your existing items or put the new ones back down or anything. I've lost out on some badass armor because of this.
1/10/08: I beat the game the other day. It was a less difficult ending than I had hoped, but the story was good. John told me that apparently the game has "New Game+" built into it in a Diablo-2 style (Normal, then Hard, then Insanity). That's certainly a plus for replayability. The achievements also support this; one of them is simply "Complete 2 Mass Effect Playthroughs on any setting." As far as I can tell, you would need to play through the game at least four, possibly five times to get every achievement. I think that's great; on my first playthrough, I got 430 gamer points (by my reckoning, I missed 205 potential points). My general rule is that at least 50% of all gamer points should be unlocked by a basic playthrough of the game. So this works. And I do play to play through at least one more time.
1/15/08: My second play-through as pure evil is going well. With the different dialogue and different order of tasks, the story flows quite different. Garrus is becoming much more of a badass, and Wrex is quite fond of me. Not sure if I really want to [[SPOILER]] on Virmire (note to self: implement spoiler Javascript). This will probably be my last update, since I can't imagine too much more can be added to my thoughts.
If you like RPGs, and especially western-style ones, you should buy Mass Effect. If you hate RPGs, then stay away, obviously. If you want an introduction to the genre and don't want to step backwards in time, Mass Effect is a good place to start.
I continually verbally spar with Eric about various code conventions, procedures, frameworks, ideas, and whatever else related to programming. Strong vs. dynamic typing, variable names, unit testing, you name it, we've debated it. Eric and John were tossing some ideas and articles back and forth in the campfire, and Eric sent over a link asking for my opinion. I read the article, but my net takeaway was neither positive nor negative.why the lucky stiff just argues (in his silly way) against unit testing and the bias against hacks and code tricks. But he doesn't mention context. Would he put that 5-line hack in a high-traffic ecommerce site?
The oversight is common among programming articles; all too often they preach a single idea as The Path. The real path is that there is no path; you have to think before you leap. It's not some Indiana Jones leap of faith thing. Do you really want to write unit tests for your RoR blog? Or do you want to put in a really nifty hack in an accounts-payable system or anti-spyware code?
Then John hit me with some of his brilliance:
FxBx: "to each his own, except for YOU." is what Fufflebee said.
FxBx: Some persons can't think
FxBx: They need to know what Microsoft and Apple are doing
FxBx: and copy for their own arts
He's right, of course. Those people are in the 80%, as defined by Jeff Atwood. By definition, the 80% aren't going to be smart; they're just doing to do. So maybe these "leap of faith" articles have a better chance of reaching the 80%.
What's my point? I'm not sure really. Us in the 20% (I'm fairly certain I'm at the bottom of it) will continue to debate about all sorts of high-falootin' ideas, and those in the 80% will keep plugging along.
The easiest way to get back into blogging is to convince yourself you've started anew, either with new content or a new feature... or both! Introducing Two Cents Is Too Much, a collection of my reviews of various things that are probably not worth anything (ask my about reviews some day).
In today's episode, I'm talking about Alien Vs. Predator - Requiem, or AVP-R. At first I thought the "R" stood for "Rated R", since the first AVP was rated PG-13. In the end, the R rating was the only thing good about the movie; hearing curses every other word was great. Otherwise, this movie sucked.
AVP-R reeked of other terrible SciFi sequels, like Starship Troopers 2. Its like the producers forgot to hire writers (maybe this was written during the writers strike). There was no plot to speak of. Instead the movie focuses on a series of fight scenes with bad lighting among various alien species and humans. I left 30 minutes in to grab popcorn and I didn't miss a thing. The best part of the movie was when one of the main characters yelled "Get to the chopper!" sans Austrian accent. Ahh, memories.
So don't go see it in the theater. Don't buy it on DVD. Wait until it's on TV, then check to see if anything else is on... I'd rather watch Chuck Norris sell the Total Gym ("Two months? Wow!") for 100 minutes than watch AVP-R again. I even had to watch the first AVP when I got home just to get the taste out of my mouth.
Manny coming around 3rd to score.
