From 5f6b4e6d6edfd2cd49af65b040976eb4a2ad96f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=2E=20Fernando=20S=C3=A1nchez?= Date: Thu, 6 Mar 2025 02:12:12 +0100 Subject: [PATCH] allow comments in rdf post --- content/post/bridging-rdf-json-ld-and-dataclasses.md | 2 +- content/post/efficient-collaboration.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/post/bridging-rdf-json-ld-and-dataclasses.md b/content/post/bridging-rdf-json-ld-and-dataclasses.md index 3968ef7..9891cb6 100644 --- a/content/post/bridging-rdf-json-ld-and-dataclasses.md +++ b/content/post/bridging-rdf-json-ld-and-dataclasses.md @@ -6,7 +6,7 @@ image: math: license: hidden: false -comments: false +comments: true draft: false categories: - programming diff --git a/content/post/efficient-collaboration.md b/content/post/efficient-collaboration.md index 4769a5f..05519a5 100644 --- a/content/post/efficient-collaboration.md +++ b/content/post/efficient-collaboration.md @@ -156,7 +156,7 @@ But it can also be done over a longer period of time. That can be perfectly acceptable, provided that the change in direction is justified and compatible with the principles of the organization. -Failure in direction is somewhat related to communication, but it subtly different. +Failure in direction is somewhat related to communication, but it is subtly different. An organization can excel at communication, but change their direction constantly. Arguably, a thorough communication strategy makes radical changes in direction less likely. On the one hand, a change in direction needs to be documented, which can be a pain.