Read how I orchestrate my daily review that consists of multiple applications using iOS Shortcuts. I create a notification-based workflow as a workaround to Shortcut's time limit when switching between applications.
In this post I revisit the topic of content consumption, adding new criteria to my selection process. I also discuss using a new tool (spoiler...it's Notion) to hold the content.
Read about how I moved away from RSS Feeds to emails to consume content. I take advantage of newsletters and IFTTT to ensure that everything moved over to email.
If you are going to edit commits in a collapsing fashion (i.e., amend/squash) in a pull request, make it your last action before merging to avoid confusing code reviewers.
In the software development world, there are always new articles and content to consume. Learn how I keep on top of it all and focus on keeping the flood of information to a sustainable level.
Working in an office comes with built-in stress relievers, namely social lunchtime with peers and the commute. When working remotely, it is important to ensure your day includes opportunities to decompress from the stresses of work. Learn about my process for decompressing at home.
Version control is something that all developers have to work through. It is such an essential part of working in the software field, especially in teams. There are many tools, utilities, commands and scenarios to learn. One facet that sometimes is overlooked is the commit message itself.
Over time, an individual or organization will create a number of software projects. The purpose of these repositories is to facilitate libraries, micro-services, documentation, mono-repositories, etc. Every so often, the time comes when a repository is no longer used. This article will outline how to archive these repositories, and the benefits to be realized.
When operating software in a production environment it is expected to have some unplanned disruptions over time. While the primary task is to resolve the disruption so that the impact is minimized, it is still very much important to track the disruption itself. Disruption reports provide transparency to others, accountability in the actionable tasks, a place for discussion, categorical data, and also a summary of the event.