Strong disagree on this. Logs should serve a single purpose of allowing developers to introspect issues with their applications. If you want to generate an event stream, a more flexible and stable architecture would be to emit events deliberately.
Imagine you build all sorts of dashboards and Workflows on top of logs or log based metrics and the dev team changes the structure of the logs or just stops logging. Suddenly all your analytics is out of whack; this is because you created a hidden dependency.
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.
I used rocketbook for a time and it worked really well. Just the erasing and having to use specific pages to take notes on meant I couldn't just grab anything to take notes on and archive it with search capabilities.
This seems like it could be nice to tinker with building something similar.
I prefer hand written notes but prefer to be able recall the notes digitally from a search.
I think the terminal output is the figma viewer. I have a hard time seeing the point of the role and software if a front end developer has to hand translate the design to actual code or styling.
A try, I’ve been using it for a few months on both m1 and x64.
It works really well.