I’m not sure about hidden dependency if the metrics break immediately. Important metrics should have alerts when absent or change unexpectedly.
Communication and the decision to depend on the logs as a source of metrics would be key to keeping these systems connected and functioning.
Taking a dependence on logs based metrics without communicating that is the failing here.
The same breakage could happen by depending on the event being emitted and a developer changing the event structure.
Communication and understanding helps both scenarios, not duplicating the effort by emitting logging for debugging, events for auditing and metrics for business.
My word choices might not have been the best here.
But consider if everyone was able to take the first year at some percentage less of regular salary. Then public funded care available with learning included?
My wife would have preferred this to having exhausted fmla just before giving birth because of early complications.
Returning to work was not an option for her, 6 years later returning to work was one of the most emotionally draining experiences for her.
If you had access to all the necessary information, what would the formula look like that you would have to track at funding rounds to give any early indication that as an employee you're not going to make anything.
This is something that I have been thinking about lately and I am just not well versed enough to know what inputs I need to build this.
I would like to be able to have a some sort of data driven risk assessment.
I would love some input here and would like model this and track when it's time to say goodbye.
A try, I’ve been using it for a few months on both m1 and x64.
It works really well.