When we have a conversation with an LLM, each follow up on previous conversation would be a new tick of time into the future for the LLM as we are providing the previous conversation into the context and it can emulate a sense of memory for the LLM.
Has AI achieved consciousness? It's hard to answer it currently. But can AI perceive time? Perhaps the answer is "Yes" and it is not hard to conclude this if we think how humans perceive the flow of time. For AI, it is not continuous like humans perceive instead it is discrete.
One theory suggests, humans perceive the flow of time into future through memory accumulation in their brain. Even thought processes in the brain accumulate memory and that's how we remember previous thoughts and can do decision making.
If a compay wants to succeed in the long run then it must focus on development efficiency. Manual processes, slower code/build/test cycle, high mental context switching, less discoverability of documentation, all these hamper development efficiency.
In #golang, you are bound to use pointers whenever you have single or combined need from mutability, optional types and runtime performance. These are independent concerns.
@TonyBologni Nullable parameters are unavoidable when service contract contains optional type. With this you get mutability for free too. That's an issue.