104 karma · joined May 6, 2021
Now you hopefully have a good block diagram and then you can attack every component in it in the same way.
This is the basic view where you really haven't explained any use case or at least not directly from the perspective of the use case. You've just explained the building blocks. Like with a car you would say it has 4 wheels, a trunk, some seats, a steering wheel, and so on, but even without describing what the hell you do with all of this, people still can get the point.
However, you can if you want to, get into more dynamic behaviours as well, often with sequence diagrams.
Especially on the lower levels perhaps flow charts start to make sense, but you are starting to get more into implementation design here than architecture.
Forget about fancy tools. This is creative work just like programming. Use something basic. Visio, OmniGraffle, Miro, Dia, ...? Or something automated if you prefer.
- use the _s variants of the string manipulations, since they are safer and protect against buffer overflows, e.g sprintf_s
- perhaps poll more often, but only print when there is a change in the output, e.g. maybe poll every 10 ms and print whenever it passes 1 second
Whoever sued these folks for false advertising should sue Neo4j as well.
Shouldn't Neo4j be sued as well for falsely claiming to be open source then?
I have a very different feeling about the OPs situation though. This is not about junior people asking too many questions or being lazy or incompetent, it is about a personality of people who are just entitled and demanding and just generally bitter assholes. Not typically seen in juniors!
So as I said previously, for most organizations, it would be crazy to the point of lunacy of their infosec team to allow the internet access to internal corporate systems and just rely on those to have been individually secured.
I would dare to say that nobody does this or I'll ask you to please give me the IP address of Google's internal DVCS server.
Take it slowly and rationally though. Do not give them any hint that you are leaving at all and start a slow powerful search for your next adventure. My number one tip? Make sure you get a good manager which is both good to you as well as in control of their immediate environment meaning so that they make sure you can keep your sanity as well.
Google doesn't do what you suggest and I'll throw in another large security-aware company as well, known for their privacy-conscious phones. They protect the perimeter as well as the inside. As does any military organization. Stop spreading misinformation.
> MFA should be integrated at the application layer, such as through an enterprise identity service as described above, rather than through network authentication (e.g., a virtual private network).
They comment with:
> While it’s no surprise seeing multi-factor authentication being a requirement, what stands out is that doing so at the network level is explicitly disallowed. Meaning all VPNs and tunnels – nextGen or not – do not meet the standard.
Which of course is completely untrue. You still want VPNs to connect sites or even client/network and any security expert worth their salt will surely recommend you to have layered security. Opening up your internal network to the internet and rely on every app to do security correctly is a ridiculously bad strategy.
I don't know or care who pomerium is or what they sell, but this sort of anti-advice severely diminishes their trustworthiness.
The main thing I'm disagreeing with is undefining what CAP means. CAP is a very particular proof and the rest I think perhaps we need a new name for.
> CAP has a long history and was originally provided without a proof.
Irrelevant. All of database history is filled with what today is comparatively junk. The understanding has improved and we have better ways of talking about the particular subject matter.
> The proved version of CAP has a very strict definition, but it's not that useful in practice because most systems don't actually follow that model.
It is useful in what it proves, so don't bend the definition. This is my main point. You will have to invent another taxonomy perhaps. We have good names for all the typical consistency models I believe, so we can use those as a starter.
> Most notably, the CAP theorem is often still true when "consistency" is defined as weaker than "linearizable".
This is the type of reasoning that just muddies rather than clarifies.
Yes, for the immediate issue at hand they just want to make money right, but they might be seeing their greater mission as extremely good, for example in providing the best handheld computing platform to the world or whatever it might be and that makes it all OK. To which level that is delusional thinking I'll let you decide for yourself, but I have a lot of first hand experience of how the mind operates in top level C-suits. They almost have to fool themselves to be able to operate and at their core believe without a shred of a doubt in what they do. Whether this comes from starting each morning with Tony Robbins affirmations I do not know.
That's what I hint at with "basic economic theory". Evil Corp X wants maximal returns and there is a price point at which they get maximal returns. They can't just raise prices infinitely, because nobody will buy the service. If a middleman takes a cut then that optimal price point moves. Explaining it as the cut being shifted onto the consumer is too simplistic of a model. A part of the cut is shifted onto the consumer and the rest is lost by Evil Corp B, to maximise their total revenue.
I think fundamentally corporations should only exist for the purpose of the public good. That is what's wrong with America and capitalism in many ways. It's not the shareholders but the public that they should answer to. If it does not serve the public good to take a 30% cut, then they should not be allowed to do so. As easy as that.