At the risk of disembowelment, defenestration, quartering, incineration, salting and irradiation for even bringing this up, my suggestion is this:
You can do it all, by yourself, with a level of expediency that will in no way sap the quality. Remember all those hilarious and oddly productive (and necessary) interactions with The Computer in Paranoia?
Well, brush of those clever, patient communication skills and start to explain one of your products to Friend Computer. Feed it all of your already finished text. Explain what you need in order to have the publication ready to go.
Ask it for a strategic checklist for next steps and a process for completion. Ask it for suggestions, for artwork. Ask it to take your text descriptions of maps for ideas of useable maps.
React to Computer with challenging questions. Point out how badly it has gotten things, how artificial, how false. Be explicit. Then review its response. Refine the next strategy, checklist and content until it is closer to what you need.
It may not cross the goal line, but it will break the log jam, it will regain your momentum. It is how I code now, and it hasn't made me dumber. Game Design is specialized form of coding.
AI assistance is a terrible weapon when used incorrectly, but when implemented with some modicum of wisdom, restraint and utilitarian ruthlessness, it is the sword that cut the Gordian Knot.
A Thousand Suns is not using your considerable strength as a writer, but your less-beloved skill as an editor. 90% of that work is changing your natural voice in those areas where your natural voice is not useful to your consumer. That's not fun game design. It is the ideal work for editorial assistance from AI. You can show the AI an example of the previous edition and then your revised edited version, then give it the rest of the unedited portion and ask AI to clean it up in much the same way, and give you back a redline version.
Then you shift from editor to reader - trading a lesser, boring strength for one of your greater, exciting strengths! (or more technically, from copyeditor to line-editor) You don't have to accept any of the suggested changes, but if you accept even half of them, you could potentially have the text revisions of A Thousands Suns done by the end of the month.
Based on a similar situation I had last year, I'd guess that it would reduce your personal time to finish the project from 50 hours to maybe 8, with about an hour of direct interaction with the AI agent. It is closer to using a spellchecker than asking HAL for help.
This article may help:
ReplyDeletehttps://theproductiveengineer.net/hardest-or-easiest-work-first-what-the-research-shows/
At the risk of disembowelment, defenestration, quartering, incineration, salting and irradiation for even bringing this up, my suggestion is this:
ReplyDeleteYou can do it all, by yourself, with a level of expediency that will in no way sap the quality. Remember all those hilarious and oddly productive (and necessary) interactions with The Computer in Paranoia?
Well, brush of those clever, patient communication skills and start to explain one of your products to Friend Computer. Feed it all of your already finished text. Explain what you need in order to have the publication ready to go.
Ask it for a strategic checklist for next steps and a process for completion. Ask it for suggestions, for artwork. Ask it to take your text descriptions of maps for ideas of useable maps.
React to Computer with challenging questions. Point out how badly it has gotten things, how artificial, how false. Be explicit. Then review its response. Refine the next strategy, checklist and content until it is closer to what you need.
It may not cross the goal line, but it will break the log jam, it will regain your momentum. It is how I code now, and it hasn't made me dumber. Game Design is specialized form of coding.
AI assistance is a terrible weapon when used incorrectly, but when implemented with some modicum of wisdom, restraint and utilitarian ruthlessness, it is the sword that cut the Gordian Knot.
A Thousand Suns is not using your considerable strength as a writer, but your less-beloved skill as an editor. 90% of that work is changing your natural voice in those areas where your natural voice is not useful to your consumer. That's not fun game design. It is the ideal work for editorial assistance from AI. You can show the AI an example of the previous edition and then your revised edited version, then give it the rest of the unedited portion and ask AI to clean it up in much the same way, and give you back a redline version.
ReplyDeleteThen you shift from editor to reader - trading a lesser, boring strength for one of your greater, exciting strengths! (or more technically, from copyeditor to line-editor) You don't have to accept any of the suggested changes, but if you accept even half of them, you could potentially have the text revisions of A Thousands Suns done by the end of the month.
Based on a similar situation I had last year, I'd guess that it would reduce your personal time to finish the project from 50 hours to maybe 8, with about an hour of direct interaction with the AI agent. It is closer to using a spellchecker than asking HAL for help.