Cache invalidation is one of the most complex computer science tasks. Especially so for GitHub action workflows since there is no embedded mechanism to clean or invalidate present caches. However, what we can do is to update cache keys with a dedicated environment variable of the workflow or repository secret.

Let's learn how to extend existent Pull Request Update GitHub Actions workflow with steps specific for Dependabot pull requests (i.e. labels). We will add two jobs to the existent pull_request workflow and experiment with separate before and after workflow_run event workflows. Fortunately, after the recent GitHub actions update we don't need to use a separate pull_request_target event workflow as a workaround.

GitHub Actions is an awesome and very powerful tool. Let's explore workflow running time optimizations with caching node_modules and production build artifacts. We will be using Dependency Cache GH Actions feature driven by actions/cache. Hint: as always, cache invalidation is a key.

Just finished this very insightful and down-to-earth book on team management basics. Comes with loads of actionable advice, check-lists and quizzes. It covers everything from first month on the job and managing yourself to efficient meetings and growing leadership within your organization. Author, Julie Zhuo joined Facebook early on as a designer intern and since then has grown to the position…

Reviewing code is complex and demanding. When implemented correctly it can truly lift the project and the team up to the next level. On the flip side, when done wrong, it causes more harm than good. Let's dive deep into what makes for a good code review and how to approach it in a scalable, respectful and mutually beneficial manner.

Reminiscing on coding approaches and application architecture patterns introduced and popularized by AngularJs 1.x framework in the front-end community. Framework itself is gone and dusted, but its legacy is very much alive.

A bit of whining for history's sake. Here is the post on 1.6.0 AngularJs release version from the official blog post dated December 2016: Angular 1.6 will get regular non-breaking change releases over the next six months, and we will be aiming for the release of Angular 1.7 containing any necessary breaking changes by Summer 2017 . Ultimately version 1.7.0   was released in May 2018 with…