vault backup: 2026-03-24 10:13:10

This commit is contained in:
2026-03-24 10:13:10 -04:00
parent 44ff68ea52
commit 250265de28
2 changed files with 71 additions and 32 deletions
+38
View File
@@ -0,0 +1,38 @@
---
id: 2026-03-24T09:51:24-04:00
aliases: []
title: 2026-03-24 09:51:24
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/timestamped
dg-publish: true
date-created: 2026-03-24T09:51:24-04:00
daily: "[[2026-03-24]]"
weekly: "[[2026-W13]]"
monthly: "[[2026-03]]"
quarterly: "[[2026-Q1]]"
yearly: "[[2026]]"
---
# 2026-03-24 09:51:24
A peer referred to column lines as matchlines,
which I felt was incorrect
based on how I've seen it heard it used,
but I was curious of the etymology.
CAD topics dominate search results for the term,
but I found this one for clothes-making
which appears to be older (1800's)
and may be the origin of its use in drafting.
> **match-line**
>
> a line drawn on a pattern
> denoting where the textile pattern must be aligned
> to ensure it is visually continuous across seam lines.
I have to note that modern use of this meaning is exceedingly rare.
So rare that I'm suspicious that LLM hallucination is afoot,
but I can't research further now.
+33 -32
View File
@@ -16,36 +16,37 @@ tags:
> where the question is about an end user's attempted solution (X)
> rather than the root problem itself (Y).
> [!quote] [How To Ask Questions The Smart Way_ "Questions Not To Ask"](http://www.catb.org/~esr/faqs/smart-questions.html#classic)
> **Q:** How can I use X to do Y?
> [!quote] [_How To Ask Questions The Smart Way_ --- Eric Steven Raymond](http://www.catb.org/~esr/faqs/smart-questions.html)
> > [!quote] ["Questions Not To Ask"](http://www.catb.org/~esr/faqs/smart-questions.html#classic)
> > **Q:** How can I use X to do Y?
> >
> > **A:** If what you want is to do Y,
> > you should ask that question without pre-supposing the use of a method
> > that may not be appropriate.
> > Questions of this form often indicate a person who is not merely ignorant about X,
> > but confused about what problem Y they are solving
> > and too fixated on the details of their particular situation.
>
> **A:** If what you want is to do Y,
> you should ask that question without pre-supposing the use of a method
> that may not be appropriate.
> Questions of this form often indicate a person who is not merely ignorant about X,
> but confused about what problem Y they are solving
> and too fixated on the details of their particular situation.
> [!quote] [_How To Ask Questions The Smart Way_ "Describe the goal, not the step"](http://www.catb.org/~esr/faqs/smart-questions.html#goal)
> If you are trying to find out how to do something
> (as opposed to reporting a bug),
> begin by describing the goal.
> Only then describe the particular step towards it
> that you are blocked on.
>
> Often, people who need technical help
> have a high-level goal in mind
> and get stuck on what they think is one particular path towards the goal.
> They come for help with the step,
> but don't realize that the path is wrong.
> It can take substantial effort to get past this.
>
> **Stupid:** How do I get the color-picker on the FooDraw program
> to take a hexadecimal RGB value?
>
> **Smart:** I'm trying to replace the color table on an image with values of my choosing.
> Right now the only way I can see to do this is by editing each table slot,
> but I can't get FooDraw's color picker to take a hexadecimal RGB value.
>
> The second version of the question is smart.
> It allows an answer that suggests a tool better suited to the task.
> > [!quote] ["Describe the goal, not the step"](http://www.catb.org/~esr/faqs/smart-questions.html#goal)
> > If you are trying to find out how to do something
> > (as opposed to reporting a bug),
> > begin by describing the goal.
> > Only then describe the particular step towards it
> > that you are blocked on.
> >
> > Often, people who need technical help
> > have a high-level goal in mind
> > and get stuck on what they think is one particular path towards the goal.
> > They come for help with the step,
> > but don't realize that the path is wrong.
> > It can take substantial effort to get past this.
> >
> > **Stupid:** How do I get the color-picker on the FooDraw program
> > to take a hexadecimal RGB value?
> >
> > **Smart:** I'm trying to replace the color table on an image with values of my choosing.
> > Right now the only way I can see to do this is by editing each table slot,
> > but I can't get FooDraw's color picker to take a hexadecimal RGB value.
> >
> > The second version of the question is smart.
> > It allows an answer that suggests a tool better suited to the task.