The Day by day Developer.

  For programming there is an idea that the device optimally needs to be like a gaming laptop or have alot of processing power , when compiling really doesn't take as much from the developer's time as coding does . For programming specially for applications that aren't games the requirements of the processor doesn't have to be so much , in fact a low end processor like an i3 10th gen can be more than enough and I would even recommend because overheating is our real enemy since if the processor overheats , no matter how fast it is , the performance will go down quickly ; when we developers tend to stay for a long time , and most of that time isn't in graphically intensive tasks.  Quick access memory is equally important.  So here are the main problems I think we face  : - 1 - Over heating over a long period of time  2 - Slow access to memory ( internal and external)  3 - Eye pain 4 - High memory on the main disk

Veiled Virgin" by Giovanni Strazza (1876) Fig 1  endless-column by Constantin-brancusi Fig 2 Today you can see examples of abstract or intentional art  , music sometimes carries a meaning and needs to get in line with a rhythm , same thing for coding , some programmers like to mess around with new ideas like myself , others try to just keep it within the rules even if their solution isn’t the best .  Both approaches have their pros and cons and need to be implemented if we want a holistic approach. I recommend you follow Collen Galen (a high rank top performer in coding competitions) , in this video he describes very well the relationship between intuition and logic and how he needs to put his intuitive ideas to the test by logic which takes time but is absolutely worth it . When I started coding I relied on my intuition more than logical representation of things like the problems , goals and the tests I needed to implement . This made all my initial work spaghetti like and not