In my experience, nothing has helped this more directly than dhyanas (technically these are practices for the mind and is somewhat like meditation, but not exactly). However these are ridiculously difficult and hard to maintain as a daily practice. Currently, as I am aware of, the information on these are not available online and by tradition taught directly. Also I also can not guarantee the teacher you will find would necessarily be a good one.
I learned to use these practices via Babji Kriya Yoga first initiation. (it seems somewhat religious, but actually is not related to any)
What about dressing up for the jog and afterwards showering and dressing up again? Also most people don't have a park in a 5 minute walking distance. I would say for most people they take 10-30 minutes to get to the training place, train at least 20 minutes and then 10-30 minutes back again and then 5-10 minutes of shower. Now that is quite a large part of the day.
I have been a developer for a little more than a month now and what I have discovered is that although the office is open, whenever someone passes you, they treat you like you are in some kind of a no-distraction bubble, even if you get along really well. I have become to respect that culture.
I work in an open office and while I don't get too many interruptions with people coming up and distracting me, the office tends to be very noisy on times and it does interfere with concentration.
I've seen suggestions for good noise cancelling headphones but I don't feel very comfortable wearing headphones for long periods of time.
> In Japan it's very much frowned upon to talk on the train, at least in Tokyo. I kind of like that system.
My experience was different. Random people started conversations with me, including a coy girl on the shinkansen, even though her English was as good as my non-existant Japanese. I'm pretty sure it depends on how inviting you look for conversations. I mostly had a dumb smile on throughout my trip, so I guess they liked that.
I would say riding a local commuter train (ie. on the JR Yamanote-line in Tokyo) versus long-distance (ie. the bullet train/shinkansen) might be a sufficient different environment that talking is more accepted.
As long as one isn't overly loud, of course.
If you're outside of one of the "quiet zones" (like the local commuter trains or the subway); I find that people are really warm and friendly and doesn't mind talking for a while or helping you out a bit. I guess it helped a lot that I spoke some bare minimal Japanese (to the point where some started talking English to me, as the conversations approached more medium/advanced territory).
Testing can be more difficult in some cases, if you haven't carefully structured your code. In python you can always monkey patch whatever outside dependencies you have, whereas in Go, you can't do that without structuring your code to allow it. Careful use of interfaces and dependency injection can let you do it, but if you don't know to use that style, you can get big blocks of code that become hard to test because they expect the whole operating environment to exist, which may be hard to do during testing.
If you want to write code in a Domain Specific Language (even if that domain is "math"), it's nearly impossible in Go. You can't do operator overloading or all the really crazy hacking on the functionality of basic parts of the language to make it work in fundamentally different ways (the way you can with numpy etc). Go will always look like types, functions, and methods.
Right now, Go has no user-defined generics.. this is actually not a problem for many projects, but if you happen to need a lot of specialized containers for different types (like red black trees, graphs, etc), then it can be a barrier. There are ways around it, probably the best way is just code generation to duplicate the container code per type that you need. The other option is just using interface{}, which is basically void* or "Object" for Go, and casting in and out of it... but that can be slow.
There's probably some stuff I'm missing, but those are the major points that I can think of.
My guess is that if you've written code that's hard to test in Go, it's going to be hard to write good, non-brittle tests in Python. It's not so much that you need to write code amenable to dependency-injection to write good tests, you just need to write modular code.
As a fan of DSLs, I actually do appreciate how easy it is to understand any Go that anyone has written, since there aren't any cutesy DSL tricks anywhere. So, yeah, it's hard/impossible to do DSLs, but that might not be a Bad Thing.
Generics is a (frequently discussed) downside. It's definitely a tradeoff. For every container type we had, we had to make a copy of it or a typesafe wrapper around it for every possible instantiation of the container with different types. If you're used to coding by making flexible containers and so on, that's definitely much more brittle and challenging in Go. Go peeps will tell you that's part of a tradeoff they're willing to take.
I've used a Japanese toilet and for me the hand washing facility attached to it is meaningless as I do not understand why would anyone ever wash their hands with cold water. Especially I do not understand people who simply wash their hands by dipping them into cold water for a second.
But maybe the culture of washing hands with warm water and soap is merely in North Europe. And maybe I am illusioned by the effectiveness of warm water.
There was a little study about this last year I believe [1]. Most of what comes out of your A is happy living at 37°C, so I'm sure it doesn't mind an extra 3°C or so.
I pretty much always wash my hands with cold water, unless they are especially grimey. The only advantage is that hot water seems to work better with soap, which may help dislodge dirt easier.
> why would anyone ever wash their hands with cold water.
Well it depends on the time of the year. In winter, you certainly don't use them that much because water is freezing cold. But as soon as it turns april-may, water becomes lukewarm or even relatively hot in summer months (summers are excruciatingly hot in Japan), so then it's not an issue anymore.
> And maybe I am illusioned by the effectiveness of warm water.
Do you mean warm water is more effective at washing ? There's actually no basis for that. Surfactants matter more than temperature.
Sincere question from an open-minded student: My mindset is such that I try do everything for long-term happiness, but if I stop worrying about the future and live only one day at a time, where will I ever end up?
I, too, am a student. We all learn from each other.
We can't say where we will end up in life. No one knows this for certain. Being responsible and planning for the future are good things. Taking good care of yourself financially, mentally, physically and emotionally are all important now and for the future.
Life happens while we make plans. Many times, life interferes with our plans. That's OK. That doesn't mean we should stop planning. Understanding that we cannot predict or control the future will transform our suffering.
We can live now and plan for our future and have peace inside as well.
If you pick up almost any book on eastern philosophy you'll find that living in the present is the key. Give up the future. It won't be how you imagine anyway.
It is highly related to the Questionable Cause fallacy: namely many believe that if two events are highly correlated then there is a causal link between them.
The business has traits X, Y, Z and successful, so we conclude that the traits X, Y, Z causes it to be successful.
I learned to use these practices via Babji Kriya Yoga first initiation. (it seems somewhat religious, but actually is not related to any)