Nope, they have fought for decades to avoid that label. The were given the label "Information Service" and that makes all the difference in the world. That enables them to issue poison packets when they suspect things they don't like, to cancel services to people, to double-dip and sometimes triple-dip for communications as seen in cases like Netflix, and more. It has helped them evade lawsuits about discriminatory service on the basis of customers potentially being slightly more expensive, and being able to evade regulation time and time again.

Even as recently as this spring, declaring that since they are not common carriers they can discriminate allowing ISPs to charge Netflix on one side plus also charging customers on the other side.

Reclassification from "Information Service" to "Common Carrier" would be a transformative step for the net neutrality debate, dramatically forwarding the movement. But it would also come with an enormous amount of regulation and the industry really does not want that.

I hope it goes forward.

Not because I want the recording industry to shut them down, but because common carriers are exempt from the responsibility over their traffic. That is really the best solution for ISPs so they are no longer liable for the content that travels over the wire.

ISPs getting reclassified as common carriers is a major step toward net neutrality, as common carriers are not allowed to discriminate over what they carry.

In fact this is not the 68000 but its crippled little brother the 68008, which uses an 8-bit external data bus (as the 8088 is to the 8086). That was also used in the Sinclair QL, which was Linus's first computer before he bought a 386 PC and got into Minix. Could Linux now be ported to run on the QL?

And, if you've not figured out what I'm trying to tell you, my answer in your example would be, "Unless you want to spend two more million and spend 12 more months in development, and COMMIT to that- no."

The idiot notion of not being "negative" is fantasy that some crazy HR people came up with to whitewash over the real problems going on in a given company. You need to not just simply say, "no", but in the same vein, trying to not say no is stupid, crazy, etc. Sometimes things ***ARE*** really negative things and you can't wish/will them any other way.

Sadly, the JIT model is the only way to work in a mess like that...followed up with plans to vote with your feet.

The problem with that particular notion ("Yes, but you'd need to spend...") is that they're oftentimes NOT savvy enough to grok where you're coming from and they'll just hear the "yes" and make you try to jam 18+ months of dev effort into 6-8 months with the typical, classical, predictable failures, in spite of explanations why it just won't work with their notion. They hear "yes" followed by "wah...wah-wah...wah-wah-wah" like on Peanuts animated features when the adults talked. The "yes" means to them it's doable- the rest is irrelevant details as far as they're concerned (And, YES, I've dealt with the kind all too often and quite a bit in the last two and a half years, much to my chagrin...)

If "yes" is part of the answer when it probably ought to be a "no" or a qualified "no", then it's the wrong answer many times. Seriously. Any notions, from HR or otherwise that doesn't allow for a "no" answer from anyone other than executive management is a recipe for disaster.

Bills are not that simple. By the time they are entered into THOMAS for tracking they have already been through many different groups. Lots of fun little additions have been made. Also by design it is extremely difficult to track down who added what and when; there is no button to track down the details of an individual line like you get with version control; it becomes "these were attached by someone" rather than "Sen. Johnson added line 47 requiring additional oversight, then Sen Smith modified line 47 to remove the oversight". Common citizens do not see the change log, they are only allowed to see specific checkpoints.

Critically, these are NOT little 10-line precise changes. Instead, this is a bill that adds some limits to NSA spying, and a bill that re-authorizes the patriot act, and a bill that gives the Attorney General the ability to rubber stamp "emergency production" of business records acquisition without a judge, and a bill that grants immunity ("liability protection") to those who hand over records without a court order, and a bill that pays people under the table for giving information to the government if they bypass the courts and just hand it over, and a bill that allows the DNI and AG to bypass the requirement to declassify information, that is, a bill to decrease transparency and remove important data from federal reports. And more.

It is 7000 words and 46 pages. Many similar bills exceed 100 pages. Some bills, especially those with critical financial items, grow into the thousand page range with all kinds of ugly growths attached.

Hooking that up with an OKCupid style is quite difficult. Did they reject it because of the NSA spying portion? Did they reject it because of the pen register changes? Did they reject it because of the declassification portion? Did they reject it because of the additional ability to bypass the courts? Did they reject it because it re-authorizes the USA PATRIOT act?

Trying to match it more in an OKCupid style, you may really like the beautiful eyes, but find the cluster of moles and cracked teeth rather ugly, the personal history of high school dropout insufficient, the three aborted teenage pregnancies and collection of STD's rather bothersome, and the extensive criminal history and drug additions are not exactly spouse material ... but those eyes, they are really quite lovely.

That's the issue with so many of these bills. Politicians start with an important bill that is very likely to pass, and then attach all kinds of unpalatable features to it.

They are not little 10-line precise changes to policy. This particular bill is 7000 words in a 46-page PDF. Often they are in bills that are tens of thousands of words, sometimes hundreds of thousands of words, and hundreds of pages in length.

It is easy to headline "${PoliticalParty} objects to bill with ${Feature}" but to not mention the fact that the bill included several hundred additional features.

You've got a headline "Thirsty person rejects glass of water", but buried deep down in the details you will read the water is yellow and brown and came from the toilet. The thirsty person will turn that drink down and wait for something a little more palatable.

Very true. Also, different humans have different versions of "most reasonable outcome".

Many deaths through history are caused by quite conflicting goals. War, obviously, is different groups killing over conflicting outcomes. Mafia/cartel/gang/etc kill to get their own best outcomes even though other groups strongly reject the premise.

They saw the cookie-cutter AS degree and passed on him. Not broad-based enough. Probably in a downturn.

Both items are deal-breakers when you're dealing with someone with the levels of experience that were available during the latter condition. (Why get a fresh AS grad, when you can get an SME for roughly the same price? Mainly because the SME's desperate...)

