Skip to main content

The Genius of Insomnia

This article deals with a very narrow kind of insomnia, but insomnia has different causes, only one of which is likely related to creativity:

  • A mixture of habit and need for sleep
  • Excessive work and demands
  • Life stresses
  • Mental health issues
  • Inclination, i.e., night owls

Like many of us, I've had a variety of sleep styles over the years. In high school, I went to bed late, was chronically late to school, and would sleep into the afternoon on weekends. In my late twenties, driven to complete college while working a job that required hours from 4 AM, I often only slept 3 hours a night, but having to wake up that early eventually stuck my body clock to an early riser. B-school made the same kinds of demand, although now I was an early riser who often stayed up until 3 AM to finish projects. By then, I learned to just go with my needs, to go to bed when I felt like it, and to not force myself to do something I was incapable of, and rather than struggle to simply work until the desire for sleep overtook me. Eventually, married, with a spouse, I had years of solid, uninterrupted sleep, asleep almost as fast as hitting the pillow, sleeping my 'black death' of memoryless deep sleep. At some point, under great pressure at an employer, I develop sleep problems, shortened and shallow sleep. It was only when I left and found a better employer have my sleep patterns gone back to a moderately healthy form, still almost immediately asleep, but usually a decent 6.5 hours, although not my ideal 7.

https://www.nytimes.com/2019/01/05/opinion/sunday/insomnia-sleep.html?comments#permid=30020237

Comments

Popular posts from this blog

Behave: The Biology of Humans at Our Best and Worst by Robert M. Sapolsky My rating: 5 of 5 stars I finished reading this crying. It is a work of neurobiology, social science, anthropology, and history, but ultimately it is a work of great humanity, suggesting ways that humans, our groups, our systems, and our societies can be made better. View all my reviews

A Journey — if You Dare — Into the Minds of Silicon Valley Programmers

My responses in a NY Times comment section for the book, Coders: The Making of a New Tribe and the Remaking of the World by Clive Thompson : #1 - Link Although I've been a software developer for 15 years, and for longer alternating between a project manager, team lead, or analyst, mostly in finance, and now with a cancer center, I found it funny that you blame the people doing the coding for not seeing the harm it could cause. First, most scientific advancement has dark elements, and it is usually not the science but how it is used and sold by business people that is the problem. This leads to the second problem, in that it is not coding that is in itself problematic, but specifically how technology is harnessed to sell. It is normal and desirable to track users, to log actions, to collect telemetry, so as to monitor systems, respond to errors, and to develop new features, but that normal engineering practice has been used to surveil users for the purpose of selling. Blaming

Don't learn to code. Learn to think.

A response to  Don't learn to code. Learn to think. : Below is is my usual response when I see an article stating that everyone should learn to code:  Rather than programming, it is more important to impart the thinking of computer science (CS) than a specific implementation. Programming can be an end point for some students, but it is likely that programming itself will be increasingly automated, so that one needs more the general concepts common in CS. Even then, programming itself is to some degree a grunt task that one progresses beyond:  The following are typical components of a CS degree: algorithms & flowcharting systems thinking logical systems and set theory object-orientation & patterns probability, statistics, mathematics All of the above can be useful in an increasingly automated and data-driven world.