Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Re:It's not arrogant, it's correct. (Score 1) 466 466

Okay let's say it is a road.

Netflix paid company A to move X trucks across the road.
Consumers paid company B to receive Y trucks to their house.

It is between company A and B to sort out what they will pay between each other.
If the cost is too high for company A they are free to pass the increased cost onto Netflix.

Just like NetFlix is free to go to company C to get a better deal.

To put this into a more concrete absurdity.. Let's say you have a gated community with an HOA. Guard shack, the whole works.
The HOA could pass a rule that in order for any packages from Amazon to be delivered Amazon must pay $10 per package to the HOA.
It is their road they are using. They can't get it unless they go by the guardshack, etc.
Just as absurd as Netflix paying the consumers ISP to get their internet traffic delivered.

Comment: Re:I... don't understand this at all. (Score 2) 125 125

Unfortunately this isn't a huge shock to me. Back in the 90's I remember trying to hook up a fortune 500 company to the internet. They were using public IPs on their internal network.. They complained when I told them they had to readdress their network.. I even dug up the various RFCs, who owned the public blocks they were using, etc.

There was actually a discussion along the lines of will we ever need to communicate with those companies? i.e. can we just ignore the problem.. In the end the argument that those places using public IPs wouldn't be able to communicate properly with the reset of the network got things going in the right direction..

Comment: Shortage appears real to me. (Score 1) 617 617

I know where I work we have quite a few open heads for competent C++ or Java devs.

However most fail at the interview stage.. They can't describe data structures they claim to know.. They can't implement some pretty basic problems in a working manner.. They can't decompose a problem into a workable design.

It's fairly rare that we get older people on the interviews.. But the few I have interviewed they tended to fall short in data structures or coding.. They could usually decompose the problem into a workable design.

My guess is that older workers end up in psuedo manager positions.. They design and tell all the underlings what to do.. They spend so much time designing and answering questions from above and below that their dev skills get rusty. When they find themselves looking they don't brush up those rusty skills.. And of course no one ever tells you why they are saying no after the interview.

PS: If you looking for a job Amazon in Seattle is definitely hiring :)

Comment: Re:Google Police (Score 1) 200 200

>Not this phone. It sat by the cash register unclaimed all the next day. “I don’t know anything about this stuff, but I know enough to know this phone was different.”

So the phone sat in the bar for a day and then they tried to figure out who owned it. Sounds pretty reasonable to me.

Comment: Re:IPs parallel the discoverable world (Score 1) 321 321

A better parallel is a phone number.

Somebody made a phone call with a voice distorter and threatened someone.
That phone call came from your house. Should you be arrested and thrown in jail because of that?
Or do they have to prove it was you that made the phone call?

Comment: Re:Developers shouldn't have production access (Score 1) 288 288

We do own the contents of deployment but not the mechanics of deployment. That means we setup software into packages the deployment system can consume. We identify what set of packages goes into an environment. We choose which environments go on which hosts. The actual deployment is kicked off via a web UI.
The merchanics of the deployment then worry about copying the data over and running the deployment scripts.

If something goes wrong with the automated system it is someone elses problem. However if something goes wrong with the scripts in the package we are deploying it is the devs problem.

Comment: Re:Developers shouldn't have production access (Score 3, Insightful) 288 288

I've been in companies that practiced it both ways.

Company A) Developers can never ever access production no matter the reason. The end result in that situation was bugs that couldn't be reproduced on the desktop or in the QA environment. The problems went on for months until I had a lucky break of a developer moving jobs into the system admin role of the production environment. When he looked things over he discovered the previous admin had not configured things in production properly. To the point of lying about it when I had sent a previous check list of things to verify. If I had access to the systems the problem would have been resolved in a few days rather than months.

Company B) Developers own the software and hardware from end to end. In my current company we have to package the software up into a deployment system and deploy it that way. However we do have full access to all the systems. Can/do we do hacks and quick fixes? Yes, if the situation warrants it. But in the end it has to get rolled into the official distribution for it to be correct. Can it be abused? Yes. But that is why the culture of the company become very important. In the end you either trust your developers to do the right thing or you don't. If the company can't trust the developers to have ownership of their code and systems.. Well then at least for me I would say I'm working at the wrong company.

FYI, I enjoy working at company B far more than I ever did at company A. Given a choice I will never go back to an environment where developers don't have access to production.

Comment: Re:Everyone ignores Commodore (Score 1) 301 301

On the C64 you had to move the ROM out of the way to get to the RAM underneath. I don't remember the exact details but you could either see the RAM or the ROM and it was controllable.

If you want to get into memory expanders the C64 had at least a 512K ram expander available. I remember having one and it worked with GEOS at least.. might have been used as a form of ram drive to speed up games as well.

The drive drive was a computer in itself that you could buy ram expanders for and run programs on. Typically used for increasing load speed or duplicating copy protected disks.

Comment: Re:wrong logo (Score 3, Informative) 312 312

He is the Chairman of the Board and was representing the company during the annual shareholders meeting.
That doesn't fit the whole he doesn't really work there anymore statement.

When he isn't on the board and isn't representing the company at the shareholders meetings I'll believe he doesn't work there anymore.

Comment: Re:Netalyzr ? (Score 1) 194 194

Yes because that couldn't be exploited at all..

What's that? The malware/trojan/root kit installed it's own root-certs and is running a proxy listening on and
That proxy is snarfing up all the data and shipping it off to some other server...

Just because you can't imagine how it could be abused doesn't mean it can't be abused.


Revisiting the "Holy Trinity" of MMORPG Classes 362 362

A feature at Gamasutra examines one of the foundations of many MMORPGs — the idea that class roles within such a game fall into three basic categories: tank, healer, and damage dealer. The article evaluates the pros and cons of such an arrangement and takes a look at some alternatives. "Eliminating specialized roles means that we do away with boxing a class into a single role. Without Tanks, each class would have features that would help them participate in and survive many different encounters like heavy armor, strong avoidance, or some class or magical abilities that allow them to disengage from direct combat. Without specialized DPS, all classes should be able to do damage in order to defeat enemies. Some classes might specialize in damage type, like area of effect (AoE) damage; others might be able to exploit enemy weaknesses, and some might just be good at swinging a sharpened bit of metal in the right direction at a rapid rate. This design isn't just about having each class able to fill any trinity role. MMO combat would feel more dynamic in this system. Every player would have to react to combat events and defend against attacks."

The rule on staying alive as a forecaster is to give 'em a number or give 'em a date, but never give 'em both at once. -- Jane Bryant Quinn