It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
DevOps or whatever you'd like to call it; 'site reliability engineer' seems to be the hot new title from where I'm at as a newly-minted one of same, although it seems really to be the latest iteration on "make our app & data infrastructure work" previously known as 'release engineer'. I think that's in large part down it having become more than possible for a solo developer to run enterprise-grade kit for free or nearly so with minimal effort: servers and databases (AWS, Google Cloud, Heroku) version control (GitHub, BitBucket), next-gen build tools (Travis, CircleCI), even metrics (Coveralls, PackageQuality). That's done a lot to bridge the gap between development and administration and made the synthesis of the two a compelling specialization for organizations big enough to need specialists. System administration as a separate discipline is never going to die out but more companies will be trying to hold off on investing in it when they can farm that out to the platforms and hire people who can work on the core product too.
Functional language development is having a moment and I'm hoping it lasts. Odds seem good, but it's still not as easy to find jobs working with these as it is to turn up the old standbys of Java, C#, and PHP.
Data science seems like a gold rush with some really neat things happening and a lot of really stupid things happening. I'm not outright bearish but I wouldn't be surprised if demand for analytics-at-scale were to recede some in the medium term.
Blockchain is an outright bubble. It's about to run into the NoSQL issue of "really, you need to know why you want to use this if you're going to commit" but much, much harder.
Projects based on the elimination of trust have failed to capture customers’ interest because trust is actually so damn valuable. A lawless and mistrustful world where self-interest is the only principle and paranoia is the only source of safety is a not a paradise but a crypto-medieval hellhole.
It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
I think serverless (aka "someone else's server") isn't really a departure from the trend -- more cloud management, more automation, more build & deploy, less and less straightup administration. I don't see container orchestration going anywhere, I'm afraid ;)
I've seen a handful of compelling use cases for blockchain. One involved a distributed database of 3D models/CAD stuff where licensing, authorship, and versioning were all concerns. A peer-to-peer append-only ledger makes sense for something like that, but it's pretty specialized.
Yeah, my naive hope is that serverless would make container orchestration another "auto" layer. You (as in devops) would still need to know how to operate on that layer if needed but you wouldn't really need to write Dockerfile(s) or figure out a way to monitor containers at scale.
Regarding blockchain... I agree, they marketed it (to companies and even consumers) as the next revolution in tech WAY before they actually had something revolutionary to corroborate such statement.
And if you cry wolf too many times... :-D I am sure there are people out there tackling problems the blockchain would indeed solve, I'm not sure replacing PayPal is chief among those (except if greed is your compass because you're not actually solving the trust problem nor helping the user experience).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
DevOps or whatever you'd like to call it; 'site reliability engineer' seems to be the hot new title from where I'm at as a newly-minted one of same, although it seems really to be the latest iteration on "make our app & data infrastructure work" previously known as 'release engineer'. I think that's in large part down it having become more than possible for a solo developer to run enterprise-grade kit for free or nearly so with minimal effort: servers and databases (AWS, Google Cloud, Heroku) version control (GitHub, BitBucket), next-gen build tools (Travis, CircleCI), even metrics (Coveralls, PackageQuality). That's done a lot to bridge the gap between development and administration and made the synthesis of the two a compelling specialization for organizations big enough to need specialists. System administration as a separate discipline is never going to die out but more companies will be trying to hold off on investing in it when they can farm that out to the platforms and hire people who can work on the core product too.
Functional language development is having a moment and I'm hoping it lasts. Odds seem good, but it's still not as easy to find jobs working with these as it is to turn up the old standbys of Java, C#, and PHP.
Data science seems like a gold rush with some really neat things happening and a lot of really stupid things happening. I'm not outright bearish but I wouldn't be surprised if demand for analytics-at-scale were to recede some in the medium term.
Blockchain is an outright bubble. It's about to run into the NoSQL issue of "really, you need to know why you want to use this if you're going to commit" but much, much harder.
I wonder if and how serverless computing will change the role of DevOps. I'm already tired of the docker and kubernetes trend :D
I agree with you with blockhain, if it was ever useful Bitcoin and its creator have not exactly demonstrated how or why. My favorite article on the subject: Blockchain is not only crappy technology but a bad vision for the future
I think serverless (aka "someone else's server") isn't really a departure from the trend -- more cloud management, more automation, more build & deploy, less and less straightup administration. I don't see container orchestration going anywhere, I'm afraid ;)
I've seen a handful of compelling use cases for blockchain. One involved a distributed database of 3D models/CAD stuff where licensing, authorship, and versioning were all concerns. A peer-to-peer append-only ledger makes sense for something like that, but it's pretty specialized.
Blockchain seems like an inherently specialized tool. The grand generalizations seem really steeped in a capitalist gold rush.
Yeah, my naive hope is that serverless would make container orchestration another "auto" layer. You (as in devops) would still need to know how to operate on that layer if needed but you wouldn't really need to write Dockerfile(s) or figure out a way to monitor containers at scale.
Regarding blockchain... I agree, they marketed it (to companies and even consumers) as the next revolution in tech WAY before they actually had something revolutionary to corroborate such statement.
And if you cry wolf too many times... :-D I am sure there are people out there tackling problems the blockchain would indeed solve, I'm not sure replacing PayPal is chief among those (except if greed is your compass because you're not actually solving the trust problem nor helping the user experience).