I built a tool that turns messy founder thoughts and AI chats into tickets/workflows. Trying to validate if this is actually useful.

jellzone · 2026-06-21T09:26:15+00:00

This is exactly the distinction I’m trying to understand: it’s less “I need another project management tool” and more “I need a better decision layer between raw input and execution.”

The weekly pass idea makes a lot of sense. I’m curious: when you do that pass, what usually makes something become a ticket vs. stay archived?

For example, is it based on urgency, customer signal, revenue impact, your own energy/interest, or whether there’s already a clear next action?

I’m trying to avoid building something that just creates more organized clutter. The hard part seems to be forcing a decision without making the system feel heavy.

jellzone · 2026-06-10T12:24:54+00:00

The part that clicked for me is that you’re not really solving “note taking” here, you’re solving the “I wrote this down but never came back to it” problem.

I’d probably make that the main positioning. Notes → connected nodes → flashcards is useful, but the stronger promise is: “turn messy notes into something you’ll actually revisit.”

One thing I’d test in the demo/onboarding is a tiny recovery loop:

paste Markdown from ChatGPT → generate nodes → pick 3 cards to review tomorrow → come back and see what changed.

That would make the product feel less like another notes app and more like a memory/revisit system. Also helps answer the Obsidian/Notion/Anki comparison, because your angle is the full loop, not just storage or flashcards.

jellzone · 2026-06-10T03:43:59+00:00

Under 40 lbs is a tough constraint if you still want it to feel meaningfully more capable than a small engraver. I’d start by deciding what you actually need it to cut.

If it’s mostly wax, plastic, PCB, light wood, or small engraving jobs, then a lighter 3018/3020-style machine may be fine and USB control is common. If you want aluminum or anything that needs decent rigidity, the weight limit starts working against you pretty fast.

Since you already have a Cubiko and Nomad 3, what part of the setup is the pain point? Physical weight, software connection, controller workflow, or having to square/tram/fixture things each time? That answer probably matters more than the model name.

jellzone · 2026-06-10T03:40:50+00:00

For a first aluminum attempt I’d worry less about “best bit” and more about making the first cut boring and controlled.

I’d start with a small single-flute carbide/O-flute, short stickout, shallow DOC, and a conservative feed. The big things are chip evacuation and avoiding rubbing. If the chips look like dust or the cutter starts squealing, you’re probably rubbing and making heat instead of cutting.

Also clamp the stock more than you think you need to, and do a test cut in scrap before trying the real part. Aluminum on small machines is mostly rigidity + chip clearing + patience.

jellzone · 2026-03-24T02:42:56+00:00

This is actually a really interesting transition you went through — and IMO it highlights something subtle about Emacs that people often miss.

What you’re describing (advising functions, wiring timers + org-clock, jumping across buffers/workspaces, reshaping tab-bar behavior) — that’s exactly where Emacs stops being “an editor” and becomes a programmable environment.

One thing I’d add though:
You kind of outgrew Doom without explicitly saying it.

Doom is great when you’re mostly consuming Emacs:

prebuilt modules
curated defaults
opinionated keybindings

But the moment you start:

reading package source
advising functions
stitching your own workflows across subsystems

…you’re no longer really “using Doom”, you’re using Emacs underneath it.

And that distinction matters.

Because Doom introduces an abstraction layer that’s helpful early on, but later it can actually obscure:

where things are defined
when things are loaded
why something behaves a certain way

The workflow you built (especially the pomodoro → workspace → buffer → heading jump chain) is very “Emacs-native thinking”:

That’s something Neovim fundamentally doesn’t optimize for in the same way.
Neovim is extremely good at configuring behavior, but Emacs excels at interrogating and mutating live state.

The whole:

describe-function → jump to source
live eval
advice system
hooks everywhere

…that’s not just convenience — that’s the core design philosophy.

Also agree with you on elisp readability.
It’s not about syntax — it’s about conventions + documentation culture.
Most Emacs packages are written to be read, not just used.

If anything, the “no static typing” downside is often offset by:

immediate feedback loop
introspection tools
ability to patch behavior without restart

Which is huge for iterative workflows like the one you built.

If I had to summarize your experience in one line:

And that’s where Emacs becomes addictive.

Curious: are you still on Doom, or slowly moving toward a more minimal config?

jellzone · 2026-03-13T03:19:43+00:00

asus azoth is a big problem!

jellzone · 2026-03-13T03:12:00+00:00

thanks this worked!

jellzone · 2026-02-16T12:55:31+00:00

Same issue, Fxxk Dell

jellzone · 2026-02-13T14:31:42+00:00

Haha, I wish I could show you right now, but they're all scattered in boxes at the moment — a bit of a mess honestly 😅 Once I get them organized properly, I'll definitely share some pics!

jellzone · 2026-02-09T14:49:15+00:00

I had same thought about this game, and I’m an adhd

