Forgot your password?

Comment: Huh. Really? (Score 1) 144

by ninjagin (#46534369) Attached to: Research Suggests Pulling All-Nighters Can Cause Permanent Damage
A couple of times a year, I stay up all through the night and go to work the next day. I find that it's not too disruptive, and that I get a bit more contemplative during the second day. It's not something I do on any kind of regular or planned basis -- it just sort of happens ... I can't sleep, so I read a book or futz around on the computer or mess with musical instruments and before I know it, dawn comes and it's time to go back to work. It's almost like one really long workday, with a really long lunch break (overnight) in the middle of it. I have to wonder what nurses and doctors (who sometimes have to work very long shifts) think about this.

Comment: Re:Skyrim (Score 1) 669

by ninjagin (#46286631) Attached to: Ask Slashdot: What Games Are You Playing?

I beg to differ. I have a sports car (an S2000) for real life driving, but I found that my proclivities for hooning were getting me in places where the law enforcement consequences would be very serious (see that speed limit? -- now double it -- that's where I used to push myself).

I picked up a copy of GTR-Evolution because of the various tracks and car selection, bought a good wheel, stick and pedals, picked up a couple extra 28in monitors for triple-headed goodness, and it's been pretty good. I found that I enjoy the 3rd person rally games -- Dirt3 is a real hoot. While I've not settled into it, I've been considering a move to iRacing, which is a lot more technically accurate when it comes to terrain and car adjustment.

So, I think that driving games can be very helpful in keeping me out of trouble and yet still very much into the technical driving mindset.

Comment: ... a mix ... (Score 1) 669

by ninjagin (#46286471) Attached to: Ask Slashdot: What Games Are You Playing?

My LAN group is playing Borderlands2 (FPS) and StarCraft2 (RTS), occasionally Diablo3 (RPG).

At home, I tend to play Rise of Nations (Thrones & Patriots, an RTS) on the PC and augment that with Super Mario World 3D and Super Mario Brothers WiiU.

I still enjoy Wii Sports Resort, mainly for the bowling and archery and frisbee.

For mobile, it's Donkey Kong Country and Super Mario Brothers on the 3DSXL.

Lots of games, but nothing especially unusual.

I'm kind of excited about Titanfall (almost out) and this kickstarter game called "Reset" (by Theory Interactive) that I think is due out late this year.

Comment: Re:And in other news... (Score 4, Insightful) 625

by ninjagin (#46229463) Attached to: Majority of Young American Adults Think Astrology Is a Science

What you have identified as "political correctness riding a democratic ass" is a lot older than you assume, but it is, in fact democratic... old school. It's old name, back in the times of the Greeks and the Romans, was "decorum". It means "fit" in latin, having the meaning of "suitable". It's part of good rhetoric, as a device that brings an audience closer to you by not being rude or offensive. To flip that around the other way, you can include (or show that you welcome) a person or group of people in your reasoning or community by choosing your words carefully.

I think you may be conflating decorum with inappropriate recognition for achievement, but the two are separate things. The former is meant to show or develop alignment with shared goals or interests, and the other is meant (with good intent, perhaps, though with questionable results) to boost self-esteem.

I choose to observe rules of decorum (the people around you actually decide what they are) because I want to work more effectively with people around me and to perhaps have an easier time convincing those people to do things that I see as beneficial. By not declaring that the people around me are my hated opposition or labeling them in ways that might confine their ways of thinking to those that oppose my views, I keep them open to my persuasion.

Since I share your goal of not perpetuating inappropriate recognition of achievement, I'm happy to let you know that I was utterly unconvinced by your point of view and there is little chance that you will ever persuade me. I encourage you to keep floundering away in your rhetoric until everyone around us is as convinced as I am.

Comment: Re:Pffft (Score 1) 723

by ninjagin (#46111017) Attached to: Atlanta Gambled With Winter Storm and Lost
To go a little further, You don't need a special truck to do plowing -- a sanitation truck with a blade mounted will suffice. Flatbed heavy trucks can be equipped with gravel/salt spreaders. The notion that one needs to keep a cityful of special equipment that's specialized for snow is a bit of a red herring. Most cities already have the trucks they might need -- they just need the ability to equip them for snow/ice remediation when the need crops up. Also, maintenance for snow/ice-fighting equipment is a little bit of occasional metalwork and a coat of paint -- not high-dollar, and already well-within what most cities already have to do for the equipment they use on a regular basis.

Comment: I've had experience with this, actually... (Score 1) 162

by ninjagin (#45660783) Attached to: Ask Slashdot: To Publish Change Logs Or Not?
When I first started working in IT, back in my early software days (as a tech writer), we did assemble a release report out of the defect tracking system, but then groomed it so that the descriptions were meaningful, and they communicated what the customer would actually see a a change. So many software changes don't leave much of a trace or evidence of a change at all that at some point you need to focus on the things you fixed/enhanced that could be appreciated. Occasionally, when there was a meaningful grouping of individual changes around a particular feature or piece of functionality, we were better served by an umbrella description that spoke generally about a swath of modifications and the area of functionality they affected. Further, we would "sanitize" (ugh, I hate that word) the descriptions so that they did not speak explicitly about protected IP in a way that would permit a casual engineering user to write their own stuff using the description as a template. It was also necessary to moderate the tone of individual defect reports in the summary to ensure that they did not come off as alarmist or use hyperbolic language -- you don't want to send out a report that says "Bezier curve clippings, when extended outside sections of the layout area, cause catastrophic, random, immutable, artifacts to appear in layout prior to full system crash" when it's a problem that (while bad, and fixable) doesn't happen in most situations and is only reproduceable if you use the tool in nonsensical ways. We used to have a couple layers of editorial review by the development management and sometimes legal if there was a sticky topic, but this was more to check work than to artfully craft anything. I had to help write release notes thereafter as a developer and as a manager, and the spirit is the same. If there is a bug in your stuff, your user community has probably already shared it with the world anyway, so acknowledging faults and fixing things is part of the virtuous cycle. You can actually gain user trust by demonstrating that you can successfully identify and promptly fix issues as they come up. Sales can be helped, too, if you had to solve some specific problems (or add functionality) before a customer will make a purchasing decision... they can recognize that their voice is being heard and the product is being maintained in a way that is attentive to their needs. All the same, there's no reason to shoot yourself in the foot in addition to having to fix your problems or make your enhancements.

Every young man should have a hobby: learning how to handle money is the best one. -- Jack Hurley