Forgot your password?
typodupeerror

Comment: Depends on what you mean by "develop" (Score 1) 608

by stove (#47414681) Attached to: Normal Humans Effectively Excluded From Developing Software

Program a widget for a smartphone using a already existing framework and pictures that'll display and whatever... Sure, sounds like something "we" should simplify. I'l get on it.

Building said framework? Cool, so you're going to need to know a programming language or two, how those interact with the phone hardware, what the phone hardware's limitations, perhaps some UI design and... hey, where are you going? I've got months more reading for you to do!

Comment: Re:Every single point in the joke is wrong (Score 1) 246

by stove (#43937119) Attached to: One Year After World IPv6 Launch — Are We There Yet?

You're right, I was going for a joke. What you're showing me is I'm doing a bad job of explaining the benefits of IPv6 and probably need to do more reading.

In my defense, there are probably more "gotchas" to this than you may be giving credit for. Doing "IPv6 to IPv4" translation is, as you say, easy. I don't consider that to be "using" IPv4, though. What I have read has given me some pause - firewall rules need updating, some security concerns need addressing, etc.

I'm not a network guy, just a UNIX sysadmin, so my comments should be taken with a grain of salt the size of my igorance.

Comment: Stigmatize it... (Score 2) 405

Like drunk driving. I don't know about where y'all are, but driving drunk is a step above child molestation where I am.

It's just right now, lots of people are doing it, so there's a safety in a herd.

Yes, accept that the same rules (no problems if income is large, if political power is great) that apply to DD apply to "driving-while-texting,"

Comment: And the root cause is... (Score 5, Insightful) 246

by stove (#43935247) Attached to: One Year After World IPv6 Launch — Are We There Yet?

Me: "Hello, big boss! I'd like to go to IPv6 soon!"

BB: "What will that take?"

Me: "Oh, probably a couple of months worth of completely dedicated work from your best network folks. If you don't exclusively task them, could take a year."

BB: "Sounds complex. Is it risky?"

Me: "Absolutely! We could totally drop off the internet or lose internal connectivity for quite a while if we mess it up."

BB: "What, exactly, am I getting from this expensive and risky thing?"

Me: "More or less what you have now. The features it does you don't really care about."

BB: "So it's expensive and risky and I get nothing out of it."

Me: "Yep! When can I start?"

*doorslam*

Comment: Everyone wants freedom... (Score 1) 417

by stove (#38422906) Attached to: How To Thwart the High Priests In IT

Until it breaks. Then the IT guy/gal needs to stay late and help fix the problem. Sometimes (and here's where the IT worker hits the alcohol)... get this... they suggested not to do it in the first place. After a couple times of this happening, IT workers get bitter and angry and don't want anything new on the network.

You'd be amazed what "I'd like to use device X on the network. Here's a couple devices for you, paid for by our department. Would it be possible for you to take a look at them for a couple months and let us know what'd be safe?" will get you.

Comment: Start Being Ignorant Now... (Score 5, Insightful) 229

by stove (#38422804) Attached to: Ask Slashdot: Transitioning From Developer To Executive?

(Probably not the sort of ignorance you're thinking of, though.)

Start practicing saying "I don't know." You know a lot of technology right now, but in 5 years you'll know less, and in 10 the young kids will roll their eyes when you talk about how it "used to be." Set a big organizational goal ("double our storage space for next year") and then ask the technicians how to make it happen. Resist the urge to do anything more than "suggest" things or vaguely hint at solutions. Know how little you know.

What you shouldn't ever forget is how technology "really works." You know, "fast right cheap pick 2." If your company wants to go with a cheap solution to their problems, make sure you've prepared properly for it.

All the successful technician-to-manager folks I've worked under have suggested solutions, listened when technicians explained problems and tried to get managerial roadblocks out of their way. On the plus side, the best managers I've worked for were promoted techies. Good luck!

Games

Decrying the Excessive Emulation of Reality In Games 187

Posted by Soulskill
from the plumbers-with-shrooms dept.
An editorial at GameSetWatch makes the case that game developers' relentless drive to make games more real has led to missed opportunities for creating unique fictional universes that are perhaps more interesting than our own. Quoting: "Remember when the norm for a video game was a blue hedgehog that ran fast and collected rings and emeralds? Or a plumber that took mushrooms to become large, and grabbed a flower to throw fireballs? In reality they do none of those things, but in the name of a game, they make sense, inspire wonder, and create a new universe. ... We’ve seen time and time again that the closer you try to emulate reality, the more the 'game' aspects begin to stick out. Invisible walls in Final Fantasy, or grenades spawning at your feet when you go the wrong way in Call of Duty: Modern Warfare 2 are examples of kicking the player out of that illusion of reality, and letting them know that yes, this is a game, and yes, the rules are designed to keep you in the space of this world, not the real world. In reality, as a soldier I could disobey my orders and go exploring around the other side. I could be cowardly and turn back to base. Games shouldn’t have to plan for every eventuality, of course, but it’s not so hard to create universes that are compelling but where the unusual, or even simple backtracking, is not so unfeasible."

In order to get a loan you must first prove you don't need it.

Working...