TK, or the secret to effortless writing (2024) • Hacker News Board

Re: TK, or the secret to effortless writing (2024)

#11

Post by karmakaze » Sun, Jul 12, 2026, 5:19 PM UTC

ultraboom wrote: post #5

x______________ wrote: post #2

tl;dr add tk when you hit a wall (abbreviated from 'to come', yet spelled with k as tc appears in many words)

I slice my latke with a pocketknife.

I found the low frequency surprising as it's so easy to pronounce--I suppose tc is used in most cases. Here's what I found for bigram freqs near TK:

Ratios (count / total) and percentages:

    PG: 0.00047%
    TK: 0.00046%
    KK: 0.00045%
    HQ: 0.00042%
    FN: 0.00042%

Every other one here I'd expect to see: Postgres, kk/okay (and my initials), headquarters, function. Of course there's Tcl/Tk but not used nearly as much as it could.

Re: TK, or the secret to effortless writing (2024)

#12

Post by karmakaze » Sun, Jul 12, 2026, 5:21 PM UTC

LLMs should use "TK" or stable diffusion (and the like) so as not to get hung up on sequential words/thoughts and fill them in later instead of hallucinating filler.

Re: TK, or the secret to effortless writing (2024)

#13

Post by wonger_ » Sun, Jul 12, 2026, 5:46 PM UTC

ultraboom wrote: post #5

x______________ wrote: post #2

tl;dr add tk when you hit a wall (abbreviated from 'to come', yet spelled with k as tc appears in many words)

I slice my latke with a pocketknife.

True, but have you ever sliced your LATKE with a POCKETKNIFE?

Re: TK, or the secret to effortless writing (2024)

#14

Post by Haranrk » Sun, Jul 12, 2026, 5:55 PM UTC

karmakaze wrote: post #12

LLMs should use "TK" or stable diffusion (and the like) so as not to get hung up on sequential words/thoughts and fill them in later instead of hallucinating filler.

I think this is a great idea.

Re: TK, or the secret to effortless writing (2024)

#15

Post by rsingel » Sun, Jul 12, 2026, 6:07 PM UTC

Indeed a great trick. I often double it to TKTK just to make it stand out even more.

Fun fact: the Ghost.org editor looks for TK

https://ghost.org/changelog/tk-reminders/

Re: TK, or the secret to effortless writing (2024)

#16

Post by pratikdeoghare » Sun, Jul 12, 2026, 6:12 PM UTC

If you use Brashtag notation you could insert #tk{} bag.

https://github.com/pratikdeoghare/brashtag

Re: TK, or the secret to effortless writing (2024)

#17

Post by techno_tsar » Sun, Jul 12, 2026, 6:34 PM UTC

wonger_ wrote: post #13

ultraboom wrote: post #5

Earlier quoted context omitted.

I slice my latke with a pocketknife.

True, but have you ever sliced your LATKE with a POCKETKNIFE?

...I did, a few years ago, when I went camping with some friends.

Re: TK, or the secret to effortless writing (2024)

#18

Post by chickensong » Sun, Jul 12, 2026, 7:05 PM UTC

sublinear wrote: post #10

Could you instead use any two numerical digits? Then you've got a tagging system with up to 100 tags. This assumes you're writing according to guidelines that insist you spell out all numbers. i.e. 58 is always intentionally "fifty-eight", so "58" must be your own meta text.

I think you can use whatever you want. The point is just to drop a quick marker that you can find later, and not interrupt your flow.

Re: TK, or the secret to effortless writing (2024)

#19

Post by chickensong » Sun, Jul 12, 2026, 7:07 PM UTC

Shout out to Title TK by the Breeders.

Re: TK, or the secret to effortless writing (2024)

#20

Post by sublinear » Sun, Jul 12, 2026, 7:54 PM UTC

chickensong wrote: post #18

sublinear wrote: post #10

Could you instead use any two numerical digits? Then you've got a tagging system with up to 100 tags. This assumes you're writing according to guidelines that insist you spell out all numbers. i.e. 58 is always intentionally "fifty-eight", so "58" must be your own meta text.

I think you can use whatever you want. The point is just to drop a quick marker that you can find later, and not interrupt your flow.

Ah, never mind. A slight refinement needed here.

AP style only spells out one through nine. 10 and above are written as numerals. So, you'd get 10 tags, not 100.

I think the regex would be: /(?<!\d)\d{1}(?!\d)/