Skip to Content

Eric Gregorich

Posts on page 6

Losing the ability to read and think deeply

Explore the modern struggle to read and think deeply amidst constant digital consumption. This post delves into how short-form content impacts focus and offers strategies to rebuild the ability to engage with evergreen material.

I’m losing my ability to read deeply and understand what I’m reading, and I’m not the only one.

I used to read for hours, fully immersed. I’d put the book down and still think about it, processing and connecting it for a deeper understanding and recall.

Today, we’re consumed by digital email, chats, TikTok, social media, short blogs, video clips, and other quick consumption forms. The content is designed to keep us engaged.

There must be a connection between today’s consumption and the ability to read and think critically.

Today, I struggle to read

Losing the ability to read and think deeply Read more

Document your work!

Documentation is vital for software developers. It boosts understanding, ensures thoroughness, improves collaboration, and saves future time and effort.

Please document your work! I’m speaking from the context of a software developer/architect, but this also applies elsewhere.

Currently, it may feel like a waste of time. You may think, “I’ll remember this.” or “I’ll never do this again.” I’ve been there (and still think this). However, documenting has so many advantages. I’m pushing myself to do better at it constantly. More documentation with less effort.

Creating documentation is a great way to go through whatever it is in greater detail and ensure you don’t miss anything. I can’t count how many

Document your work! Read more

Thoughts about code comments

Argues for comments that explain code's purpose to other developers, serving as a guide and documentation extension rather than code repetition. It also stresses deleting commented-out code and relying on source control.

For many years, I thought my code should be clean and easy to read, and therefore I don’t need to use comments. The code itself should be “self-documenting”.

Over time, my view on comments has changed. I’ve learned to appreciate comments in my solutions, especially when I’m not the only developer.

I’m currently reading A Philosophy of Software Design, which has a section of the book dedicated to comments in your code. The author’s viewpoints aligned with my own.

I find it easier to write the comments for a new piece of code before

Thoughts about code comments Read more

Adding color to your tools can help you be more productive

We can use Colors in our Productivity System to help us quickly identify things. I find it especially useful to identify each area of my life with a specific color.

Here are some of the colors I use to identify areas of my life.

  • Purple = Family
  • Red = Health
  • Brown = Home
  • Orange = Creative work
  • Green = Client work
  • Blue = Personal
  • Use colors in a variety of tools.
  • If you are an analog type, you can use different colored pens and highlighters.

Many digital applications allow the use of colors in some form.

  • Calendar applications allow you to set the default color of
Adding color to your tools can help you be more productive Read more

Writing for Busy Readers

Writing for Busy Readers by Todd Rogers and Jessica Lasky-Fink is a book about how to write effectively. A short and well-written book (it should be) that is full of examples.

I was browsing in the bookstore when I found this book, and it somehow caught my attention. I write a lot of documentation and email during my day job, as well as posting to this blog, and the ability to write short and compelling content is essential.

As readers, we consume a ton of content, and if it’s not short and to the point, it simply won’

Writing for Busy Readers Read more

Using a working memory file to stay productive during the day

I created a Working Memory file that I’ll use throughout the day. I learned this from Cal Newport, although I’m sure he didn’t invent the idea.

The idea is to have a single text file open all day that you use to write all of your notes, today’s tasks, etc. Similar to a Daily Note available in some applications, like Roam Research, Logseq, or Obsidian, this file persists daily.

I clean up the file daily, move tasks to my task system, and save essential notes into my note application. My Working Memory file also has

Using a working memory file to stay productive during the day Read more