1
I understand how mechanical prompts that shape the process or output, such as "list out the steps to do x, y, z" can lead to a better output.
I'm skeptical of techniques such as "roleplay as a world expert in X field", or "If you do this well, I will reward you with $200". Are there any articles or reviews of these approaches?
Currently on a Macbook Pro.
Example: Mega objects that should be broken down; mega functions that should be broken down; objects in the wrong areas (business logic in presenters)
I'm dealing with this on a case-by-case basis through forensic pull request reviews, and loading common themes into a ways of working document.
My concern is that the devs just don't seem think like architects - thinking about the jobs to be done and the classes and methods needed to do the job, and where they should live.
Is this a common issue and are there solutions? In particular, solutions for non-CS background developers.
Each window has all the tabs relating to a specific task.
When you finish a task, you can close the whole window at once.
When you want to pause a task, you can minimise the window.
Your minimised windows show you of your tasks in progress without you having to infer it be checking all of your tabs.
Building the habit is hard, so what I did was install a browser extension that limits the number of tabs you have running, and set the limit to three. This will force you to start using new windows for different tasks. It can be annoying in the long term, but it's enough to break the "new-tab-by-default" habit.