#betareaders — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #betareaders, aggregated by home.social.
-
CW: My Git experimentation for beta reader reviewing thoughts.
As I continue to use my Git workflow for beta readers, I am realizing Git just isn't for fiction prose and everything I am doing is tricks and hacks to work with it.
I ended up hiring someone to build me a python script that is interactive.
The common frustration I ran into was,
let's say Jason edited a paragraph in Chapter 1.
Jane edited the same paragraph but a different section.
I wanted Git to smartly present these as changes and have me reject, accept, and or set them aside for later.
It couldn't do that with Git. I'd eventually have to open files and compare myself, which defeats the reasoning. I was contorting Git to the point it stopped making sense to hack and contort.
I gave up and just use Git as glorified Cloud storage and for tracking my own changes to my own MD files.
My trial and errors to turn Git into more of a track changes system that was screen reader friendly wasn't cutting it, so I just decided to pay someone money to make me a non-vibed Python script that includes multiple things such as Critic Markup support, Pandoc's Track Changes support when I convert DOCX to MD using --track-changes=all,
and other goodies that compare comments, compares insertions, deletions, and far more inside of text files and MD files.
I *could* use Google Docs and Track changes, but I like working with local text files, and I have more than five beta readers.
#Git #ReadingCommunity #Beta #BetaReaders #Python #Programming
-
CW: My Git experimentation for beta reader reviewing thoughts.
As I continue to use my Git workflow for beta readers, I am realizing Git just isn't for fiction prose and everything I am doing is tricks and hacks to work with it.
I ended up hiring someone to build me a python script that is interactive.
The common frustration I ran into was,
let's say Jason edited a paragraph in Chapter 1.
Jane edited the same paragraph but a different section.
I wanted Git to smartly present these as changes and have me reject, accept, and or set them aside for later.
It couldn't do that with Git. I'd eventually have to open files and compare myself, which defeats the reasoning. I was contorting Git to the point it stopped making sense to hack and contort.
I gave up and just use Git as glorified Cloud storage and for tracking my own changes to my own MD files.
My trial and errors to turn Git into more of a track changes system that was screen reader friendly wasn't cutting it, so I just decided to pay someone money to make me a non-vibed Python script that includes multiple things such as Critic Markup support, Pandoc's Track Changes support when I convert DOCX to MD using --track-changes=all,
and other goodies that compare comments, compares insertions, deletions, and far more inside of text files and MD files.
I *could* use Google Docs and Track changes, but I like working with local text files, and I have more than five beta readers.
#Git #ReadingCommunity #Beta #BetaReaders #Python #Programming
-
CW: My Git experimentation for beta reader reviewing thoughts.
As I continue to use my Git workflow for beta readers, I am realizing Git just isn't for fiction prose and everything I am doing is tricks and hacks to work with it.
I ended up hiring someone to build me a python script that is interactive.
The common frustration I ran into was,
let's say Jason edited a paragraph in Chapter 1.
Jane edited the same paragraph but a different section.
I wanted Git to smartly present these as changes and have me reject, accept, and or set them aside for later.
It couldn't do that with Git. I'd eventually have to open files and compare myself, which defeats the reasoning. I was contorting Git to the point it stopped making sense to hack and contort.
I gave up and just use Git as glorified Cloud storage and for tracking my own changes to my own MD files.
My trial and errors to turn Git into more of a track changes system that was screen reader friendly wasn't cutting it, so I just decided to pay someone money to make me a non-vibed Python script that includes multiple things such as Critic Markup support, Pandoc's Track Changes support when I convert DOCX to MD using --track-changes=all,
and other goodies that compare comments, compares insertions, deletions, and far more inside of text files and MD files.
I *could* use Google Docs and Track changes, but I like working with local text files, and I have more than five beta readers.
#Git #ReadingCommunity #Beta #BetaReaders #Python #Programming
-
CW: My Git experimentation for beta reader reviewing thoughts.
As I continue to use my Git workflow for beta readers, I am realizing Git just isn't for fiction prose and everything I am doing is tricks and hacks to work with it.
I ended up hiring someone to build me a python script that is interactive.
The common frustration I ran into was,
let's say Jason edited a paragraph in Chapter 1.
Jane edited the same paragraph but a different section.
I wanted Git to smartly present these as changes and have me reject, accept, and or set them aside for later.
It couldn't do that with Git. I'd eventually have to open files and compare myself, which defeats the reasoning. I was contorting Git to the point it stopped making sense to hack and contort.
I gave up and just use Git as glorified Cloud storage and for tracking my own changes to my own MD files.
My trial and errors to turn Git into more of a track changes system that was screen reader friendly wasn't cutting it, so I just decided to pay someone money to make me a non-vibed Python script that includes multiple things such as Critic Markup support, Pandoc's Track Changes support when I convert DOCX to MD using --track-changes=all,
and other goodies that compare comments, compares insertions, deletions, and far more inside of text files and MD files.
I *could* use Google Docs and Track changes, but I like working with local text files, and I have more than five beta readers.
#Git #ReadingCommunity #Beta #BetaReaders #Python #Programming
-
CW: My Git experimentation for beta reader reviewing thoughts.
As I continue to use my Git workflow for beta readers, I am realizing Git just isn't for fiction prose and everything I am doing is tricks and hacks to work with it.
I ended up hiring someone to build me a python script that is interactive.
The common frustration I ran into was,
let's say Jason edited a paragraph in Chapter 1.
Jane edited the same paragraph but a different section.
I wanted Git to smartly present these as changes and have me reject, accept, and or set them aside for later.
It couldn't do that with Git. I'd eventually have to open files and compare myself, which defeats the reasoning. I was contorting Git to the point it stopped making sense to hack and contort.
I gave up and just use Git as glorified Cloud storage and for tracking my own changes to my own MD files.
My trial and errors to turn Git into more of a track changes system that was screen reader friendly wasn't cutting it, so I just decided to pay someone money to make me a non-vibed Python script that includes multiple things such as Critic Markup support, Pandoc's Track Changes support when I convert DOCX to MD using --track-changes=all,
and other goodies that compare comments, compares insertions, deletions, and far more inside of text files and MD files.
I *could* use Google Docs and Track changes, but I like working with local text files, and I have more than five beta readers.
#Git #ReadingCommunity #Beta #BetaReaders #Python #Programming