Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Re:every consumer needs to assume some responsibil (Score 1) 44

So basically I'm responsible, because I didn't write the firmware, and instead it was written by an idiot? Like someone who runs Windows, and is therefore able to turn off Windows Update because it exists in the first place, and could be the very channel which, by means of DNS cache poisoning and/or router compromise and/or BGP poisoning, was the means to infect the thing in the first place?

How about we hold the idiot who thought giving the fridge a routable address via NAT off the local network in the first place, so that they could market specific brands of milk via coupons sent to me when I'm running low on milk, was a good idea, responsible instead?

Comment Re:What a great idea! (Score 4, Interesting) 107

"Shooting drones down will not solve the problem."

Shooting drones down will solve the problem of having drones in the air. That's the problem this device is designed to solve. None of the other things you mention come under the remit of this device, and the device was not intended to address or solve them. This is just the latest in anti-aircraft evolution.

Comment It's clear you do not understand the position. (Score 1) 158

It's clear you do not understand the position. You need to read about what the job entails, and then decide if you want to accept the offer or not. It's a substantial change in role from your current position. In this case, the Wikipedia article is pretty accurate:

As others have stated, your primary responsibility is specification. To do this, you meet with stakeholders, and do projective business IT strategic planning.

While you can relatively easily negotiate for read only access as a demand from "on high", you should not personally use it. It should be used by your staff, temporary or permanent, for the performance of detailed specification compliance audits and spot checks. This is adequate justification to get management buy-in for this type of access. This type of access is for a role, not for a person. This is one of the reasons it should not be you.

For day to day operations, what you need are dashboards, which measure the degree of compliance with the detailed specification in an ongoing basis. The main purpose of the dashboards are to give you information you can summarize periodically to the executives, and as feedback into your strategy decisions going forward (particularly decisions surround capacity planning and technology adoption).

The purpose of the ability to audit is to ensure that the dashboards are not giving you fudged numbers based on what you want to hear, vs. what IT whats to implement (or what they can implement; you may be asking for the impossible, as a dictator, when you should be viewing the detailed specifications as a negotiation). Audits can also provide progress reporting on deployment of specification changes, based on what IT is reporting vs. actual. Since you appear to be planning a lot of churn for them, I suspect you will need one FTE staff member to perform rolling audits to ensure that things are on schedule, and if they aren't, you can negotiate either a schedule change, or a working emphasis (this is a prioritization list: other things will suffer if you have insufficient staff in IT for the demands being made).

Good examples of what you can dictate are things you've complained about: Automated Provisioning, use of SRM in VMWare installations, enabling automated tiering in EMC storage hardware, and so on. Things which will bite the enterprise on the ass eventually, if they are not done.

Your initial dashboards should be based on displaying progress on this (e.g. "percentage of VMWare installations with SRM enabled", etc.).

Note that before any of your shit starts running down hill, you need to make sure you are not downhill from them. To do that, you are likely going to have to have meetings, a couple times a week (usually something like Tuesday/Friday), to collect requirements for the business, and then mash it into part of the requirements document that you will need to prepare before you start defining strategy and dictating conformance/performance). Otherwise you will find yourself buried in crap, because your goals will not be clearly derived from the enterprise goals.

Your ability to take new input from the early in the week meeting and report it in the late in the week meeting with the stakeholding execs is going to be your main performance metric until you go into the design, then implementation phases. Your goal is to get to an ongoing maintenance/change phase. Your metrics will be different in each phase. You will use these in your performance reviews to justify yourself.

If you have other things you care about, they need to be in the specifications -- and they probably need a dashboard, and they need to have a schedule.

For example, if you care about automated provisioning, then you need to have a scratch machine that is identical to the production machines, and you need to have a metric of "how long from a zeroed state does it take to provision the machine and make it ready for service. You would likely break this down further by provisioning category, if all machines are not provisioned identically (it's unlikely that they will be), and you need to have a list of configurations that the dashboard uses to display per-configuration percentage above/below goal speed (translates to downtime), and so on.

Note that for every metric you define, you will need to be prepared to negotiate a baseline acceptability, and then provide feedback into the IT performance review process as well -- and be prepared to give out "exceeds expectations", if they happen to do so -- be fair, do not just be a dictatorial ass: these people are your partners, not your minions.

If after reading the definition of the job -- and reading all of the above -- you feel that you are prepared to take the job, and define at least a rough outline of the stages of getting the processes in place, and demonstrate your progress on doing so to the execs -- and you want the job -- then take it. Otherwise, decline the job, and expect them to either find a second choice from inside to promote. Most likely whoever else has kept their systems up, and also bitched to management about the difficulty in doing so due to the environment, an outside person who can do the job, an outside person who's basically going to be a NOOP, or, worst case, an outside person who thinks they can do the job, but who will actually screw everything up. In other words, you should also think carefully about whether or not you can afford the risks of not taking the job, even if it's not entirely to your liking or inside your comfort zone.

