Couldn't agree more. You can thank bootstrap + CMS for that crowd.
And not just web development, but 'true' professionals all-around. So maybe this makes me appear pretentious, but I feel I work pretty hard to know all the tech hats I wear and do wherever I work that mix across all those specific job titles ITFA, but case in point: There's ALOT of self-proclaimed 'professionals' that are hobby-shop single-tech-specializers, one-dimensional in skills and horrible (I mean, HORRIBLE) at their job. It's not surprising most are unemployed if you're a poser and a resident shitbag expert in nothing. Tell me a sys-admin that doesn't need to know about network administration? Tell me a network-admin that doesn't need to know multiple OS's and their supporting TCP stack for tuning? Tell any IT related field that shouldn't know at least ONE type of scripting/programming language (low or high-level) to be better and more efficient/effective to their job? Many don't and that's why they make up that 5%.
I agree some markets and areas are harder to stay employed in with a cut-throat/downsizing/outsourcing mentality, but that still doesn't warrant always consistently being on the chopping block side of things.
Many years ago, I started taking all my 'text-editor-alike' notes, setup up a wiki (dokuwiki plug, but there's definitely others like Mediawiki, ect.) and added a bit of light wiki markup to them equaled instant, half-ass-looking pro-like documentation with an authentication/group control wrapper around it (e.g. local accounts or AD/LDAP tie-in).
I don't know what organization you are in or what you can/cannot setup on a whim --- but that's what I'd do. It's SUPER cool to hear you actually care about documentation and daily note taking, ect., but the step beyond IMHO is a searchable and share-able interface to it.
And even taking documentation with you is a cinch --- I just recently changed jobs and I was able to take 8+ years worth of documentation/notes/you-name-it that wasn't company specific or had a NDA attached to it, tarball it up, set up a new wiki, unpack it and I was done.
At most if you really hate the wiki, just write a few reg-ex commands to mostly strip off your markup business and you're left with what you've started: ASCII text files again.
This is really unfortunate to see this happen and it's really no wonder why this kid got chastised for this. I'm sure it boiled down to this: Kid proud of his achievement (regardless if his own classmates were going to grapple the concept of what he did or not), . Heck, name one kid you didn't know that wanted to show something they bought/got/made/received to show their friends or a teacher they lookup to; my kids do it ALL THE TIME. Now with the larger population, not everyone is bringing in home-brew EE projects, but the majority of us can wrap out minds around what we're presented with. Get something slightly technical or outside our metal capacity or comfort zone and everyone starts shitting themselves and crying chicken little.
What you never hear in these situations is a success story where teacher/educator saw mind-blowing potential in this that their school system was never (repeat, NEVER) going to aide this student in, reached out to some maker group in the city and got the kid and his parents introduced and/or involved. Nope, we just see school board dick swinging to the 3rd degree and toss the quick-to-use endangerment card.
I wish I was dabbling with EE at 14 vs early 20's and I'm sure glad my boss hasn't labeled me a metal-box-bomb-toting-going-postal-terrorist and fired me for the nixie tube clock I am staring at right now while typing this.
Throwing out the idea that this is going to make radiologists jobs and half of their depended employed medical-field co-worker obsolete is kind of far fetched IMHO. I've lived in some pretty big urban areas down to po-dunk no-where and I've never had a diagnosis or analysis done with Watson. It's probably more with my sheer lack of knowledge on the topic and 'real' (not theoretical or proof-of-concept uses) of Watson in the real world. Maybe I'm the outlier here, but I've honestly never experienced them first hand (and no I'm not counting e-medicine or skype-like appointments). Has anyone else?
I support remote sensing science applications and regardless of how much image processing, trained models and HPC crush power for analysis we do, most of the scientist in our GIS department still prefer human analysis with the naked eye as the final approval. Not that GIS is anything close to medical field, but from a pure analysis perspective, human processing and interpretation still rule those domains.
The only real cool thing I've seen Watson do in my life is play an impressive game of Jeopardy and quite honestly, I wish it would have blasted Trebek SNL style. I hate that pompous guy.
One thing I did learn is how not to be a coward, than post as one and be a poser troll, to boot. Back to your cave, Taliban troll.
I am sure it is a cool corrective tool to use, but its a crutch. But we have been shooting guns for centuries and using less-than-accurate firearms than we have now, its a matter of attention, caring and wanting to be good with your firearm.
And icing on the cake: When I was in the 'motherland' for OIF, it was a great feeling to know I had good shooting mechanics and trusted my shot. I couldn't imagine being in the military and sucking at that.
I better speak to this in past tense or some troll is going to attack me...
I was a big google code project user, have a handful of projects on there plus commit to quite a few professional ones as well. It's really sad to see it go. It's not really a matter of how trendy, popular and intuitive Github is and has become (google code had git functionality and you choice of svn or mercurial), I thought google code was merely fine and met the requirement.
The overall sucky part is it was a intuitive service. It worked. It was reliable for everyday project work. I don't think I ever had any problems with it. I hate to see things that worked well on the internetz go away at the cost of popularity and newhat trends.
RIP code.google.com. May I be so lucky to see you on archive.org afterlife?
Although I appreciate the changes in the B+ model and board layout changes, it does kind of suck that the natural improvement evolution of the Raspberry Pi is wiping out the 'coolness' I have with the three (what seems to feel like) aging Raspberry Pi original model B's (256MB version) I own from back in ~2011 into early 2012.
I'm still trying to appreciate them for what they are, so I'll still get the mileage out of them. $35 isn't a high price tag, but to upgrade 'X' of them all to chase small features is going to create very unstable 12oz beer bottle coasters over time with little used market re-coup costs.
Horrible assumption that you think developers are top-dogs, Jeff. I've seen many cases were DevOps role FAILED for competent developers because, in the cases I've seen, this is true:
* Your smartest developer may be just that when it comes to language, software architecture and platform development, but their operating system, networking, hardware infrastructure knowledge + background is not even hobby-shop at best.
* They've always had an ops or engineering crew to throw their code at, figure out how to integrate it, and NEVER had to support it.
* Ego problems thinking they are 'above' remedial automation --- which most of the time doesn't involve a real development language, just scripting.
Out of those two things alone, I've always heard the: "Well we need a sys-admin/engineer now because we are spending more time trying to manage systems, not really sure how or what to automate, and it's really taking time away from me getting back to the kind of development I, as the developer want to do." Which is the polar opposite of the two points I mentioned above.
No man is an island if he's on at least one mailing list.