Implementation makes a difference. Early versions of NT were quite good, but unpopular because you needed 16MB of RAM (if I recall correctly) to run them in an era when a high end personal computer shipped with 4MB of RAM. Over the years they tried to hold the line, at one point getting the minimum down to 12MB of RAM, but perhaps not coincidentally stability got really bad.
Yes, he designed stuff for our enemy, but if I had lived in the civil war times I might have built something like the CSS submarine Hunley.
With slave labor, no less.
Yes people are limited by their culture and time, but not *that* limited. Braun deserves condemnation for using slave labor in WW2.
in fact, given the increased US involvement and the general unrest in the Middle East it probably pushed back their goals somewhat
Really? You've heard about this caliphate they are creating in what used to be Iraq before the US tore it to pieces?
If anything, I'd say 9/11 was a win/win for those involved.
Sad as it is, you're not far from the truth. Sharks hate and love each other in equal parts, and when they find out someone under them fooled them, they do understand he's too dangerous to be there. But firing him can be dangerous, too - if he can fool you, who knows what else he's capable of? Making him an ally (temporarily, of course, there's no such thing as friendship among predators) is the wisest course of action.
That, in a nutshell, is why the biggest assholes get promoted instead of fired - because the ones making those decisions are the exact same kind of human trash.
Did you mean NetOps? DevOps refers to a development paradigm. If your development paradigm risks actual user-impacting down-time, you need firing ASAP.
Assuming you meant NetOps, can they live with provisioning me at least four (dev, test, UAT, and training) clones of the entire production environment? No? well then, they can make their case to the CTO whether inconveniencing them or our end users will have more of an impact on the bottom line. If the CTO says "go", hell, I'll code right in the production environment - Oh, you wanted that mortgage payment to go through this week? Bummer!
Developers should never have the power to affect end users. If they do, it represents a failure not on their part, but on the entire IT corporate food chain, all the way to the top. Choosing customer-facing downtime over a few more terabytes and VMs amounts to corporate suicide.
Sorry, what part of paying you to do a job requires me to give a shit about whether or not your failed third-world culture doesn't like answering direct fucking questions?
"Rude" does not apply. Breach of contract, however, does. I just wish more companies would catch on to this before they decide to outsource, rather than paying extra for literally nothing more than a built-in scapegoat for any and all problems.
One of the key problems I've run into, not only in regards to ERP, but in general, is that when you outsource all of your development your future is in the hands of someone who doesn't have your companies best interests as their primary concern.
Even in those cases where you get a good service provider (which will depend on the specific people you've got working on your project much more than the company they work for, so anyone who says "Oracle = good" is missing the point) you still run into one of the most fundamental human problems: we suck at communication.
When you outsource something the degree of clear, concise, validated communication required is many times what is required for in-house development (where communication can still be a major problem). Capturing user needs and implementing them in a useful and user-efficient manner is hard enough with a high-bandwidth internal-communications channel. With outsourcing it is almost impossible for the people designing and building the system to get the information they need from the end-users.
So one question I would ask the OP is: how often do your provider's developers talk to your end users? (not your end user's managers, who don't have a clue what the system requirements actually are). If the answer is "never or hardly ever" then in-house is definitely the way to go, because your in-house team will have at least some chance of building a system that will serve end-user needs.
Plug your USB stick or disk or keyboard into the Pi, and if it reports that there's a new not-a-USB-stick/disk/keyboard, you know there's malware on the device.
So I'll make my malware pretend to be a plain old USB stick for the first N hours. Then it will simulate an unplug and replug itself in as a keyboard that types "format c:\ncat
It's a basic principle that if an attacker can compromise your hardware, you're fscked. But it looks like the new part is that the malware can go viral, reprogramming USB devices. Whoever was careless enough to release a USB controller with firmware that can be arbitrarily reprogrammed from the host computer needs to be taken out and shot.
I agree with you in general, but in this case, if you don't know those acronyms intimately, I can safely say you have zero ability to provide a useful answer to the underlying question.
As for the question at hand - They seriously use Access and Excel as the interface? Fire them now. Access and Excel have their place, and enterprise level data access ain't it. Buy a working ERP package that meets your needs, and spend your in-house development time on integrating with something that meets 95% of your needs rather than trying to bolt functionality on to a piss-poor 50% solution.
Although you might at first prefer to work with the Devil you know, the biggest problem with extending what you have now will rear its head when you try to upgrade it to the latest version, and find that virtually all your customizations have broken. Even if you pay your vendor to make those customizations, you may have somewhere to point a finger, but you can still expect months of pain telling them which parts of their own damned software they broke and need to repair.
Therefore, Congress will pass a law making itself exempt from CIA/NSA spying and the rest of the country be damned.
It's already illegal - you think the CIA is going to care about another law to ignore?
he'd have been fired on the spot for lying to his superiors for months and trying to cover up his own incompetence.
The boss can lie to his underlings all he wants. You seem to be going by book-learning on which is which here and ignoring the data.
Allowing the NSA, DHS and CIA (hell, even the IRS, for that matter) to continue to operate as they are allowed to will swallow up the last vestiges of America and its dream.
Don't forget the Fed, which funds all this.
The dystopia exists now but it's not too late to turn back.
It's actually the collapse of the Fed's product that will be the only thing that can scale it back. It could resolve nicely or turn into a nightmare - here's hoping for the best!
So why is lying to Congress not a punishable offense?
Congress used to keep those in contempt of Congress in jails in the old Guard rooms until they agreed to cooperate (or the session ended). The room that's now the House post office was last used in 1934 to hold a prisoner. Both the Legislature and the Judiciary have almost entirely abdicated their powers to the Executive Branch since then.
These days we have a sitting Attorney General who is convicted of Contempt of Congress (which carries a *minimum* one month jail sentence) and roams about freely and the Legislatures' intelligence committees are employed by the "intelligence community" directly (same as the Fed owns the banking committee). The Legislature really has no actual power to enforce its proceedings at this point.
See, this isn't a crime, it's just the employer checking up on his employees' work. I guess a couple of them thought they were due a raise and made a stink. A low-level employee was blamed and will probably be scapegoated/fired to make this all go away and then business will carry on as usual.