Yeah, you're technically old-school. You were taught a discipline- which, in truth, is little different than learning a trade, to be bluntly honest.

Colleges have lost their way...or worse, they've taken to strip-mining students for all the cash they can bleed from them and the government through student loans.

How many of them are doing embedded Linux and Android projects- and when they weren't, how many of them were using ThreadX, VxWorks, pSOS, Lynx, QNX, etc.?

If you needed to know VS, you were working in the wrong circles. I didn't need to know VS even though it was one of the bigger deals for doing Windows development- I knew how to code C++ and understood and used ATL, MFC, etc. Which, by the way, is the way everyone should've framed it. Not, "do you do VS"?

Which is pathetic for the CC, honestly. Python's doable because it's *free* just like Java was then- and worse, you didn't need VS to do C++...

Dev C++
With MinGW or Cygwin, Eclipse

Sure, it didn't have some of the glitzy stuff MS was shovelling- but you could have pretty much done Windows or Cross-Platform C++ development back when Java was the big rage at the Community Colleges. And this doesn't even get into them doing Linux for all of it, including Java, Python, etc... They're guilty of some of the same mentality that spawned the notion that these idiot "bootcamps" are a good substitute for a discipline or vocational education. The problem isn't quite the thing Mike Rowe's fingering on this- but he's close enough to not disagree at all. They're guilty of trying to strip-mine all the students for all the money they can. Actually teach something? That's too much into our "BoM" on those grads we're pumping out.

Part of the reason you had problems getting a gig was that they saw the "cookie-cutter" Associate's degree and passed on that. You've nothing to offer except coding for them at that stage, regardless of whether that's true or not- because that's the only metric they've got to go off of. If you actually have ability and can pick up the Engineer's trade, you should get the rest of the BS degree you should get (which won't assure you the job...little will, honestly, unless you've got 2-3 decades of the bleeding edge, self-taught through the school of hard knocks...but it'll HELP, all the same...) and work on teaching yourself any gaps in anything they didn't teach you on your own. There's always something that they won't/don't teach you. You have to learn it on your own. Whether it's C++, OOD/OOA, or the like, you're going to have to be able to grab the ring yourself repeatedly to keep employed. The reason they passed on you is the AS degree- because of the "pathetic" I opined on at the beginning. They're not teaching a trade. They're honestly not teaching a good base to work with at most Community Colleges these days. They're teaching you the in-vogue stuff right then (You shouldn't be learning VS, you should be learning C++ which doesn't really and honestly give a tinker's damn where it's being implemented if you've done it right... You shouldn't be learning Java just because the College is too cheap to get proper Windows tools (which, again, is PATHETIC because the tools have been "there" within reach for nearly 20 years...). You shouldn't be learning Python because that's the big main big-deal in dynamic content websites in there with Java and PHP... You get the idea...) In all honesty, it wouldn't endear you to me if I were to hire help with either my Game Porting interest or my Agritech one. In the former, I'd need a self-starter that understands C and C++. They'd need to be adaptable to pick up Lua if they didn't already know it. They'd have to be able to debug code on X86, ARM, and MIPS. The requirements for the Agritech business I'm starting...are similar in nature, along with "getting" embedded coding. That's the kinds of jobs there's currently work for that's sustainable. An Associate's isn't going to help you there unless you can show you putz with that stuff already and can prove you might grow to fill those shoes in a 6-18 month timeframe being allowed to do it. The same goes for a "bootcamp".

And, unless they were wired to move on to other things, either on their own or by way of a proper (mind...) college education, they'll be technically obsolescent in 3-5 years.

Bootcamps are useful for teaching you some new buzzword skill, but they're not the same thing as properly learning a trade or a discipline- they're only truthfully useful for quickly picking up a new set of tools for the trade.

Like others I found the headline confusing. I read it as "Researchers are predicting the use of Wikipedia as a vector for the spread of disease". This may mean that:

• Disinformation and ignorance are diseases.
• Memes and computer viruses are diseases.
• Wilipedia contains information that leads to depression.
• Instructions on Wikipedia lead to substance abuse.
• This is getting entertaining, fill in your own reason here.