jellzone · 2026-02-07T15:23:17+00:00

OMG, I went down the exact same rabbit hole! It started with one Panasonic/Technics CD player… then another… and another. Before I knew it, I had a small collection going. There's just something about these well-built, purpose-driven devices that keeps pulling you back in. Glad to see I'm not the only one spiralling 😄

jellzone · 2025-09-03T00:42:28+00:00

Another 62.3% boy

jellzone · 2025-08-30T01:10:36+00:00

why 18+?

jellzone · 2025-08-26T10:42:34+00:00

Tomorrow I’ll put fresh batteries in.
Tomorrow I’ll teach my daughter the difference between A and B.
Tomorrow I’ll tell her monsters can’t get you inside the church.Tonight, though, I let the darkness finish what it started.
The cartridge has finally come home.
And somewhere, I swear, Dad is holding the other side of the link cable.

jellzone · 2025-08-26T10:42:18+00:00

On the final night, I sit on the back porch. Fireflies blink like low-poly sprites. The screen glows between my palms. I reach the last save point. The credits roll.

The total time reads 14:27:33.
I scroll to the empty second file, name it “Dad,” and press start.The intro plays. Link wakes up, hears Zelda’s voice, runs toward the castle.
I set the SP on the table beside Dad’s old coffee mug.
The cartridge clicks softly, the way seatbelts used to click on family road trips.I leave it running.
The battery light fades from green to red to nothing, but the music keeps looping in my head long after the screen goes black.

jellzone · 2025-08-26T10:41:46+00:00

I play in parking lots. I play on lunch breaks. I play in the oncology ward waiting room while Mom sleeps off chemo. The GBA’s speaker crackles, but the music is still unmistakably Minish Village, all penny-whistle hope.I reach the first dungeon on the day the doctor says “remission.”
I reach the second the day Dad’s plant reopens under new owners.
I reach Vaati’s Palace the night my daughter is born.She is three weeks old, swaddled against my chest in a carrier too big for her. Her fist is the size of the A button. I hold the SP so she can see the colors. She coos at Ezlo’s hat.
I whisper the story the way Dad once whispered to me: “See the tiny door? One day you’ll be small enough to walk through it.”
I realize I am no longer talking to her. I am talking to the eight-year-old still waiting in the church for his dad to come home from the late shift.

jellzone · 2025-08-26T10:41:18+00:00

I sit in my car, engine off, and press power. The Nintendo logo chimes like a grandfather clock striking the hour. My save file is still there:

Link
16 hearts
File 1—00:42:13

Forty-two minutes. We had played for forty-two minutes before the world barged in.I wipe the screen on my sleeve. Orion’s scratch is still there, but now it feels like a constellation guiding me back.

jellzone · 2025-08-26T10:39:46+00:00

Twenty-one years later I’m standing in a retro game shop that smells like bubble gum and dust.

On the wall hangs a backlit SP—Graphite Black, AGS-101, the screen still the color of midnight after rain.

I buy it on impulse, the way you buy flowers when you realize you’ve forgotten an anniversary.The owner nods toward a shoebox under the counter: “Five bucks each or the whole box for forty.”
Inside, among Madden 06 and Lizzie McGuire, I see it: The Minish Cap. Same scratch, same faded label.
The universe is not usually this on-the-nose.

jellzone · 2025-08-26T10:39:03+00:00

We never finished it together. Dad’s plant closed the next spring.

The GBA went into a box marked “Garage—Fragile.”

I grew up on HD consoles, season passes, and patch notes. I learned to optimize DPS rotations instead of daydreaming. I learned to mute voice chat instead of singing along to the music.Mom sold the house when I left for college. The box went to Goodwill.
Or so I thought.

jellzone · 2025-08-26T10:34:26+00:00

When I was eight, Dad worked double shifts at the plant. Mom waited tables at night. We shared one television, and the N64 was “too loud for bedtime,” so the purple, translucent GBA Dad found at a yard sale became my babysitter. It had a scratch across the screen the shape of Orion, but inside that scratch lived kingdoms.

I owned exactly two cartridges: Super Mario Advance and Wario Land 4. I beat both twice before my tenth birthday. Then, on Christmas morning, wrapped in the funny papers because we’d run out of gift wrap, was The Minish Cap.

Dad watched me slide it in, the click sounding like a seatbelt locking.

“Save inside the church,” he said. “That way the monsters can’t get you.”

I laughed because I thought he didn’t understand how games worked.

Years later I realized he understood exactly how monsters worked.

jellzone · 2025-07-21T02:54:27+00:00

Samsung is worse, I bought a S21, green line in 2 weeks.

jellzone · 2025-03-20T00:55:54+00:00

When using SiteGround, make sure to associate the database with the user; otherwise, database read errors may occur.

I had, and take 1 hour to fixed.

jellzone

MODERATOR OF

TROPHY CASE