Well you know..that's just like your opinion man.
Opting out of this site at this point. A bunch of 6-12 year idiots (recognizably) telling people what they think they know that they don't know. It's silly recursive.
Substantial proactive improvements not relevant to the same build|OS which comes full circle to the linux comment which is so hated. That is: anyone with source and knowledge can make it work and those without...blackscreen.
Don't think that was where I was going. It was more of the none of this stuff is really done, it is hard in this language and help would be appreciated..as understood through the project splash page and then examined through commits?
And the last windows 7 update black screened my pc and left me in limbo till I was able to restore. What exactly is your point? Windows is not a standard to be held higher than..well anything.
This is a great little read and encapsulates the other side of the 'rethink the way' trend-ism of some HN new lang advocacy. C is fine, C is good. It is widely understood, it is a systems staple, and it is not dangerous in knowledgeable hands. Rocking the boat is fashionable.
The common culture/perspective point is the most important single factor in the old vs young workplace decision.
It's the 'Hey nineteen' phenomena.
At almost 50 the desire to spend 8 hours a day with 20-30 year olds, encouraging enthusiasms, persevering in mentoring and then learning/acceptance of new ideas/tools, being persuasive about experiences in project scope/direction and contributing as part of a growing creative team effort is exhausting.
Not to mention the older you get in this industry you see a lot of reinvention/progress the 'wrong way' (or blatant ripoffs done for profit) which you just become opinionated about.
As an old SA and systems programmer my exposure to 'js everywhere' (node + angular -w- nosql backend) has convinced me that it's best left to hobbyists and experimenters. The same kind of folks that liked the
gentoo linux distribution. If you can make your business run with js front to back good for you. I don't want the pain.
Javascript + the node paradigm is such a bad systems approach that I've never even bothered dealing with learning it to any extent. One look at an async waterfall and nested callbacks + libuv 'transparently' handling blocking routines was enough for me.
One open plan work environment story. One and only.
Lasted three months there. Noisy, smelly (kitchen nearby),
and the head counters would come by every couple hours to see who was at their seat and who wasn't. You don't have to be uber employee to fail to appreciate the master plan and want out of this type of thing.
Agile + scrum were transparently about providing leadership/managers with a reason to be involved at higher rates of compensation. Streamlining customer/developer communications or promoting the creation of well designed solutions were not part of our agility. We didn't need paid moderators to chuckle at our jokes, enjoy our insights, and make bad decisions on our behalf.
Devops and the whole automation phenomena I ignored till the realization creeped in that companies were hiring HR folks who thought that automation and the anti-pattern of SA OPs were silver bullets 'everywhere'.
The tools that are in use that have become part of the devops 'stack' like ansible and chef or jenkins and atlassian and all this...cruft. If I want to deploy and CM for *nix please don't tell me I have to work with Ansible specialists doing deploys and orchestration + CI and builds behind some Atlassian sales masterpiece.
You may not be able to hire someone who can understand our shell scripts and deploy|test automation for cheaper than us but you actually have people who can write a shell script and diagnose a systems problem without handing off
to a developer to decipher '312:yaml malformed button hook, dict value unbuttoned.'
I'm just a veteran of some psychic wars and probably don't know what is good for me though. :)
Surprised no one else has commented on this. Worked on EHMP recently and that is a huge, huge project that was never going to leave the ground. It was apparent pretty quickly that it was a paper tiger. Technical debt everywhere.
It's no surprise that EPIC or someone else will step in after enough $$ has watered the contractor landscape. Business as usual.
Worked in the industry for the last 20+ years as a network engineer, sysadmin, test engineer, systems programmer and security analyst.
As I've gotten older (almost 50) and IT employment has become more structured (with new approaches devised to make business and processes more profitable and controlled (agile, devops)) my interest in the field has waned. I still like the creative aspect of the work where it pertains but if I was in corporate IT (instead of small scale hybrid cloud, HPC and scientific computing) would rather do something else.