diff --git a/blog/2024-06-13-summer-buildbar.mdx b/blog/2024-06-13-summer-buildbar.mdx
index 6b955c3..0358b54 100644
--- a/blog/2024-06-13-summer-buildbar.mdx
+++ b/blog/2024-06-13-summer-buildbar.mdx
@@ -13,7 +13,7 @@ technical problems, new developments with Bazel and Buildbarn.
 
 And also have a few beers.
 
-Feel welcome to come over on Wednesday 19 June 2024, from 16 to 20.
+Feel welcome to come over this Wednesday the nineteenth of June from 16 to 20.
 
 ## Directions
 
diff --git a/docs/tips/debug-bazel-go-projects.md b/docs/tips/debug-bazel-go-projects.md
index 69ae18d..175978b 100644
--- a/docs/tips/debug-bazel-go-projects.md
+++ b/docs/tips/debug-bazel-go-projects.md
@@ -164,6 +164,16 @@ end | psub ) $BUILDOZER -- -h
 
 ## Execroot trick
 
+:::info
+Alternative title: Execroot trap
+
+Hedron Vision notes a flaw with this technique for long-lived access to files,
+with go-to-definition in the IDE being a great such use-case,
+the Execroot is regenerated for new builds, and only contains the files needed for that build.
+See https://github.com/hedronvision/bazel-compile-commands-extractor/blob/main/ImplementationReadme.md#compilation-working-directory-and-the-external-link
+for how they access generated source files with a symlink of `external` itself.
+:::
+
 If the execution directory of the program does not matter
 you can execute it directly from the _execroot_,
 where all source files are available as they were during compilation in the sandbox.