Hope that all helps.

Comment every consumer needs to assume some responsibility (Score 1) 44

"every consumer needs to assume some responsibility"

Really? When *I* go online, yes, I have to assume some responsibility.

I hold the "things" up to the same standard: when the "things" go online, *they* have to assume some responsibility. It's not my f***ing fault if my fridge wants to surf the web, it's the fridge's fault.

Comment Re: Aha! (Score 5, Informative) 434

It's true, and to stay out of legal trouble, most now put it in their terms and conditions.

Citation or you are spewing garbage.

If he won't, I will (simple Google search, which you could do, if you knew how to work Google):
"You also understand and agree that there are users and members on the Site that use and subscribe to our Service for purely entertainment purposes. Those users and subscribers are not seeking physical meetings with anyone they meet on the Service, but consider their communications with users and members to be for their amusement."

In other words, they find it amusing to troll people, and some of the people who troll people may or may not be employed by the company.

Comment Re:The actual finance guys I know want interest up (Score 2) 106

The day traders I know are afraid it's going to kill their ability to make money.

Day traders don't care.....if the market is up, they go long, if the market is down, they go short. What they want is volatility, long, predictable swings where they can jump in and jump out.

Money being sucked out of the stock market into the bond market reduces stock liquidity, which in turn, reduces stock volatility. Day traders rely on more or less large swings in stock prices, and when major holdings are not in play (because there are none, if all the institutional investors have fled to bonds), then their ability to profit evaporates.

Day trading is generally based on options with a limit order (to reduce downside risk, since they can't use the Black-Scholes or Black-Scholes-Merton hedging model in order to balance risk via bonds and other longer term instruments -- since they are *day* traders). There is the possibility of using ETFs in order to hedge risk, but then the upside is considerably reduced; generally, to lower than the brokerage fees, so it's not an option (pardon the pun).

Comment Re:I'm from Mongolia (Score 2) 195

Desalination plants are also used for treatment of alkali water.

"A new report from the Asian Development Bank sent a warning signal to Mongolia that, despite its wealth of natural resources and pristine image, the country faces a severe water scarcity and quality crisis"

So if you can't fix the quantity, fix the quality.

Comment I'm pretty sure the interconnect bus is not the is (Score 1) 108

I'm pretty sure the interconnect bus is not the issue.

The thing that slows down most ARM devices is the memory controller, which is why iPhones are such a win: the PA Semi folks were able to speed up the memory controller considerable, but only for Apple's chips. The nVidia people have made some forward progress, but the bottleneck is still the memory bandwidth making the graphics (among other things) pretty crappy. They are almost an order of magnitude slower than the A9. If you had an A9 at the core of these things, yes, the interconnect would become the bottleneck, but good luck sourcing Apple's hard-won designs.

The secondary problem is that the parts are not uniform between models, meaning you can't depend on anything but the lowest common denominator, which translates to intentionally limiting feature so that this will run on everything. This include using older API sets because not all of the phones can run the latest (which is what you expect, since that's sunk cost, so you lose out on any of the modern features that would compete with integrated phones. A lot of this has to do with carrier certification for the combinations of components, which go up by a power of two for each ne possible module you can plug in.

The idea is pretty doomed due to the least common denominator alone, even ignoring that it's a s mid-mash, and they are using real software engineers of component isolation and interface contract. In other words, it's a mess of epic proportions;

Comment General answer: no (Score 1) 106

General answer: no

Less general answer: most startups come from the U.S., not China; the economy is bad in China and Greece (and maybe two other EU countries, who are now regretting letting Germany be in charge of their economies, the way Germany wanted to be in WWI and WWII), and that's not a problem for the U.S.. This is not like the dot bomb, where everyone was afraid to invest in startups, who were going to lose money on every customer, but make it up in volume.

Comment Re:Ignorance? (Score 1) 233

Theocratic busybodies are no good at answering that question..

Now at what point does a human first gain anything considered consciousness? That has yet to be proven, but most guesses put it at or around 15-20 weeks of gestation; around the same time the brain forms...

Actually, cognitive psychologists put it at the point where someone can recognize themselves in a mirror. So if you are disinclined to accept religious involvement in definition of civil law because of a little thing called the Establishment Clause of the 1st amendment, i.e.: "Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof...", and you happen to believe in the separation of church and state... they can go pound sand.

We should no more make laws based on precepts of Christianity than we should make laws based on Sharia.

"The fundamental principle of science, the definition almost, is this: the sole test of the validity of any idea is experiment." -- Richard P. Feynman