So you're saying that the splitters are split into two groups? One group which knows when it's a good time to split, and the other group which doesn't?,
Financial security is the reason - if people don't have financial security, they'll expect their children to care for them in their old age when they're unable to earn.
That's the case in most (all?) immigrants cultures - children are expected to, and do, take care of their parents in their old age (exceptions are always there ofc).
After families are established and have financial security, they no longer need to rely on their children in their old age - at which point it becomes a choice.
Perhaps -
1) The people in the richer society are exposed to more ideas and options than the people in poorer societies, which makes them evaluate having/not having children vs "have them because everyone does it"
2) The people in richer societies have a social security net/wealth to fall back on in their old age, whereas the poorer societies are always "hand to mouth" without having the luxury of any retirement savings - all their time and energy goes just for basic survival - and they need children to support them in their old age.
Personally, I'm planning to learn about the internal implementation of databas(es), starting with the book Designing Data Intensive Applications.
This is so that I learn about the current ways data is stored
I cope by reminding myself that I shouldn't compare my personal knowledge with the combined knowledge of a community - multiple people here are knowledgeable about and post about different areas
FWIW, this is exactly what it's like for me too - "Not enough stimulation and I get distracted easily, too much stimulation and I shut down completely."
Stack trace usually means a full stack trace. I've rarely seen one in production - it's usually for unhandled errors.
Usually it'll be a one line log which will point you to the point in code where it's erroring out.
Sounds like you just want the logs for the [microservice] for a particular failing request, and not the stack trace?
I'm genuinely surprised that a question about a particular failed request could be interpreted as a request to start logging stack traces for all requests. One reason for the surprise is I also believe it would be unreasonable to log the stack trace for every request.
I always try to give people the benefit of the doubt, if my interpretation of something seems unreasonable I like to make sure there's not a more generous interpretation, and give the benefit of the doubt when possible.
Again it's about a pattern over time, not just one instance. I realize I'm consistently not being given the benefit of doubt so I work on my communication. It continues and I start to wonder if it's intentional. To answer your question in the other thread, it seems similar for some but not others.
I think some people form an initial impression of others and that impacts the communication going forward, probably not always intentional. I think also some people try to diminish others through public communication. I don't know if that is what I was experiencing but it could be the case, something to be aware of.
