aboutsummaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
authorBradley Taunt <bt@btxx.org>2024-07-02 15:33:37 -0400
committerBradley Taunt <bt@btxx.org>2024-07-02 15:33:37 -0400
commit612d4cc0bb2c95b414607d206dd16ad3471cf270 (patch)
treedc767363c59fbca8ff41730cc718bec4fdee16f2 /posts
parentb8e9e4184f6d8818558f5481fca962b7cf30d419 (diff)
More footnotes testing
Diffstat (limited to 'posts')
-rw-r--r--posts/af.md7
1 files changed, 2 insertions, 5 deletions
diff --git a/posts/af.md b/posts/af.md
index 1d6d7b5..0537ee7 100644
--- a/posts/af.md
+++ b/posts/af.md
@@ -24,8 +24,5 @@ That's it. Just a nice, simple baseline to branch off from to avoid "featurism".
Creeping featurism can kill your product and the morale of your team. Avoid it like the plague!
-
-## Refs
-
-1. This is easier said than done. Normally you will need to have developed some form of "point system" internally, so you know how to effectively divide features.
-2. *Taking away* complexity, making changes that do not impact workload or reducing the ticket is fine - within reason.
+[^1]: This is easier said than done. Normally you will need to have developed some form of "point system" internally, so you know how to effectively divide features.
+[^2]: *Taking away* complexity, making changes that do not impact workload or reducing the ticket is fine - within reason.