D. Moonfire @dmoonfire@octodon.social

Right now, Author Intrusion is sadly just a collection of black triangles (technical milestones but nothing fancy to look at).

I have a weird workflow though. I'm using Rider/VS Code to do the coding on my Linux machine, getting it working, then pushing up to my WIndows machine to do code cleanup using ReSharper and documentation using GhostDoc. Sadly, those two functions are non-Linux AFAIK.

Flight of the Scions 11: Stonewait's Gallery #Action #YoungAdult #Patreon #OneDollarPatreon
https://fedran.com/flight-of-the-scions/chapter-11/

Kanéko's curiosity and skin color get her in trouble when she spies a steam-powered vehicle in front of the inn.

Have to call it a day with Author Intrusion. I got the Gulp-inspired project loading and a simplified solution-like file list but I need to get the NuGet-based package loading that works like NPM (packages installed in the novel directory instead of the application).

Like NPM, a specific novel can have a specific version of a plugin and produce consistent results even if my tools/libraries evolve years later. I got burned by not having this with my old publication frameworks.

@LynnLamb Thank you. If you have questions, comments, feel free to ask. I love talking!

Bah, why didn't anyone tell me that @kevinbeynon was on Mastodon? Okay, I know why. You aren't my babysitter. :P

Check out Libreture, it's a DRM-free (yay) ebook hosting that looks really promising.

The fun part is getting Autofac/DI working with unit tests is a challenge. I think I figured out a workable pattern.

Right now, I'm starting with gulp-inspired management where it finds the project (.aipy) anywhere underneath the root director or where you provide the path. That way, you can call the command inside the project.

I'm writing AI to be like a programming cool, with a decent CLI and additional tools.

Today, I get a good start with Author Intrusion. Mostly it was gutting the previous version and rebuilding it properly. In the old version, I cut corners to get to the "good stuff" but ended up having the system choke on performance.

This time, I'm writing it slower with TDD in mind, mostly making sure each part is fairly solid before moving to the next.

It isn't as fun but I have higher hopes I can actually finish this time. :)

@Alamantus According to George Carlin, it was our purpose in life and now the human race can be phased out.

I should have CWd that. Sorry.

I've always said that I'm writing AI for "programmers who are writers" so having a more complex query should be okay. If it saves me 30-50 hours not building up a CSS parse tree, then probably worth it. :)

Well, I restarted Author Intrusion again. The last iteration was promising but I was spending my time working on reinventing stuff because I thought it was what I want. Earlier this week, I realized what it was and how I could use an existing library to hopefully avoid spinning wheels.

It does mean I can't use CSS selectors for phrases. Instead, I'll use XPath and C#'s XElement.

No `file.chapter word` and probably `//file[has-class('chapter')//word`.

Not as pretty but I need this working.

@JSGarner @PletchaPJWebb

I know exactly what you mean. On the other hand, these are the highest they've ever been so I can't argue. :D

I'm up to three hours of sleep in the last forty-eight. I hate vacations and the surge of work I have to do before I go on one.

Working late tonight, it sucks.

On the other hand, I got fan mail, so that was great.

They hated the end of my last serial. That sucked.

They said they liked everything I've written. That was cool.

They wanted to commission me to rewrite it happier. Sadly, I already have a commission for the sequel, so I don't feel right in forking the story. That sucks more.

I'm not sure how to handle this.

For tonight, though, I'll probably just putz since I have to work once the kids go to bed.

Bummer, my current code base for Author Intrusion hadn't solidified enough so I have no clue how to get it going again.

I mean, I can always start over but I'd like to avoid that.