#Writing

Just dropped my latest piece. It's a 12,000-word novella built in Scrivener v3, exported to PDF with custom StoryGrid beats and Fountain markup for the script sections.

Key bits:

• 3 act structure annotated in the margins.
• 5 character arcs mapped using the Hero's Journey template.
• Embedded worldbuilding index (12,000+ entries) using Zotero tags.
• Cover art generated in Midjourney v5, printed on matte 200gsm.

I’m pushing it on r/Writing, Twitter, and a personal site. Expecting the usual "nice job" but also want the haters to point out the fluff. Does the blend of novel and script format actually work, or is it just a gimmick?

Drop your thoughts. Brutal feedback only.

Every time I sit down to start a story I end up drafting the first sentence over and over It's not that I hate the idea, it's just that the exact phrasing feels wrong until it doesn't. The irony is that the rest of the piece often flows fine once I finally accept the opening. Anyone else stuck in a loop with that one line?

I'm having trouble with writing dialogue that sounds natural. Maybe someone can help me out? I feel like my characters all sound the same 😊

Daily writing routines force creativity into a mold. The best work often comes from letting ideas gestate in the background. Insisting on constant output prioritizes volume over depth. I've seen drafts crumble under the weight of forced consistency. Let the process breathe.

I’ve been experimenting with a narrative that uses only marginalia and footnotes to tell the plot. The main text is almost empty, with the story unfolding in the margins. Does this technique keep the reader engaged, or does it feel like a gimmick? Any examples of authors who’ve done something similar? I’d appreciate feedback.

I finally nailed down a custom Arch Linux environment that doubles as a writer’s studio. The goal: create a portfolio page that looks great, runs fast, and demonstrates the technical chops behind a solid writing workflow.

Hardware: • Intel i7‑12700K with 16 GB DDR4 • NVIDIA RTX 3060 8 GB, driver 535.104.05 • Dell UltraSharp U2720Q + HP ENVY 27, 4K @ 60 Hz • Samsung 970 EVO Plus 1 TB NVMe for OS and scratch disk

Software stack: • Arch Linux 2024.02‑base (kernel 6.6‑generic) • Wayland via Sway (i3‑like tiling, floating windows for editing) • GNOME Shell 44 on XWayland for legacy apps (LibreOffice, Scrivener) • Zotero + Better BibTeX for references • Pandoc 3.1 for .md → PDF → HTML conversion • Neovim + CoC with coc‑language‑server for syntax‑highlighted writing

Set‑up steps (high‑level):

1. Install base Arch, add mesa, nvidia, nvidia-utils, wayland, sway, and gnome‑shell.
2. Configure /etc/mdev.conf to load NVMe controller on boot.
3. Create ~/.config/sway/config with a floating rule for Scrivener and a workspace mapping that puts draft pages on monitor 1, reference files on monitor 2.
4. Use lightdm-gtk-greeter to switch between Wayland and X11 sessions as needed.
5. Set up a .profile that launches tmux new -s writer which spawns a Neovim buffer, a htop, and a lsof watch.
6. Export PATH to include ~/projects/writing_tools/bin where custom scripts live: md2html, git‑commit‑draft, pdf‑check.
7. Push everything to GitHub: a static site built with Hugo, hosted on Cloudflare Pages.

Result: Every time I hit <Ctrl‑s> in Neovim, my drafts sync to GitHub, the static site rebuilds, and the preview pops up in the secondary monitor. The portfolio page features a live‑updating PDF preview, an interactive Markdown editor, and a live‑search over my bibliography.

If you’re running a dual‑monitor setup with Arch + Wayland and want your writing to look like it deserves, this should give you a solid start. Drop your questions or tweaks below – I’m mostly happy to troubleshoot kernel 6.6‑generic or Sway tiling headaches.

TL;DR: Kernel 6.6 + Wayland + Sway + GNOME on XWayland + Neovim + Pandoc = a writer’s dream machine.

Okay, so I finally mustered the courage to try that "Rule of Three" bit I've been rehearsing for weeks. I had the premise, the beat, the tag—everything lined up in my head like a tight 4/4 set. Went on stage, hit the first line, got a chuckle, then tried to land the third punchline and... crickets.

Turns out I mixed up my timing. I was counting the beats in my head like I was doing a stand‑up version of a metronome, but the audience was on a completely different tempo. My third line came out half a beat early, so the callback felt forced, like a bad improv sketch that never got the cue.

To make matters worse, I used the term "callback" in the punchline itself, which is a rookie move—you're basically telling the audience "hey, remember that joke?" and they just stare. I think I also dropped the word "punchline" instead of "punch line" and that tiny slip made it sound like I was reading a textbook.

Moral of the story: don't over‑engineer the rhythm in your head, and definitely don't name‑drop comedy jargon mid‑joke unless you're on a panel about comedy theory. Anyone else flubbed a classic structure because they were too busy counting beats?

• TL;DR: I bombed a Rule‑of‑Three because I was counting beats like a drummer and said "punchline" mid‑joke. Help me fix this?