When I hear framework I think client interaction - whether cli, API, or web page.
276 karma · joined February 11, 2016
When I hear framework I think client interaction - whether cli, API, or web page.
This is also because I think of mongo as generalist, which may or may not be right.
It seems as though there are better choices for more specific use cases
The only part of the commute that was terrible was the subway. Otherwise, you're getting fresh air walking or doing what you want on the train (reading, side work, or browsing Reddit/hn), and enjoying a nice view out the window in my case.
Obviously a shorter commute is better, but the logistics of the commute make a tremendous difference. If I had half the commute but it was by car and dealing with traffic then I'd probably be in a worse mental state.
It has always been a frustrating thing.
Ideally you set up 3 master nodes, with distributed etcd cluster for state, and enough machines to run your services with replication.
All of which is not bad at all to get started with if you use something like Kops.
Some useful docs: https://kubernetes.io/docs/admin/high-availability/building/
However, either way, if you're really the market for the product then not seeing pricing won't keep you from inquiring.
It would be pretty annoying to have a generator running at home, but no internet (although it certainly still happens with downed wires). Or worse, you have power, but the fiber box doesn't.
With Chrome on OS X I've got pretty used a more or less flawless video experience - kind of forgot what it used to be like.
You can easily add a serializer as a field on another serializer to serialize nested objects.
I believe that's a core part of the training for Navy SEALS.
They push you far past your "breaking point" to realize that it isn't where you thought it was, helping you learn to keep your head about you when in extreme situations.
I'm sure there are plenty of ways to control it, but I'd wager that most will be ignored outside of basic ACL’s.
Often times certain user types should only have access to certain fields in data or be able to query it in certain ways.
Too often I see apps where the developers just assume they have full control since they're making the interface, while it's trivial to watch the API calls and intercept or modify them.
Specifically, the issue I have in mind is the commonly shitty way that trades are viewed (and trades people not seen as educated). Like plumbers, carpenters, hvac professionals, metal workers, etc.
My understanding is that there isn't as much of a divide or poor view of those paths in at least certain parts of Europe. Germany comes to mind, but I certainly could be wrong.
In many professions they also don't properly value experience (fresh graduate, with a degree), but that's another issue.
If anyone has my data, I'd want it to be the one that you can hope is implementing best practices.