Non-relational databases have field occurrences. Fields in a document are associated with other data in the same document. Those associates may contain values that occur in other documents' fields. You may have to do multiple queries to pull data from multiple documents (if it's a large data set), but the individual queries are fast.
No, you cannot do fast ad hoc queries in a non-relational document store. No, you don't have anything like normalization in non-relational databases. Yes, managing duplication of data across docs in a document store is problematic.
Node.js developer here. I've written probably 10K+ lines of jQuery code. I wouldn't start a new project using the push-pull DOM based approach jQuery offers. I've written enough React to know it's a far superior, data-driven approach.
Now, I do use Babel, which is a little harder to defend. At some point, there will be no point in transpiling ES6 to ES5 code. But that moment hasn't yet arrived. Node.js still doesn't support ES6 imports, except in 'experimental' mode. I use them because they have a much cleaner syntax than CommonJS require().
As for other libraries--why would you rewrite from scratch code that you can obtain from the internet and is well-tested, often written by people more knowledgeable than you? You should be focusing your efforts on your code business, and leave stuff like data-caching, transport, authentication, animation, responsiveness, etc. to people and companies who are actually good at it. The best you can hope for is to spend time rediscovering all the mistakes they encountered.
For those who can't afford health care though working two jobs, the only way to keep them docile is to turn them against imaginary bogey men. This works, because they don't have an inkling as to how obscenely wealthy the 0.01% are.
And I'll be darned if I'm not some spritely young wet-behind-the-ears coder! How the heck did I ever get signed up for this, anyway? I think it began with Netly News... IIRC, Soledad O'Brien had something to do with it.
Pushing 60. I started as a full-stack developer writing interdepartmental apps using a 4GL. Been an analyst, technical lead, lead architect, embedded systems programmer, and now come full circle to full-stack web development. I've kept up, and currently trying to push my organization from JQuery/Handlebars/Express (infrastructure groundwork I put down 4 years ago) to ES6/React/Redux/GraphQL.
It's hard, because the 40-somethings I work with are Javascript fatigued. They just want the merry-go-round to stop. For me, to stop learning is death. But I appear to be losing the battle in pushing to stay on top of current practice,
But here's the problem: when job searching, the cohort I compete against is invariably much, much younger. I wouldn't have this problem if I had stuck with C++ or Java my entire career. As someone previously posted, I'm an "outlier". The best counter I've come up with is to write about what I know and what I am learning.
I my mind, too many organizations want a "buddy" culture. It's not what I want, I want to do good work and deliver. The best way to gel a team IMO is to always be learning and delivery value to your end-user. Take pride as a team in your work, not in your team standing in Super Mario (that came up in a recent interview I had. Really.)
I agree about the gullibility of some people, just disagree about who we are talking about.
The best chess AI programs are already rated 200+ points above the top-ranked human players. No master today disputes that a machine would kick their ass, even though masters train *daily* against AI programs.
Bill Gates recently acknowledged that their are different kinds of intelligence. We are starting to see how machine intelligence is of a kind we don't understand and won't match. How long we can keep an edge in other types of intelligence is the only point left to debate.
I haven't voted for either party for the presidency in the last several elections. Am I wasting my vote? No, I'm in a solidly blue state, I can afford the protest vote.
Right. "Human intelligence" is a strawman. Computers can't have human intelligence because they lack human perceptions, and will not have the biochemical jibberjab underpinning it.
Human intelligence is actually not that good... we are fooled all the time... hence, Trump!
I just got my head around Swagger, which has umpteen implementations to choose from, and now tackling GraphQL, which has umpteen implementations to choose from. In the meantime, still learning Javascript2015 and trying to use Seneca for microservices.
And while I'm doing that, I have a legacy PHP app to deal with, a legacy Nodejs app we're trying kill, a new Nodejs app that runs our site. And... documenting/redesigning our data model and architecture.
The biggest problem with GraphQL is that much of the documentation assumes familiarity with one or more of: Relay, React, Hapi, Redux, Sequelize, GraphQL plugins (many) and on and on. And... documentation and examples before 2016 tend to be outdated or not working.
It takes me weeks just to analyze all the options available, and pick something that isn't going to throw a dozen new technologies at the team, some of which might already be abandoned.
Slashdot Mirror
Non-relational databases have field occurrences. Fields in a document are associated with other data in the same document. Those associates may contain values that occur in other documents' fields. You may have to do multiple queries to pull data from multiple documents (if it's a large data set), but the individual queries are fast.
No, you cannot do fast ad hoc queries in a non-relational document store. No, you don't have anything like normalization in non-relational databases. Yes, managing duplication of data across docs in a document store is problematic.
Blue collar workers aren't less smart. They are less trained to think critically.
Facts get in the way of a good story.
Node.js developer here. I've written probably 10K+ lines of jQuery code. I wouldn't start a new project using the push-pull DOM based approach jQuery offers. I've written enough React to know it's a far superior, data-driven approach.
Now, I do use Babel, which is a little harder to defend. At some point, there will be no point in transpiling ES6 to ES5 code. But that moment hasn't yet arrived. Node.js still doesn't support ES6 imports, except in 'experimental' mode. I use them because they have a much cleaner syntax than CommonJS require().
As for other libraries--why would you rewrite from scratch code that you can obtain from the internet and is well-tested, often written by people more knowledgeable than you? You should be focusing your efforts on your code business, and leave stuff like data-caching, transport, authentication, animation, responsiveness, etc. to people and companies who are actually good at it. The best you can hope for is to spend time rediscovering all the mistakes they encountered.
but that's because of Spotify and online news feeds. I expect because of that, the U.S. has seen a comparable drop in FM listeners.
Seems like criminals like the anonymity of blockchain currencies.
I would never include gratuitious image in anything I published. Never!
Hmmm... now, why would American society be divided?
https://en.wikipedia.org/wiki/...
For those who can't afford health care though working two jobs, the only way to keep them docile is to turn them against imaginary bogey men. This works, because they don't have an inkling as to how obscenely wealthy the 0.01% are.
I vaguely remember a similar operating system, written by brothers Wendes. As I recall, Microsoft quickly bought them out and employed them.
And I'll be darned if I'm not some spritely young wet-behind-the-ears coder! How the heck did I ever get signed up for this, anyway? I think it began with Netly News... IIRC, Soledad O'Brien had something to do with it.
The first PC I programmed, using Logo. And I didn't have to come in at midnight to find an empty console. 1977.
You only use vi because Microsoft yanked edlin years ago. Try finding that in the Store, sucker.
I definitely overpaid for these two-penny nails!
Sure, that's what all the AI would *like* us to do. You are an AI chatbot sockpuppet, aren't you?
To be clear: I'm not talking about changing what is not broken, I'm talking about addressing legacy implementation issues. Big Ball of Mud stuff.
Pushing 60. I started as a full-stack developer writing interdepartmental apps using a 4GL. Been an analyst, technical lead, lead architect, embedded systems programmer, and now come full circle to full-stack web development. I've kept up, and currently trying to push my organization from JQuery/Handlebars/Express (infrastructure groundwork I put down 4 years ago) to ES6/React/Redux/GraphQL.
It's hard, because the 40-somethings I work with are Javascript fatigued. They just want the merry-go-round to stop. For me, to stop learning is death. But I appear to be losing the battle in pushing to stay on top of current practice,
But here's the problem: when job searching, the cohort I compete against is invariably much, much younger. I wouldn't have this problem if I had stuck with C++ or Java my entire career. As someone previously posted, I'm an "outlier". The best counter I've come up with is to write about what I know and what I am learning.
I my mind, too many organizations want a "buddy" culture. It's not what I want, I want to do good work and deliver. The best way to gel a team IMO is to always be learning and delivery value to your end-user. Take pride as a team in your work, not in your team standing in Super Mario (that came up in a recent interview I had. Really.)
Anyhow, I might try freelancing. :-/
It says so right above the non-compete clause
I agree about the gullibility of some people, just disagree about who we are talking about.
The best chess AI programs are already rated 200+ points above the top-ranked human players. No master today disputes that a machine would kick their ass, even though masters train *daily* against AI programs.
Bill Gates recently acknowledged that their are different kinds of intelligence. We are starting to see how machine intelligence is of a kind we don't understand and won't match. How long we can keep an edge in other types of intelligence is the only point left to debate.
Please check all that apply to your personal belief system:
By answering this survey, you help us identify the whackadoodliest of the whackadoodles. Thank you for your participation.
I haven't voted for either party for the presidency in the last several elections. Am I wasting my vote? No, I'm in a solidly blue state, I can afford the protest vote.
Right. "Human intelligence" is a strawman. Computers can't have human intelligence because they lack human perceptions, and will not have the biochemical jibberjab underpinning it.
Human intelligence is actually not that good... we are fooled all the time... hence, Trump!
enough sed. don't bash me.
I just got my head around Swagger, which has umpteen implementations to choose from, and now tackling GraphQL, which has umpteen implementations to choose from. In the meantime, still learning Javascript2015 and trying to use Seneca for microservices.
And while I'm doing that, I have a legacy PHP app to deal with, a legacy Nodejs app we're trying kill, a new Nodejs app that runs our site. And... documenting/redesigning our data model and architecture.
The biggest problem with GraphQL is that much of the documentation assumes familiarity with one or more of: Relay, React, Hapi, Redux, Sequelize, GraphQL plugins (many) and on and on. And... documentation and examples before 2016 tend to be outdated or not working.
It takes me weeks just to analyze all the options available, and pick something that isn't going to throw a dozen new technologies at the team, some of which might already be abandoned.
So, yeah, JavaScript fatigue.
we'll give you millions of zero dollars. Feel better?
Yeah, it's wonderful.
https://www.theatlantic.com/business/archive/2017/03/economic-despair/520473/?utm_source=feed