The New-ish Technologies That Will Alter Your Career
Nerval's Lobster writes Over at Dice, there's a discussion of the technologies that could actually alter how you work (and what you work on) over the next few years, including 3D printing, embedded systems, and evolving Web APIs. Granted, predicting the future with any accuracy is a nigh-impossible feat, and a lot of nascent technologies come with an accompanying amount of hype. But given how these listed technologies have actually been around in one form or another for years, and don't seem to be fading away, it seems likely that they'll prove an increasing factor in how we live and work over the next decade and beyond. For those who have no interest in mastering aspects of the so-called "Internet of Things," or other tech on this list, never fear: if the past two decades have taught us anything, it's that lots of old hardware and software never truly goes away, either (hi, mainframes!).
And, here we go again, gratuitously shilling for dice.com.
No thanks.
Lost at C:>. Found at C.
Dice clickbait!
Can you say "recursion"?
"5 Meaningless buzzwords not worth your time"
Yeah yeah these things exist... and have existed for decades.
jail / prison may be the only place to get healthcare. + free room and board on the side.
... you forgot "all the sex you NEVER wanted."
The sad part is that there are already people who are breaking windows and stuff just to get a jail cell to sleep in.
"Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
In IT, there isn't really much that is new. Cloud systems evolved from offsite data centers. However, there are a few things which are important:
1: IoT. Securing these is like trying to use bandaids after someone stood in front of a 3000 rpm gunship weapon. However, if it does take off, one will have to factor in every doodad that might require Wi-Fi, or might have a 3G card so it can phone home and the black hats can hack into it.
2: Separation of the Internet into sub-networks. It is only a matter of time before this happens. With the state-sponsored armies of blackhats, you can't win a war of defense. The only real way to keep your stuff secure (as a business) is to separate out functions with physically different networks (SIPRNet, NIPRnet are examples), so the Internet is not the only means of communication. This involves real leased lines, additional fiber laid, and additional network fabric, perhaps virtual circuits, so only machines that are configured to communicate with each other can.
3: Bit rot, CAS systems, and ensuring files archived are still readable in a media-agnostic way. That way, if finance needs a document from 2005, it doesn't matter if it is on tape or disk, they can obtain it with minimal operator intervention.
This is a two person operation?
Nerval's Lobster works for slashdot, and from his comment history, his entire job is to submit dice.com stories (this is not an exaggeration, as was pointed out to me, go look, it's literally nothing but dice.com posts).
However, he can't actually directly post the articles? So he is literally paid to _submit_ articles to slashdot, but can't directly post them himself? Isn't that a little silly?
Over at Dice, there's a discussion
No, there is a cheesy article with 2 comments. 2 comments does not a "discussion" make.
Quantum computing is the only thing I could imagine altering software development drastically.
Hell, that's s reason for us not to follow the discussion. Seriously.
Dice-related posts are like diversity hires. They may be good, but people are assuming that they weren't picked for their quality.
When I read the headline I thought, "IoT Devices...could alter your career...by leaking all kinds of stuff about you to accidentally connected Facebook, Google+ and other social accounts."
I don't even think people know what they're getting into out there - here's a guy who's at least trying to get his head around what people are thinking about on
IoT consumer privacy.
There are two sad bits about this actually.. that you think this is new, and that people are still doing it. Its been going on for a long time.
It's like predicting how these 'automobiles' will be a big part of our lives (news is 100 years too late, but at least accurate). Predicting the future by simply stating the present, brilliant!
XML is like violence. If it doesn't solve the problem, use more.
the fusion generators come online in 2017
http://hardware.slashdot.org/story/14/10/15/1327230/lockheed-claims-breakthrough-on-fusion-energy-project
and
the diamonoid nanothreads are being constructed for the space elevator
http://science.slashdot.org/story/14/11/17/0249218/scientists-discover-diamond-nanothreads
now all we really need is for the crowd over at miri
http://intelligence.org/
to get the ai's online and we'll be heading out!
How about trying to break in into the prison? If they don't catch you, you're in prison. If they do catch you, they throw you in prison.
It's win-win!
Get free satoshi (Bitcoin) and Dogecoins
Once in a great while, something comes along that fundamentally alters the way the overall practice of computing operates. Everything else is a rehash of the old stuff, with improvements that have been made since its introduction. Cloud computing is just hosted data centers with more flexibility and APIs to control the difficult tasks of resource and application provisioning. When you've been in IT long enough, you see patterns repeat. It's cool when something that barely worked before comes back around with new improvements. But, the buzzword itself is not what you build a career on -- it's the fundamentals that are only learned by dealing with lots of different problems over time. This is why older workers in IT get discriminated against -- younger people seize on the buzzword and deride the older folks for patiently explaining that it's all been done before.
The one thing on that list that did irk me a little is "Web APIs" being listed as a fundamental change to the way we work. It's a change, but not a good one. Admittedly we shouldn't be hand-coding assembler for most tasks, but the introduction of monster "service" APIs and web frameworks gets developers so divorced from the underlying complexity that the "how it works" part is lost. I would say that's the big change...developers can code up something horribly inefficient that works, but they'll never know how to track down the "why" behind the bad performance. And since hardware is virtually free, developers who don't pay the AWS bill directly will just keep consuming the free resource.
Maybe I'm becoming a "Get off my linear lawn!" curmudgeon, but I've yet to see sufficiently common "cubicle programmer" scenarios that show the net benefits of parallel programming (PP).
PP is fairly hard to test and get right such that the human labor is often more than the machine labor savings. And common PP needs tend to eventually get folded into declarative or semi-declarative API's or interfaces, such as RDBMS and browsers/renderers based off of SQL and markup. The database and the browser manage the PP under the hood so that custom application developers don't have to. Maybe the cutting edge or the high-end can always take advantage of such, but most developers don't fall into that. (I don't dispute PP having solid niches, but they are still niches.)
I've asked for realistic examples on various forums, and so far they were pretty weak justifications, rare situations, or a niche need.
Sometimes I get the "Ayn Rand" argument: If you don't squeeze every ounce of speed out of the machine, then you will be replaced by those who can". But typically companies don't want code that is difficult to understand or manage unless the speed advantage really matters. Slow machines are an annoyance, but confused staff developers can result in apps not working at all. It's usually cheaper to buy a new, faster server than fire your developers and retrain a new set on all your shop's stuff.
And often the bottlenecks are fixable by tuning existing linear processes, or farming large-volume processing to a RDBMS (which can use parallelism under the hood. Those building systems software tools like RDBMS will need to know PP well, but that's usually been the case for decades.)
Table-ized A.I.
HTML and CGI -- still the web tech that the smartest people use, now with (ideally minimal) CSS. Sites that are client-executable clean are always the best from any number of standpoints. Sites can, and generally do, work on almost* any browser, almost any operating system, *any* device with even the most basic web browser. Plus you don't get amazingly unfriendly behaviors like menus that drop down without the user asking for them.
C -- still the fastest language other than pure assembler, plus it's reasonably portable and can be *very* portable as you develop the required platform support for GUI, etc.
Python -- changed the face of server side CGI for people who were paying attention, and otherwise, Perl still works fine (even if you have no idea what you wrote an hour later.) Both provide extensive libraries that can give you a great headstart on all manner of projects.
PostgreSQL and sqlite, still on top of the database heap.
Everything else... just noise. It may be entertaining noise, it may even be *fascinating* noise, but still, there's no gain on productivity to be had, and in fact, all the time you waste learning, or forcing your employees to learn, the "latest and greatest" java-infected horseshit, the more you degrade your actual productivity. That, of course, assumes competence was present in the first place. Not a given.
* [versions of Safari won't render CGI buttons as specified.]
[background music] "I'd like to extend a surmise for instantiation of surface-approximate prototypical hands-on pass-arounds in order to provide in-house guidance, as well as a vector for social media sharing utilizing a cloud-resident archival basis. [slide] Moving forward, this will provide seamless integration, representing a pro-active new paradigm that is win-win at the end of the day. [slide] I believe it’s time to synchronize the tactility scale. [slide] As a marketing manager, how do you resolve 110% of rendered graphics material with exertion levels of 130% developed by actual instantiation? [4k resolution animation of hotties fondling 3-D printed prototype suggestively] Unquestionably, pre-OOBE hands-on for our gurus and rock-stars will provide the synergy required for seamlessly moving from concept to actuation. [slide] [credits] Thank you. [corporate logo] [music fade]"
I've fallen off your lawn, and I can't get up.
except for the suggestion about healthcare. the very idea that you would get timely or otherwise adequate healthcare in the US prison system is outright absurd. you do NOT want to find this out firsthand.
Perhaps he was too busy inflicting TeX on us?
I've fallen off your lawn, and I can't get up.
Deer have mollusks?
I've fallen off your lawn, and I can't get up.
* including 3D printing,
Nope. wont change my life or work. For the things I am involved in it is either too expensive, or already relevant.
* embedded systems
Nope. changed my life already. I saw how the analog chips which we used in the end of the 90s for signal processing became obsolete and unavailable/expensive (-> Burr Brown being bough by TI) Not a new tech at all.
* and evolving Web APIs
Oh yeah, because that going to mache such a big difference
Anything that has a number in title will be garbage (or otherwise redundant). LinkedIn is full of "The six ways that you can succeed at your next interview", "The Top Ten techs of the 2010s". "The Seven Programming Techniques you must know"
Kittenman's law is fine. Pat pending.
"The greatest lesson in life is to know that even fools are right sometimes" - Winston Churchill
It's good to know embedded systems are new-ish technology!
Really makes me feel good about the implantable cardiac defibrillators, hard disk drives, engine control units, CNC machines, remote weather stations, mobile phones (baseband), insulin pumps, etc. that I've worked on for the last 20+ years.
A home might have 3-5 desktop/laptop processors in it, while that car on the driveway probably has at least 20, maybe 50, processors in it.
Embedded systems, and the engineers who design the hardware, software, firmware, etc. are kind of like air - all around you, and you don't really notice them, but you sure would if they disappeared.
Now if you'll excuse me, I have a soapbox to step down from, and a lawn in need of protection from young whipper-snappers.
I think the article was a sensationalist clickbait.
Cloud - virtualization on commodity hardware. 1st it was google/facebook/hadoop/specialized, now it's OpenStack
Software instead of hardware - instead of custom boxes, everything in software in a virtual layer - docker even
Tiny custom commodity hardware for low power - small arm/x86 systems for low power apps where an expensive system used to be used - RasPi as web server, Ardurino, Atom, smart tvs.
Networking things that were not & better communication - see TVs, thermostats, clocks, lightbulbs