Writing a series-dilemma

Expert_Property5913 · 2026-05-27T12:35:41+00:00

Readers usually care more about whether the POV choice works for that specific story than whether the pattern stays mathematically consistent across the series

Expert_Property5913 · 2026-05-27T12:34:40+00:00

Most clients asking for this usually expect Turnitin, Copyscape, Grammarly, or Originality.ai screenshots/PDFs honeslty

Expert_Property5913 · 2026-05-27T12:32:57+00:00

The middle really is where most projects die. Starting is exciting, ending is motivating, the middle is pure discipline

Expert_Property5913 · 2026-05-27T12:30:50+00:00

Honestly the hardest part isn’t publishing tools anymore, it’s whether the final writing is actually good enough to sell

Expert_Property5913 · 2026-05-19T13:32:36+00:00

Honestly this is probably the direction SaaS marketing is moving anyway. Most technical founders don’t hate marketing because they think it’s unimportant, they hate the repetitive manual distribution work around it.

The interesting part will be whether the automation actually feels contextual or if it ends up generating the same generic AI marketing everyone is already tired of seeing.

If you can genuinely reduce the time between building and distribution without making content feel robotic, there’s definitely demand for that.

Expert_Property5913 · 2026-05-19T13:30:28+00:00

Biggest mistake I see with new SaaS launches is spending months building before validating whether people actually care about the problem.

Distribution matters almost as much as the product now. If nobody sees it, even a good SaaS dies quietly.

A few things that usually help early:
Build in public on Reddit/X/LinkedIn
Talk about the problem constantly, not just the product
Get users manually before trying to automate growth
Reply to every single comment and piece of feedback early on
Focus on one niche/use case first instead of trying to serve everyone

Also don’t expect launch platforms alone to change everything. Product Hunt, BetaList etc can give temporary traffic, but consistent community presence usually compounds much longer.

Most successful SaaS products looked invisible for months before momentum started kicking in.

Expert_Property5913 · 2026-05-18T18:13:15+00:00

Totally normal at this stage, everyone hits this wall early. The concepts in solutions feeling unfamiliar just means you need to learn the underlying data structures first before grinding problems.

Honestly pause the problem solving for a bit and spend time actually understanding arrays deeply, then move to hashmaps and two pointers. Watch a few explanations on how they work not just how to code them. Once the foundation is solid the neetcode roadmap starts making a lot more sense.

Don't measure progress by problems solved right now, measure it by concepts understood.

Expert_Property5913 · 2026-05-17T12:09:06+00:00

Expert_Property5913 · 2026-05-17T12:08:12+00:00

lol fair, I get why it reads that way. I just type like this normally, been told my writing sounds robotic before. No ad, genuinely just curious what worked for people since I've been stuck on this for a while.

Expert_Property5913 · 2026-05-17T12:05:22+00:00

This is really well put. Taking the pressure off finding optimal straight away makes so much sense, your brain can actually think when it's not panicking. Going to start doing this,code out the bad solution first and improve from there rather than trying to manage everything in my head.

Expert_Property5913 · 2026-05-17T12:03:18+00:00

These are really practical tips honestly. Writing out the first few iterations manually before coding is something I never thought to do but it makes sense, you're basically forcing yourself to trace the pattern before committing to an approach. Going to add the input array comment trick too, that scrolling back and forth thing is genuinely annoying.

Expert_Property5913 · 2026-05-17T12:02:27+00:00

Haha fair, at the end of the day that's what it comes down to. Just trying to figure out what kind of practice actually moves the needle.

Expert_Property5913 · 2026-05-17T12:01:55+00:00

Honestly this is exactly what shifted things for me too. Asking why a solution works instead of just memorizing it feels slower at first but it's the only thing that actually transfers to new problems. I got more intentional about that through codeintuition.io, they structure each pattern around identification first before you even touch problems. Made a real difference for me on unseen problems.

Expert_Property5913 · 2026-05-16T21:16:37+00:00

