Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment Pick the Right Tool for the Job (Score 1) 247

As an employed programmer that does everything from reading hardware schematics and writing C, to writing server code in C#, and finally writing all our build scripts in Python so they will be cross platform... I suggest learning Python as a way of getting back into things. I work in a variety of environments, embedded/linux/windows, and I had to make certain concessions in my code to account for the OS running the scripts, but Python was very easy to pick up and create useful things. I've managed developers who are very particular about whatever domain they're comfortable in, but if I can get the windows guys to install Python 2.x I'm golden. Always use the best tool for the job, while Python is great, I don't use it to build my .NET projects. MSBuild is better suited for that, no matter how clunky and painful it may be. This post is a bit muddy, so I mean to say if you're writing anything for your own personal improvement, use Python. Once you get your bearings, you may have to adapt and learn something else. Programmers are craftsmen, we should be skilled enough to work with whatever tools we're given.

Piracy

Sony Gets Nasty With PSBreak Buyers 246

YokimaSun writes "The war between hackers and Sony over the PlayStation 3 has now taken an even more sinister turn, with Sony going after not just shops but actual buyers of the PSBreak dongle, threatening them with fines of many thousands of Euros and forcing them to sign cease-and-desist letters. It seems Sony will use any means necessary to thwart both homebrew and piracy on the PS3."

Comment Re:F/OSS! (Score 1) 565

I agree! As an embedded programmer, ASM/C/C++ are languages I code with every day. Possibly worth noting: I am 30 years old and started with Visual Basic. Just because something is *newer* doesn't necessarily make the old languages less valuable.

Games

When Does Gore Get In the Way of Gameplay? 141

Wired is running a story inspired by the level of gore in the recent Wolverine game that wonders: how much is too much? It mentions a study we discussed in February which indicated that violence tended to interest gamers less than other characteristics. "... the longer you play a 'twitch' action game, the less you notice the cultural content — the gushing blood, the shrieks of agony. You're too busy focusing on the gameplay. I noticed this with Wolverine. For the first hour, I found the deranged bloodshed both shocking and exciting; it made me feel like I 'was' Logan, the grunting, killing-machine character from Marvel Comics' X-Men universe. But as I became more expert, the cultural shell of the game boiled away. In a sort of staring-into-the-cascading-numbers-of-the-Matrix way, I found myself looking past the visible aspects of the game and savoring the underlying, invisible mechanics of play. ... The game became pure physics and algorithms: Vectors, speed and collision detection. The gore had become mostly irrelevant."

Slashdot Top Deals

"Hello again, Peabody here..." -- Mister Peabody

Working...