We haven't started using it yet but we've been thinking about using the Architecture Decision Record pattern as presented in the ThoughtWorks Technology Radar [1].
The basic idea is document decisions with a specific structure and keep it close to the code. The thing is any time we can answer "why", it's a form of decision that can be documented somehow. Since it's close to the code, while coding, any search will also land on those decision if the same terms are used.
There are several tools to help with that as presented here [2] and here [3].
Actually it's a debate my wife and I had for a while but our situation became more strange than that. We now have the bed in the living room and we just turn off every power bars when we go to sleep to not have any lights disturb our sleep.
Some of the reason behind is separation of concerns strangely enough. I work from home, we live in a 1 bedroom apartment, and I felt really stressed whenever I would play video game or watch TV while still in the very same space I worked all day. I was basically doing everything in the same 10sqft all day every day. Now, because it's in another room, I feel way more relaxed.
Another plus is now I get the sun up right in front of me from bed every morning and that's just an awesome feeling I didn't get from the bedroom. I believe the bedroom should be oriented south east to get that morning sunshine to wake you up, and we didn't get that before.
Exactly this! We got rid of out dinning table because we were always eating in front of the TV or the PC. We got rid of the couch because we were always watching TV from bed. We didn't see the point in keeping these only to very rarely have people come over. We can meet outside or they can deal with the no table no couch setup, I won't live in a more crowded space for them.
Regarding the "bragging" posts, according to this Hidden Brain podcast [1], it has a more negative effect than anything and is usually not the truth about people current situation in life. For instance, we might see the great vacation pictures, but turns out they were fighting the whole time and it wasn't fun at all, but it is not like they are gonna share that part on FB.
Interestingly, there seems to be an equality bias[1] where the experts opinions weight no more than any other person's opinion. So apparently the reasonable heuristic isn't always applied in how we perceive and judge information.
Maybe, but I see "aware" as noticing things external to myself as opposed to "conscious" or "present" where it has a more spiritual, intra-personal meaning.
Or maybe I'm not understanding the terms the right way as I'm not a native English speaker and may put concepts and meanings from my native language into these terms.
Given what I started and how I've been thinking, maybe "aware". Being aware of what's happening around me, of the thoughts I have, of the progress I make, doing the mental process of noting things rather than being passive about what's going on. Does that make sens?
I decided to note on a daily basis what I learned over the day. To commit to it, rather than being a note in a note book, I made it as a blog[1] on which I post daily. It is badly written and really incomplete but as it is mostly for myself, I have no issue with it.
The ultimate goal is to see what I learned over a year so I can better appreciate the progress I made, rather than only base my retrospective on feelings. It might also be useful to find what I learned but can't put the name on it, or find links to interesting things I found several months ago.
To help staying focused, I decided to fix goals and rewards. The first reward is on January 1st if I haven't skipped a single day from when I started.
I worked in QA on some AAA titles and I remember being told that the hours the team was putting in testing the game (nearly 300 people over several months of over time) would be matched by the players in the first 6 to 8 hours from the release. That and when the team is filling hundreds if not thousands of defects daily, how can the dev team keep up and "fix" everything?
The basic idea is document decisions with a specific structure and keep it close to the code. The thing is any time we can answer "why", it's a form of decision that can be documented somehow. Since it's close to the code, while coding, any search will also land on those decision if the same terms are used.
There are several tools to help with that as presented here [2] and here [3].
[1] https://www.thoughtworks.com/radar/techniques/lightweight-ar... [2] https://adr.github.io/ [3] https://github.com/joelparkerhenderson/architecture_decision...