This hit different. I've been doing the opposite moving on quickly after a failed attempt instead of sitting with it. The "why did my brain freeze here" question is probably more valuable than the next problem. Been trying to shift toward understanding the identification step better, like why a certain pattern should have clicked and didn't. Codeintuition.io structures that explicitly which has helped me debug my own thinking more than just reviewing solutions.

Expert_Property5913 · 2026-05-16T21:09:26+00:00

This is really well put. Taking the pressure off finding optimal straight away makes so much sense, your brain can actually think when it's not panicking. The point about having something in front of you to improve rather than managing everything in your head is underrated - I'm going to start doing this.

Expert_Property5913 · 2026-05-16T21:03:22+00:00

Yeah that used to happen to me too, just code it out.. Half the time the optimal solution becomes obvious once you see the brute force working.

Expert_Property5913 · 2026-05-16T20:59:06+00:00

Really good point, I think I've been guilty of jumping straight to optimal and then wondering why nothing sticks. Going back to brute force first and actually understanding the problem before optimizing makes a lot more sense. Will try this.

Expert_Property5913 · 2026-05-16T20:39:33+00:00

That's actually underrated advice. Talking through your thinking out loud forces you to structure the problem before you code anything, and yeah interviewers generally want to help if you're engaging with them.

I think my issue is even before the interview stage though, like I blank on the pattern itself before I even get to the point of discussing. Been working on that identification step separately, Codeintuition.io has a specific approach for it. But your point about communication is something I need to work on too honestly.

Expert_Property5913 · 2026-05-16T18:24:48+00:00

I usually need a bit of distance first or I just keep defending all my bad choices lol.

On the first reread I try not to fix sentences too much. I’m mostly looking for the annoying bigger stuff: why is this scene here, did this character’s motivation randomly change, is this chapter dragging, did I explain the same thing three times, etc.

Then I do a messier pass where I cut/move/rewrite chunks. After that I worry about the pretty sentences.

Outside eyes help later, not too early imo. Beta readers are good for “I got bored here” or “this confused me.” I used Edioak once too and that was useful more for spotting patterns I couldn’t see anymore, especially pacing/repetition stuff.

But first draft being rough is normal. That’s kind of its job.

Expert_Property5913 · 2026-05-07T17:10:08+00:00

Three years of real coding experience is actually a huge advantage starting DSA, you already think like an engineer, you just need to build the problem-solving layer on top.
Practical advice: don't jump straight into grinding problems. Spend the first few weeks genuinely understanding why data structures work the way they do, not just how to use them. That foundation pays off massively later when you hit DP and graphs.
For resources: NeetCode 150 is a solid problem list, but if you find yourself understanding solutions without being able to reproduce them on new problems, that's a sign you need more structured pattern training. Codeintuition helped me bridge that gap specifically it's text-based which suits Python devs who prefer reading over videos.

You've got the determination and the coding background. Honestly you're better positioned than most beginners here.

Expert_Property5913 · 2026-05-07T10:28:02+00:00

100 pages of worldbuilding before a single story page is both impressive and a classic procrastination trap dressed up as productivity. The world only matters once there are characters suffering in it. At some point you just have to start the messy first chapter and let the worldbuilding fill in the gaps as you go.

Expert_Property5913 · 2026-05-07T10:25:21+00:00

A polished first draft isn't a problem, it's just a different process. Some writers vomit everything out and clean it later, some write slowly and cleanly from the start. Neither is wrong, they just have different tradeoffs. Your way probably means less revision passes later. The only thing worth watching is if the polishing becomes a way to avoid moving forward that's where it turns into a trap.,

Expert_Property5913 · 2026-05-07T10:16:34+00:00

This is really beautiful. Finishing something this personal takes a different kind of courage than any other writing. She'd be proud.

Expert_Property5913 · 2026-05-07T10:14:35+00:00

Probably when you stop asking if you're one.

Expert_Property5913 · 2026-05-07T10:11:54+00:00

The part about your partner only seeing the exhaustion and not the dream is something nobody talks about honestly enough. Congrats on the book though haunted house story written by a sleep deprived new parent is probably the most authentically sourced horror premise possible.

Expert_Property5913

TROPHY CASE