---
title: "Daniel Westgaard (@danielw) | Hashnode"
description: "Developer with a passion for building and development -  currently building Riftmap, https://riftmap.dev"
url: "https://hashnode.com/@danielw"
---

@danielw

# Daniel Westgaard

@danielw · Oslo, Norway · Joined April 2026

Developer with a passion for building and development - currently building Riftmap, https://riftmap.dev

[Website](https://riftmap.dev/)

### [Your senior engineer just left. Your bus factor was measuring the wrong thing.](https://riftmap.hashnode.dev/your-senior-engineer-just-left-your-bus-factor-was-measuring-the-wrong-thing?utm_source=hashnode&utm_medium=feed)

A senior leaves and the code stays readable. What walks out is the cross-repo dependency map — and your bus factor, measured from commits, never counted it.

14 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/your-senior-engineer-just-left-your-bus-factor-was-measuring-the-wrong-thing?utm_source=hashnode&utm_medium=feed)

[Jun 17](https://hashnode.com/posts/your-senior-engineer-just-left-your-bus-factor-was-measuring-the-wrong-thing/6a32dc654ce529fdf272474b)

### [A CVE just hit your base image. Your scanner won't tell you which repos to fix.](https://riftmap.hashnode.dev/a-cve-just-hit-your-base-image-your-scanner-won-t-tell-you-which-repos-to-fix?utm_source=hashnode&utm_medium=feed)

A scanner finds the vulnerable base image — not the repos you patch. Why base-image CVE remediation is a cross-repo source problem, and how to get the list.

11 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/a-cve-just-hit-your-base-image-your-scanner-won-t-tell-you-which-repos-to-fix?utm_source=hashnode&utm_medium=feed)

[Jun 15](https://hashnode.com/posts/a-cve-just-hit-your-base-image-your-scanner-won-t-tell-you-which-repos-to-fix/6a2ffde9365b098b44e4577a)

### [Your senior engineer just gave notice. Most of what they knew was in the repos all along.](https://riftmap.hashnode.dev/your-senior-engineer-just-gave-notice-most-of-what-they-knew-was-in-the-repos-all-along?utm_source=hashnode&utm_medium=feed)

Your senior just resigned and understood how everything connects. Half of that knowledge was never tribal — it was declared in your manifests the whole time.

12 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/your-senior-engineer-just-gave-notice-most-of-what-they-knew-was-in-the-repos-all-along?utm_source=hashnode&utm_medium=feed)

[Jun 14](https://hashnode.com/posts/your-senior-engineer-just-gave-notice-most-of-what-they-knew-was-in-the-repos-all-along/6a2e6ee2d045610718358c11)

### [GitLab Orbit maps your whole SDLC. It still can't tell you what an infrastructure change will break.](https://riftmap.hashnode.dev/gitlab-orbit-maps-your-whole-sdlc-it-still-can-t-tell-you-what-an-infrastructure-change-will-break?utm_source=hashnode&utm_medium=feed)

GitLab Orbit is a powerful symbol-and-SDLC graph — but it doesn't parse Terraform, Docker, or Helm. Here's the cross-repo blast-radius layer it can't reach.

11 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/gitlab-orbit-maps-your-whole-sdlc-it-still-can-t-tell-you-what-an-infrastructure-change-will-break?utm_source=hashnode&utm_medium=feed)

[Jun 12](https://hashnode.com/posts/gitlab-orbit-maps-your-whole-sdlc-it-still-can-t-tell-you-what-an-infrastructure-change-will-break/6a2bdb92c9664f607b4e28ff)

### [Is Backstage worth it? The real question is whether anyone will use it](https://riftmap.hashnode.dev/is-backstage-worth-it-the-real-question-is-whether-anyone-will-use-it?utm_source=hashnode&utm_medium=feed)

The Backstage worth-it debate fixates on cost. Spotify's own head of Backstage says adoption is where it dies — here's how to predict your outcome first

10 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/is-backstage-worth-it-the-real-question-is-whether-anyone-will-use-it?utm_source=hashnode&utm_medium=feed)

[Jun 10](https://hashnode.com/posts/is-backstage-worth-it-the-real-question-is-whether-anyone-will-use-it/6a29bc438893f4f76dc47bb0)