Essentially I am asking you to be that mentor (to your past self) and share the email you could write, specific to YOUR particular coding that you were doing. Think a mentor should include "why"? Then include why.

Remember: I didn't ask for a shortcut, I asked for specific sentences that you could have sent back in time to prevent this:

>months later I was still dealing with the consequences of early bad decisions.

Your sentences can be literally anything, specific to your specific situation, that could have prevented those bad decisions.

So, let's be clear. Your message to the past you reads:

"Hi - I am you from the future. I was asked to send back a message in time listing specific things you can do right now, having just learned Go, based on my having to deal with your code, that can prevent your bad decisions which you will be dealing with months later. It is impossible to put this into English words. So, I have no advice for you of any kind. Fuck you, past-me. And also fuck me - I'll just have to deal with your lack of understanding. I hope you have found this mentoring by me to be as helpful as I have. I don't believe in mentoring."

So, that's the new version of your message, based on your review of your own code and memory of your decisions and learning process at the time.

Well, okay. I guess I accept your viewpoint. (Note: if there's some other reason you don't want to answer publicly, such as not talking about your codebase, you can email me at the email in my profile.)

I am looking for specific architectural advice, using your experience as a case study.