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.
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...