15 December 2009
Cracking the whip
The other ALT who works at this school (we sort of irregularly alternate weeks) has repeatedly found himself in situations where students openly (flauntingly?) operate their keitais during or between classes. Each teacher has her own approach (or lack of an approach) to discipline, and the students do take advantage of gaps in the armor. My friend has sufficient command of Japanese to address their behavior, and he does, but the situation brings up some issues regarding the role of ALTs in classroom discipline. What is the role of the ALT?
The responsibilities of an ALT are dictated by his individual situation. In junior high school, I work alongside other teachers. I view myself as support for the Japanese teacher of English, and that informs my level of involvement in classroom discipline. During my first year, I'd try to match the tone of the JTE. This meant that in less disciplined classes, I wouldn't try to single-handedly bring the class in line; I just accepted that that was the way the class was.
Chalk one up for cultural sensitivity. Hah. I'm too old for that now. This contract cycle, the Age of Intolerance resumes.
Recently I've been taking a more active, assertive role because I feel more knowledgeable and confident about Japanese and the behavior of my students. When I judge that the JTE doesn't have sufficient control of her class, I move about the room and attend to the problematic students while the JTE continues to teach.
ALTs in elementary schools often have to shoulder more of the classroom discipline burden as they don't work with JTEs as junior and senior high school ALTs do. A teacher who participates in the ALT's lesson can help to a certain extent, but one doesn't always have those teachers (some totally check out when the ALT takes over the class-- cookies and coffee in the break room). ALTs at the elementary level have to use more Japanese and be more assertive with discipline in order to be effective. Not to make them sound balanced or equivalent, but I actually have a hard time comparing JHS discipline with elementary discipline-- with the former, students are more recalcitrant but the JTE can help; with the latter, it's your own show but the students go nuts for inflatable hammers. Wait-- so do my JHS students...shit.
I think I've learned a few things while teaching in both situations. My Japanese isn't very imposing, and neither is my stature, so I rarely use the intimidation route to effect behavioral change. I find that just making the students uncomfortable with a conversation works best. I do this by merely directing my attention to that student (only that student). Most students don't want to be singled out against their will. The best thing about this approach is that it doesn't have to be negative at all; it's exactly not a confrontation. You can really just talk to the student about any dumb thing that comes to your mind; instead of saying, "Quit screwing around," I say, "Where's your notebook?" or things like that. Some kind of simple, simple English sentence works; a barrage of the Queen's doesn't. I don't speak Japanese at all in junior high school classes as a rule, and this approach to discipline allows me to be consistent. Anyway, at best, the student changes his behavior so he doesn't have to speak English with the ALT; at worst, he gets some English conversation practice in.
Back to the cell phones. Discussing the problem, my friend and I agreed that the teachers should be stricter with the students to show that they are serious about following the rules, but we also acknowledged that the teachers may simply be picking their battles. Still, we wondered about the role of the ALT here. Can you overlook a blatant infraction? In new ALT training, it was pounded into our heads that ALTs are supposed to be super-genki, creative, and fun. Finding students operating their cell phones put my friend in a tough position vis-a-vis the whole 'fun, friendly ALT' thing: he wondered whether he should tell the JTE, making her aware of the situation but likely alienating the students (who would find out that the ALT told her), or take it upon himself to square away the student. He chose the latter, and I think it was the right thing to do because it was the potentially constructive route. It gave the offending student an opportunity to change his behavior. Now, I say 'potentially constructive' because the students were back at it again the next time my friend visited the school, but you know...
Anyway, each ALT must communicate with her JTE in order to establish how to handle classroom discipline, and she must find out for herself what sort of approach will work best with her students. For example, my friend who teaches primary school in Cameroon says that students there are beaten daily.
10 December 2009
MW Local Multiplayer
MW2 has somehow just worked for us. The last time we tried to play a Call of Duty game (MW1, World at War), people got discouraged because there was a big skill variance between me (who owns both games) and my friends who...gamely gave the games a go. I had sympathy for that feeling, and it wasn't particularly fun for me to play the game without knowledgeable opponents, either. On top of that, there were usually more than four of us wanting to play and we had ready access to system-linked Halo. Shit just wasn't aligned for CoD.
Things are different this time. Since the last contract cycle ended, our gaming crew has dwindled. We lost one dude (and thus his brother's participation as well) to the Okinawan mainland and two returned to the US (one of those two being arguably the best Halo player). Another fellow, while still here in Miyako, appeared to lose interest in playing over the summer. I felt similarly, in truth. While I hated the premise and game mechanics of Halo in the first place, its brilliant feature set won me over for a long time. But eventually, as all things do, it became stale. As for the new guys, only one appeared to have much interest in continuing the Halo Monday tradition.
Given this situation, I started to make provisions for more 1- and 4-player gaming, picking up titles like Carcassonne, Worms, and Operation Flashpoint: Dragon Rising. Due to the difficulties mentioned above, the CoD series games were never on the table.
In the middle of November I ordered a copy of the hotly-anticipated Modern Warfare 2. My hot anticipation merely involved intentions of plowing through the campaign, goofing around in online multiplayer (living on an island is like living in a black hole of latency), and getting some real mileage out of 2-player Spec Ops (a buddy and I had been playing Halo ODST to moderate enjoyment, so MW2 co-op was extremely appealing). I didn't expect to get into 4-player local at all.
Sure enough, I beat the campaign on my copy's day of arrival, the Sunday after the mid-year JET conference in Okinawa. I played some multiplayer online as well and was pleased by the panoply of new weapons, equipment, and killstreak rewards. That week, Long Beach* and I got into some Spec Ops and had fun. New York* and Eugene* showed up later, and we decided to give 4-player split-screen a go, not thinking that it would be much different than the experience we had on CoD4 or WaW. It was.
As far as I can tell, what makes MW2 local 4-player better than that of WaW and CoD4 Number is the local multiplayer experience tracking/weapon unlocks/custom loadouts feature of the former.
Bluntly, I had a big leg-up on my crew when it came to skill because I had been playing the game several days before they did. While this was discouraging in CoD4 and WaW (hereafter together referred to as CoD), in MW2 that disappointment is offset by the fact that just about everyone unlocks something during each game, be it as significant as leveling up or as cosmetic as getting a new title for your name. Similarly, being able to customize so much-- even without access to all of the weapons from the start-- gives each player a sense of individuality that, however shallow it may be, helps keep him ever in search of the ideal configuration for his strategy or style. The experience/unlocks system maintains their interest in the game even in the face of repeated losses, because no matter what, some progress is being made.
My favorite thing about the local multiplayer experience tracking is how, with time, each player develops his own style and branches away from the others. With the exception of Long Beach (who has consistently used launchers and LMGs from the start), everyone focuses on developing a fast UMP loadout at the beginning. I've seen it happen five times, once being myself. I think this had more to do with the nature of the 4-player games we were doing rather than some imbalanced quality of the UMP. In our current 'mature' statuses, we are as follows:
Eugene favors the assault rifle class and rarely resorts to a secondary weapon. He's a mover and shooter who hits more headshots than anyone else. Pretty handy with the knife as well. His long-time weapon was the M4 with a heartbeat sensor, but he's recently been using the FAL and continues to improve his long-range game.
As mentioned above, Long Beach is invariably seen with a launcher. Our early games usually involved me being grief-ed to tears by his AT-4 rocket, but he's since taken up the standalone grenade launcher to better effect (to Marksman III-- no one else is ever going to get that); it's basically his primary weapon. He's often found prone in corners, working both for and against his advantage. Long Beach definitely gets the Most Sportsmanlike award because he took a lot of beating early on but persevered. He makes a great teammate for a lighter, faster-moving player.
New York is skilled and fun to play with because, like me, he prefers CoD-style games over Halo and has an intuitive grasp of the game mechanics. Fortunately, aside from both being aggressive players, we have radically different playing styles. NY is the only player who consistently uses a shotgun (AA12) and an assault rifle grenade launcher attachment. Reflecting on his loadouts right now, I can see that they are really geared toward the gametypes we regularly play, like Sabotage and Headquarters; we don't do a lot of long-range fighting, and his kits and play style indicate that.
New Zealand* is the most specialized player. Starting with the universal UMP-fast dude setup and developing it out, he now tears around the map with akimbo SMGs and all of the relevant speed- and hip shooting- related perks. I imagine that it's like playing Doom 1 or something. Meeting him indoors usually turns out badly for the person who isn't him due to the sheer volume of fire his setup provides. Recently he's started using the TAR21 to good effect and is getting better at using the sights. I'd say he is an aggressive player.
Melbourne* is our newest player and the one who plays games the least. He's a capable medium-long range shooter (good timing + hard-hitting assault weaponry). Not having the same access to weapons that the others have, his loadout is less than exotic. Nevertheless, while usually getting massacred in FFA deathmatches as a new player, he's quite effective in team games. He's saved the day for me numerous times in games against more experienced pairs.
As for me, I watch screens.
Anyway, it's a pretty cool scheme. While higher level players have access to a larger absolute arsenal, it is only by the individual player's time and effort that he unlocks the attachments for the weapons. For example, Eugene and I both have the M4, but he (at a lower level than me) has access to attachments for it that I don't have (heartbeat sensor and stuff). The race continues for completion of a weapon's unlocks; I think New Zealand may win it with his near-c0ntinuous use of a UMP-based kit.
There are other improvements found in MW2. There are small maps, and the larger ones scale well. 'Shipment' from CoD4 was too small and an obvious throwaway of a map, but 'Rust' from MW2 has the appropriate complexity for 4 players to have a constant firefight. Of all the MW2 maps, perhaps only 'Derail', 'Wasteland', and 'Estate' are problematically large. The new death streaks are also good, but it's not because they help the losing player that I like them. The reason I like having death streaks is that they provide a dumping ground for the more annoying and crappy perks from MW1 like Martyrdom and Last Stand (here called Final Stand). MW2 still has Last Stand as a standard perk, but it's nerfed. You can't draw the handgun as fast as you can in MW1. We went back to play WaW last night for shits and grins, and my use of Martyrdom had my friends howling with indignation. Some stuff just isn't missed.
A gaming routine has emerged. Several times a week we meet up at my place to play several rounds, and playing with friends has pretty much become the only gaming I do these days. We're kind of 'on a day, off a day.' It works with everyone's schedule and we don't get too burned out (quite the contrary, in fact; I find myself not wanting to play at all the next day, but then being unable to wait for it the day after that).
All of this greatness from MW2 local multiplayer just fills me with that much more sorrow that it doesn't deliver split-screen system link. It would be a real contender for the be-all, end-all game of this console generation if it could run 8 players on two consoles. But I see that split-screen system-linkers like us are a tiny minority of the gaming market for whom development is not profitable. I understand it, but it sucks.
*Names changed to hide the guilty.
Stuff
I've been here in Miyako for over a year now and the sheer amount of shit my students give each other still staggers me. Today one student approached the blackboard to throw a suction-cup ball at an English vocabulary word (it's part of a game) and the rest of the students in this 17-person class started screaming about how long this kid's legs are (he's comparatively tall).
Two things: (1) That this dude is tall is not new to the class. The composition of this group hasn't significantly changed in over 8 years of schooling. (2) The comments were actually neutral-sounding, but that's the way Japanese people tend to take the piss out of anyone who momentarily stands out. Again, it never fails to fascinate me.
In other news:
I typed up a review of Infinity Ward/Activision's November release, Modern Warfare 2, but it's on my other computer and I haven't posted it yet. In that review I don't go on about how awesome or crappy the game is-- instead I talk about a few of the changes IW made to the MW formula that make the new one more 'casual gamer'-oriented than the last. I'll finalize it and put it up this afternoon when I get back to the big machine.
However, I usually bring a laptop with me to schools (this is where I'm writing from right now). It's a Gateway MTxxxx purchased straight off the shelves of Office Depot in 2007 and is currently running Ubuntu Linux. I've been pretty happy with it as far as word processing and web browsing go. Video isn't really a problem, either, but it won't push anything that involves OpenGL or lightly intensive 3D graphics. Originally the machine had Vista, and it would run Aero without a hitch, but I've since moved Vista to the homebuilt machine and replaced it here with Ubuntu. Again, I use this only for wapuro and browsing, so Ubuntu is ideal. It boots up quickly, drivers haven't been a problem, and-- contrary to the daunting image of Linux-- I haven't had to use the command line terminal once since installation. I also like how each release is aesthetically better than the last. I think it's a pretty good deal.
30 November 2009
About Maj. Nidal Malik Hasan
Calling this terrorism is either hysterical or merely for political advantage among certain audiences. It's trendy and sound-bitey without being clear about what the accused is. The more severe charge-- the real crime itself, I think-- is this demonstration of disloyalty through murder. The US military isn't perfect, but it has often been one of the more egalitarian institutions of American society. That's admirable and something to be proud of, and Hasan's alleged actions spit in the face of that achievement. Again, there are failures, but one's race and religion are generally of little concern to the military if one can do the job that is assigned. The grand ideal is that those who serve agree (in the deepest and most formal sense) to act according to duty and loyalty (yes, despite the scintillating leadership of self-interested career politicians). It works when everyone is on the same page regarding what's most important. It can't work if a soldier has another priority, if he is ultimately more concerned about (and acts according to) the interests of Islam, making money, black people, Canada, atheism, poodle enthusiasts, Christianity, Freemasonry, Jedi knights, or anything but the aims of the military. The murders are horrible. That the targets were fellow servicemen is a separate and distinct injury, and I think it should be noted in public, legal terms.
This isn't to say that there shouldn't be dissent. Dissent is part of being American; it's part of being human. American society and the American military do allow it to varying degrees. But ultimately, you've got to know where you stand. What Hasan cares about is pretty evident, and it's not the army. He could have refused to be deployed and simply faced the legal ramifications, but he instead allegedly decided to shoot people. It was an attack on the personnel, morale, and overall fighting ability of our forces. The shooter isn't someone who wants the US to succeed, and yet he is a serviceman. It seems particularly grievous.
Now, regardless of whether this is to be called terrorism, the military should combat the spread of radical Islam (and everything subversive to the military's mission) within its ranks for the sake of doing its job effectively. Much was made of the institutional efforts to prevent extreme right-wing groups from gaining traction among soldiers a while ago, if I remember correctly, so I guess this is something that military does do. Understanding Hasan's motives does matter-- not for his sake or to sympathize, but to prevent this sort of thing from happening again.
Anyway, in short, I see a traitor here rather than a terrorist (whatever 'terrorist' eventually comes to mean). Are we terrorized, or are we appropriately pissed off about someone violently crapping on the concept of duty?
*If this 'traitor' angle has been beaten to death in the US media already, I apologize-- I'm somewhat out of the loop.
Interesting article.
25 October 2009
Miyakojima Track and Field Competition
10 October 2009
A DIY Era, Part 1: Building a PC
Tyler Durden: Guys, what would you wish you'd done before you died?
Ricky: Paint a self-portrait.
Tyler Durden: [to Narrator] And you?
Narrator: I don't know. Turn the wheel now, come on!
Tyler Durden: You have to know the answer to this question! If you died right now, how would you feel about your life?
Narrator: I don't know, I wouldn't feel anything good about my life, is that what you want to hear me say? Fine. Come on!
Tyler Durden: Not good enough.
Nay, I built a computer.
Building the thing itself was mostly smooth and uneventful. I had some trouble fitting the motherboard-video card combination into the case (jiggling the boards and whatnot to get them situated was pretty nerve-racking). But anyway, pictures:
The CPU (AMD Phenom II X2 550 Black Edition) uses the Socket AM3-type of motherboard-CPU coupling armature interface (keep your wig on-- as a philosophy major I'm qualified and licensed to make up terms as needed).
The Foxconn A7DA-S 3.0 motherboard has the appropriate socket. I believe it also supports Sockets AM2 and AM2+ (is that the same as AM3? I think I saw that somewhere...). It can also rock the DDR3 RAM, a feature of which I took advantage. <-- Do we go so far as to risk awkward sentence formulations just to avoid the commonplace but proscribed ending of a sentence with a preposition? I do sometimes.
The GPU (Sapphire ATI RADEON HD4870 1GB): The card was probably the most difficult thing to decide upon (gah!). I chose this one because it isn't the most powerful card on the market this year, but it offers great performance on all games at far higher resolutions than I intend to run. I love high-definition as much as the next guy, but if I can run 60 fps on nearly anything at 1680x1050, I'm more than happy. I intend to keep the adequate-yet-modest LCD I have now for a while yet, and until I change the display, a better card would be overkill. Also, the HD4870 seemed to be where the performance return from getting a higher end card began to drop off sharply while the increase in price did not. In other words, I think the HD 4870 was the sweet spot of value when I made the purchase. Of course, you may notice that I did get the 1 GB version; apparently the memory helps when you're dealing with lots of textures. If it becomes a necessity next year, I'll grab another 4870 (even cheaper by then) and do some Crossfire action.
I seated the GPU into the PCI-E slot without incident. This particular card is something of a beast, requiring two connections to the PSU rather than drawing power from the motherboard via the PCI-E connection. There is a hot, masked CG babe on the card as well. My friend says she makes the processors run faster.
Installing the CPU was a lot easier than I expected. It's somewhat taxing because you are conscious of how fragile and crucial the CPU is but nevertheless have to secure it in a high-tension retaining device and then install a (possibly) massive heatsink-fan assembly on it. And the pins...so many... Fortunately, the CPU dropped into place effortlessly once the pins were lined up with the socket (motherboard-CPU coupling armature interface). I could feel slight resistance as I pulled the retaining arm down to secure the CPU, but it wasn't particularly concerning. The original AMD heatsink-fan came prepared with a patch of heat transfer paste, and I merely had to remove the plastic film on it before setting the whole thing against the CPU.
In a rustily ironic turn of events, one week after finishing the system, I went poking around the inside of the running computer to gather cables so they wouldn't get caught in the fans only to succeed in making a cable leap into the CPU fan, thereby chipping a blade and rendering my computer the sonic equivalent of an air compressor.
I deserve it. Moving on...
The silver lining here is that I ended up buying a replacement heatsink-fan setup for the CPU that works much better than the stock one (CPU temperature now sits at about 34 C instead of 45 C). It's a Cooler Master-- it has a larger fan, massive heat sink, and the four copper pipes running through actually contact the CPU itself by being flush with the base of the assembly. I put some extra heat paste on there to fill in the tiny gaps where the pipes cut through the base. It's been working great so far.
Anyway, I connected all of the SATA junk, power cables, and whatnot (but only after first trying to start it without plugging in the CPU power cable-- it didn't run very fast then). Connecting the small connectors from the hard disk activity light, the soft power and reset switches, et al. was sort of mendoukusai, but the helpful labeling of everything made sense. I turned it on, heard the test beep, got the BIOS screen, and enjoyed the mellow satisfaction of having built a computer.
First I installed Windows 7 RC, but I found out that the version of 7 that I had downloaded in the summer was the 32-bit one (limiting me to 3.3 GB of RAM or whatever) and the drivers that came with my computer parts weren't working perfectly. I had Vista on it shortly thereafter and got everything in order. I think playing Team Fortress 2 was the first thing I did. It ran well. I was pleased.
Naturally, I was curious about the limits of the machine. I installed Oblivion and it ran absurdly fast-- it had that strange (to me) look that high FPS motion creates. Awesome. It froze once or twice in the two hours I played, but it seemed to work well when it worked. I downloaded the single player demo for Crysis for the next test. The first run caused the computer to freeze during the opening skydiving sequence (just before the player hits the water). A second try yielded better results-- 45+ FPS. As I mused to myself about how mediocre the shooting was and the in-game dawn broke, the screen suddenly went black. The computer's fans were quiet, and no light came from the mouse, keyboard, or front panel. It was a complete power failure likely caused by the weak-ass Scythe PSU included with the case. I think. I have no proof. Some time afterward I decided to break the CPU fan as described above.
Acting on my feeling, I selected a new PSU (Kurotoshikou 650W) when I ordered the replacement heat sink fan. It rocks; it's got two 12V rails wielding 30A. People who say you shouldn't cut costs by getting a cheap PSU are right.
Since the installation of the new PSU and heatsink-fan, I've had absolutely no problems with stability. Oblivion crashes to desktop from time to time, but that's probably more to do with the volatile combination of mods I'm running to make it look and play better rather than the machine itself. I ran Crysis on 1680x1050 at very high settings just to see what would happen. Sure enough, I managed to slow the framerate to 4-player Goldeneye levels (not so low as 4-player Perfect Dark), but only at first. Once the game got moving, it was quite playable. I'll take it. That's one life goal accomplished...
TL;DR: I ALWAYS WANTED TO BUILD A COMPUTER. I HAVE NOW DONE IT; IT IS AWESOME.
Next time, Letters from Novosibirsk
OR
A DIY Era, Part 2: Painting a Motorcycle...
One is slightly more likely than the other.
30 September 2009
Battlefield 1943 and Provoked Thoughts
16 September 2009
Motorcycle stuff...
EDIT: I wrote this in Word and copy-pasted it here. The formatting is schizo and I refuse to change it.
I’ve had motorcycles on the brain for a while now, but never before has the fever burned so insistently. Bikes are literally all I think about these days. Providing that my love of motorcycling doesn’t displace my love of guitars, the panoply of my dedicated hobbies will paint me as a totally rad dude.
I’d been thinking of replacing the Hornet since I had the experience of riding a 400 in driving school. I think I finally came to my (financial) senses this week, or at least I’ve been able to convince myself that the Hornet is worth hanging on to. I’ve been doing a little reading on the 250 Hornet and the CB400 standard bike. Apparently (and this is anything but unexpected)
Anyway, I’m currently in the midst of a renaissance with my bike, the Hornet. I was sort of down about it a few months ago when I got around to replacing its fat-ass rear tire (180 on a 250?!). It’s just goddamn expensive. Also, I put slight scrapes on both sides of the tank that detract from its appearance significantly (update: I totally cratered the tank on a curb while racing the other day; no punctures, though). The wheels and rear sprocket are filthy with road grime, brake dust, and thrown-off chain grease, and the rust damage continues to creep. It’s a pain in the ass to work on anything without a center stand, so I’m checking the internets for one right now. I’d love to spend a weekend cleaning the thing…
Now I love the green machine. The current renaissance is a product of my constant reading about bikes. In comparing the Hornet to its potential replacements, I unwittingly learned more news about it. And the news is good.
First, I think I’ve got an early Hornet, maybe as early as 1996. It was received extremely positively (citation needed), and it’s cool to be riding an original.
Second, as I briefly mentioned before, the engine is pretty rocking for a 250. The 249 cubic centimeter motor gets over 24 Nm of torque (11,000 rpm) and 40 hp (at 14,000 rpm). Why did I just name those figures in metric and Imperial units? I don’t know—it just seemed more tangible to me than using one system or the other. Anyway, this engine is meant to scream. It redlines at 16,000 RPM and doesn’t even get busy (and this was news to me) until 10,000 rpm. OK, I knew that running higher revs would produce more power generally (thank you), but going over 10,000 had always just seemed excessive to me. I usually kept the machine turning slowly as I went about town thinking that it would save gas and prolong the life of the engine. However, my mileage driving that way was about 180km before reserve. Last week, when I tried running the machine at higher average rpm (and with more playful power), I got 220 km before reserve. I’m still trying to sort that out (and repeat the experiment), but I think that this engine is meant to be run faster than I had been running it. In short, the bike has a lot of power that I wasn’t effectively utilizing. Also, while it has a high pitched whine at low (>8000) rpm, the timbre radically changes to an absolute scream when opening the throttle. It’s easy to visualize air and exhaust racing through the system.
Third, I am now dead certain that the (a?) previous owner did some custom work on the appearance of the bike. Unlike stock Hornets, my bike doesn’t have the jagged Hornet logo painted on the sides of the tank. Instead it’s got chrome automotive letters spelling ‘HORNET’ running along the sides. Also, the green paint is chipping in places, revealing a layer of silver underneath. Why is this good news? I’ve been thinking about painting the Hornet, and I wasn’t certain whether the plastic parts could be easily painted; apparently it’s not a problem. I’m considering black and white right now, but I’m going to draw up a few designs. A new coat of paint would help cover the tank scrapes and give me reason to remove those chrome letters. They are odious.
Anyway, it’s an exciting time for motorcycling. I recently got riding shoes and gloves, so I’m pretty excited about the next track day when I can show off my latest fashions and subsequently get destroyed on the time trial.