TLDR: Bullet Journal rocks! Third is not a solely technical post. Over almost 25 years of working in software development I've seen multiple practices, frameworks and processes for individuals and teams. Some implementations worked and others became so bureaucratic that they made for a very unhappy group of people. From free for all to things so complicated as rational unified processes (RUP) and Capability maturity model integrated (CMMi) passing through Personal Software Process (PSP) and Team Software Process (TSP). Some of those have their merits and can be used successfully in certain contexts but when it comes to really individual things they didn't quite help me a lot. They either required use of extra tools or even create new ones to be able to do what was required of the process in addition to do the value work which in turn adds to the inertia and extra effort. The one practice that did really help me is Bullet Journaling (Ryder Carrol) precisely by being non techn...
On the last months I had a couple of the most aggressive interviews on my current job hunt. It started with one of the interviewers stating that I was being recorded and that all answers should be provided from the top of my head, that if I looked elsewhere it would be considered as cheating and against my candidacy. Wait what? Are you serious? This is a senior or staff level position. If you do not trust me to even do an interview why start this process at all? Then while talking about technology we were discussing concepts and this same individual starts to talk about specifics and "educates" the candidate and tells me to validate this afterwards. Come on, of course I will not contradict you, but if this is the kind of culture you are allowing count me out. Then on to systems design on whiteboard. Here I'm asking lots of questions regarding the domain and all they answer is to make an assumption. Then they start asking how to develop the solution bu...