https://operatorhub.io/ and "operator framework" (can't find the link to a readme) are the only things that really make sense here. Don't write them from scratch.
Basic idea is that you write a process that monitors your deployment, that reacts to config changes and events. You might end up thinking "Isn't that what kubernetes should be doing already" if you are not addicted to jumping on year-old hype trains. But if you want to do k8s that's the only way to really go. Forget all the other stuff of managing deployments if it doesn't integrate with your operator strategy.
Sadly the author doesn't understand what iterating quickly means. It's not a means of achieving greater performance in a known area, but a means of finding something that works in an unknown space.
So the completely opposite argumentation would've worked. For the last 10+ years we spent iterating over several startups to find how to use this new technology of mobile and internet, and now that we have found most reasonable usecases we can slow down and optimize them.
On the other hand there are always areas we don't know much about, like in the areas of shared knowledge, in the niches. There of course quick iteration continues to be the way to go.
The best way to avoid fraud is to become smarter oneself. It is not that hard to detect once you learned some survival skills. Sorry, but criticising someone as disrespectful for helping people to learn survival skills sounds damaging. A little like not telling your children about sex and condoms because you don't want them to have sex.
Shit will happen. Better be prepared, and better help others prepare. Stop criticizing people who try to help.
PS: He also didn't say that it isn't fraud. He said that besides fraud there are a lot of other ways a video you made could be used in other ways than you intended.
The less experience you have the more you should pay a SaaS. Then when you gain more experience you start using frameworks like self managed ELK stack more. If that is not enough at some point you can roll out your own.
All nice and true (thus upvoted), but it's not really the point he's making. The point he's making is that most modern applications require more than 1-3 developers, and therefore you need to consider the development cost and infrastructure as part of the whole consideration. So he advocates to work on decreasing these costs instead of finding another high-level distributed architecture that is running on centralized infrastructure (the internet) and that is either forgotten in a few months or built by a centralized development organization.
I would very simply summarize it like this: If you know which data you look for and say "give me this piece" then you want to use a hash table. If you don't know what you are looking for and need to filter/search, then you use a b-tree. So actually you want to use both structures regularly.
Not sure how that general principle really applies or if it's just a quirck my brain came up with, though. If you look at distributed hash tables for instance, they are hash tables on a bus network in some sense, but they are used for search/filter tasks over multiple nodes.
e.V. or eingetragener Verein, is a registered non-profit organization that must serve a good cause, imo. Usually used for sports, culture, science organisations etc. It's not a company
Well, you have to fail anyway, so failing quicker might save you some time and get you to a good solution quicker as well. Understanding that should be a core part of any HNer at least. Probably wouldn't hurd the free software world either. (pun intentended)
Is there something a linux user should take note of? Or is it Sandboxie an attempt to reproduce features like kvm/qemu to windows world? Looks like a cool tool but currently not sure what I would do with it besides of what I do with Linux already.
My impression is that monorepo got popular because submodules are too complicated to use on 3+ projects combined together. And I don't mean that the user interface sucks or that it's illogical to use, but most people will tend to use rather less submodules than more, even experienced git users. Therefore I think the breakthrough will come with someone who really understands submodules but has a great idea how to simplify the process. I hope this project may be a step in the right direction. Therefore I want to know more about the internals.
What's the architecture of this idea? Is there a reasonable assumption that it would keep the complexity for maintainers low in 3+ repos having a relationship with each other? If so, how?
I think most people would agree that this is how the game works. Even corps like Citibank would agree that this is the right way to do it, because if you hire someone that is so integrated into their world they also don't have to worry too much about him f*cking them up just because you are his current employer.
But the problem still is, how do you get that guy. There are so many people who claim to be that guy and few who actually are (and would be willing to switch).
Smart people won't switch companies just to earn a more money. Strong relationships are worth more than a bigger paycheck and while you might retain many relationships you certainly can't retain all when switching companies.
Basic idea is that you write a process that monitors your deployment, that reacts to config changes and events. You might end up thinking "Isn't that what kubernetes should be doing already" if you are not addicted to jumping on year-old hype trains. But if you want to do k8s that's the only way to really go. Forget all the other stuff of managing deployments if it doesn't integrate with your operator strategy.