OSCON is held every July in Portland, Oregon, and focuses on open source solutions to all sorts of IT needs. They have specific tracks for public sector and education. Plus, there's good beer.
CSS/JavaScript/HTML5 is plainly obvious. Everything from Microsoft to mobile hybrid development relies on this these days.
C# is the standard language of the Microsoft stack --- in fact, the bulk of MS-stack training is in C#, with only a smattering in VB.NET.
Java is the COBOL of the early 21st Century. It isn't sexy anymore but it will always be around.
PHP is used in a lot of web applications. I wish it weren't. In fact, I'd really rather see Ruby on Rails take over this space.
If you're going to program native code, you could learn Swift, sure. You could also learn Rust (Mozilla's systems-level language with significant buy-in from Samsung) for device programming. If your goal is to write native apps, your best bet for Android is actually Java. By the way, one can also design native apps in Java (the code is Swing-like) and compile them to native apps for iOS or Android using Codename One, and I imagine a few shops will pick up that practice.
I like Erlang as an honorable mention. I'd also add two others: Python (especially for data analysis) and PowerShell (which will set the grown-up Microsoft sysadmins from the point-and-click kids).
So...Dr. Tannenbaum's other project is Electoral-vote.com (2), an election prediction site (and one of the first). Any clue what's going to happen to that?
I'm sure this technology has a lot of potential. Right now it drives me nuts just looking at it. The windows jitter too much and make me want to take my glasses off and rub my eyes 5 seconds into it.
The difference is that ASU will actually confer a degree for all that online classwork, provided the student gets good enough grades. Once can even obtain degrees in EE or CS through their online program. The main thing the student misses out on is campus life.
Remember Skylab? It was America's first space station, and lasted 1973-1979 (before it burned up on re-entry). We got a lot of good science out of that station, and maybe it's time we do it again.
Get the FCC to allow ISPs to make sweetheart deals with content providers, but subject to FCC supervision. (Done)
Starve the FCC of resources so that supervision becomes impossible. One way to do this: refuse to appoint FCC commissioners, so that they can't form a quorum --- just as happened to the FEC in 2008.
...is how do you get a job and then succeed at it for longer than a year or so.
For that second part, my main recommendation is this: Don't be a bottleneck. As to how to carry out that part, there's plenty of good advice in the comments above, but your goal should be to solve problems quickly and produce solutions faster than expected whenever possible.
The grandparent post ("And people still assert this...") cites actual data. The parent post cites a movie and a demotivational poster. Which is the better argument?
I've had mine 15 years. I had to buy a PS/2 to USB adapter and occasionally clean out built-up dust. Once in a great while I miss not having a mouse wheel. Otherwise it's given me no issues. Added bonus, it's saved me from carpal tunnel.
90% of your changes won't have any effect on production systems. Just lump those together under "Routine changes to UNIX/Linux production environments" and explain that you've tested those on your sandbox network.
10% of your changes will impact your production systems, even if it's just because it's upgrading Apache or some Perl module that your systems use. This can be as trivial as "updated Perl module; ran complete unit, load and regression tests, everything works fine." to "This is a kernel patch that requires us to power cycle each box. Here is our plan to do this in a way that generates no application downtime." Those are the changes CAB is meant to catch. Document each one in a different request. Document them clearly and thoroughly. Run them by people whom you trust to write good English. Make sure that your deployment, testing, and rollback plans are solid, and document them thoroughly in each request.
After a while, you'll get really good at this, and people will trust your requests.
In my experience it's much easier to get Linux in the workplace as a server, and here there's lots of areas where it's as good as or better than Windows. Start with a LAMP server for internal web; use it to host a Wiki for documentation.
Slashdot Mirror
OSCON is held every July in Portland, Oregon, and focuses on open source solutions to all sorts of IT needs. They have specific tracks for public sector and education. Plus, there's good beer.
CSS/JavaScript/HTML5 is plainly obvious. Everything from Microsoft to mobile hybrid development relies on this these days.
C# is the standard language of the Microsoft stack --- in fact, the bulk of MS-stack training is in C#, with only a smattering in VB.NET.
Java is the COBOL of the early 21st Century. It isn't sexy anymore but it will always be around.
PHP is used in a lot of web applications. I wish it weren't. In fact, I'd really rather see Ruby on Rails take over this space.
If you're going to program native code, you could learn Swift, sure. You could also learn Rust (Mozilla's systems-level language with significant buy-in from Samsung) for device programming. If your goal is to write native apps, your best bet for Android is actually Java. By the way, one can also design native apps in Java (the code is Swing-like) and compile them to native apps for iOS or Android using Codename One, and I imagine a few shops will pick up that practice.
I like Erlang as an honorable mention. I'd also add two others: Python (especially for data analysis) and PowerShell (which will set the grown-up Microsoft sysadmins from the point-and-click kids).
Have you read Professor Dreyfus's objections to the hopes of achieving "true AI" in his book What Computers Can't Do? If so, do you think he's full of hot air? Or, is the task of AI to get "as close to the impossible" as you can?
A glass of the finished product, sampled at a downtown restaurant, tasted about average for West Texas.
So the water tastes like shit. Good to know.
So...Dr. Tannenbaum's other project is Electoral-vote.com (2), an election prediction site (and one of the first). Any clue what's going to happen to that?
That means I have to REALLY step up my Python chops if I want to compete.
2.x or 3.x?
I'm sure this technology has a lot of potential. Right now it drives me nuts just looking at it. The windows jitter too much and make me want to take my glasses off and rub my eyes 5 seconds into it.
The difference is that ASU will actually confer a degree for all that online classwork, provided the student gets good enough grades. Once can even obtain degrees in EE or CS through their online program. The main thing the student misses out on is campus life.
While true, Verizon doesn't come to all neighborhoods - and there's no way I'm doing business with Comcast.
Remember Skylab? It was America's first space station, and lasted 1973-1979 (before it burned up on re-entry). We got a lot of good science out of that station, and maybe it's time we do it again.
If you're a Manager and you have an Android, the other Managers will laugh and you, or at least not take you seriously.
Q: Where'd you hear that crap?
A: A well-respected management consultant, who otherwise knew what he was doing.
I can hardly wait for my EmacsBook!
Surely you mean C-x C-s.
Headline: "Comcast predicts storage cap"
Story in a nutshell: Comcast exec predicts bandwidth cap.
WTF?
...is how do you get a job and then succeed at it for longer than a year or so.
For that second part, my main recommendation is this: Don't be a bottleneck. As to how to carry out that part, there's plenty of good advice in the comments above, but your goal should be to solve problems quickly and produce solutions faster than expected whenever possible.
Since Node.js made it possible to write server-side logic in JavaScript.
Red Hat Military Edition? Killbuntu? Debian For Drones?
The grandparent post ("And people still assert this...") cites actual data. The parent post cites a movie and a demotivational poster. Which is the better argument?
I've had mine 15 years. I had to buy a PS/2 to USB adapter and occasionally clean out built-up dust. Once in a great while I miss not having a mouse wheel. Otherwise it's given me no issues. Added bonus, it's saved me from carpal tunnel.
If true, this is great for Detroit. That said, what the heck is the "natural average" of job growth?
90% of your changes won't have any effect on production systems. Just lump those together under "Routine changes to UNIX/Linux production environments" and explain that you've tested those on your sandbox network.
10% of your changes will impact your production systems, even if it's just because it's upgrading Apache or some Perl module that your systems use. This can be as trivial as "updated Perl module; ran complete unit, load and regression tests, everything works fine." to "This is a kernel patch that requires us to power cycle each box. Here is our plan to do this in a way that generates no application downtime." Those are the changes CAB is meant to catch. Document each one in a different request. Document them clearly and thoroughly. Run them by people whom you trust to write good English. Make sure that your deployment, testing, and rollback plans are solid, and document them thoroughly in each request.
After a while, you'll get really good at this, and people will trust your requests.
In my experience it's much easier to get Linux in the workplace as a server, and here there's lots of areas where it's as good as or better than Windows. Start with a LAMP server for internal web; use it to host a Wiki for documentation.
Master Mark will have a field day!