Simons Mith
@simons-mith.bsky.social
I may not be as colourful as my avatar, but I do have better posture.
I'm intending to post a mixture of daily lies, and whatever other stuff - serious or nonsense - comes to my attention. Obviously, my real-world name is a closely-guarded secret.
I'm intending to post a mixture of daily lies, and whatever other stuff - serious or nonsense - comes to my attention. Obviously, my real-world name is a closely-guarded secret.
Reposted by Simons Mith
Leaflet Publications are great for blogs.
Now with Looseleafs you can do more Medium-style or gdocs-style publishing too!
This ALSO makes it perfect for Bluesky longposting! Share > 300 chars, w/o the limitations of a thread.
Just go to leaflet.pub/new + publish as looseleaf!
Now with Looseleafs you can do more Medium-style or gdocs-style publishing too!
This ALSO makes it perfect for Bluesky longposting! Share > 300 chars, w/o the limitations of a thread.
Just go to leaflet.pub/new + publish as looseleaf!
November 26, 2025 at 8:56 PM
Leaflet Publications are great for blogs.
Now with Looseleafs you can do more Medium-style or gdocs-style publishing too!
This ALSO makes it perfect for Bluesky longposting! Share > 300 chars, w/o the limitations of a thread.
Just go to leaflet.pub/new + publish as looseleaf!
Now with Looseleafs you can do more Medium-style or gdocs-style publishing too!
This ALSO makes it perfect for Bluesky longposting! Share > 300 chars, w/o the limitations of a thread.
Just go to leaflet.pub/new + publish as looseleaf!
G'kxxkxk - Demon Prince of Unreachable Itches
November 26, 2025 at 4:07 PM
G'kxxkxk - Demon Prince of Unreachable Itches
needed, and if you want to avoid matching 2025AD with 8:25 pm. But who's still working at half past eight in the evening, right?
November 26, 2025 at 12:31 AM
needed, and if you want to avoid matching 2025AD with 8:25 pm. But who's still working at half past eight in the evening, right?
PS, never use 'new', 'old', 'legacy' or, of course, 'final' or the gods will laugh at you. I suggest the date instead - from YYYY to YYYY-MM-DD-HHMM format depending on how much granularity you need. [missing hyphen between HH and MM intended.] When searching for a year, add the trailing hyphen if
November 26, 2025 at 12:30 AM
PS, never use 'new', 'old', 'legacy' or, of course, 'final' or the gods will laugh at you. I suggest the date instead - from YYYY to YYYY-MM-DD-HHMM format depending on how much granularity you need. [missing hyphen between HH and MM intended.] When searching for a year, add the trailing hyphen if
If there's no other obvious order to sequence the descriptors in, at least use alphabetical order. An asset that you can't find because it's got an unguessable name is effectively lost, and an asset that almost but not quite follows the naming rules is a recipe for software bugs (or shipping errors)
November 26, 2025 at 12:22 AM
If there's no other obvious order to sequence the descriptors in, at least use alphabetical order. An asset that you can't find because it's got an unguessable name is effectively lost, and an asset that almost but not quite follows the naming rules is a recipe for software bugs (or shipping errors)
That reminds me of something else - when a base item has multiple descriptors, list the descriptors in a consistent order. The ideal is to be able to predict what an item's name /should/ be before even going to check whether it exists.
e.g. Barrel, size colour contents damage
e.g. Barrel, size colour contents damage
November 26, 2025 at 12:19 AM
That reminds me of something else - when a base item has multiple descriptors, list the descriptors in a consistent order. The ideal is to be able to predict what an item's name /should/ be before even going to check whether it exists.
e.g. Barrel, size colour contents damage
e.g. Barrel, size colour contents damage
Yeah, and I like
Widget, special custom thingy
New widget, custom special thingy
Widget, special, thingy, legacy, custom
('New' widget, by the way, was introduced in 1994 to replace the 1990 version). Note the mixed levels of naming hierarchy over the years, and the differences in feature ordering
Widget, special custom thingy
New widget, custom special thingy
Widget, special, thingy, legacy, custom
('New' widget, by the way, was introduced in 1994 to replace the 1990 version). Note the mixed levels of naming hierarchy over the years, and the differences in feature ordering
November 25, 2025 at 11:42 PM
Yeah, and I like
Widget, special custom thingy
New widget, custom special thingy
Widget, special, thingy, legacy, custom
('New' widget, by the way, was introduced in 1994 to replace the 1990 version). Note the mixed levels of naming hierarchy over the years, and the differences in feature ordering
Widget, special custom thingy
New widget, custom special thingy
Widget, special, thingy, legacy, custom
('New' widget, by the way, was introduced in 1994 to replace the 1990 version). Note the mixed levels of naming hierarchy over the years, and the differences in feature ordering
For art assets, I'd like to ask whether you'd consider going beyond your one-level examples to two levels? I've a hunch that three levels or more is too fine-grained - unless you have millions of things needing names, or many thousands of very similar things. What's the most levels you'd suggest?
November 25, 2025 at 11:35 PM
For art assets, I'd like to ask whether you'd consider going beyond your one-level examples to two levels? I've a hunch that three levels or more is too fine-grained - unless you have millions of things needing names, or many thousands of very similar things. What's the most levels you'd suggest?
corporation, one level of hierarchy would have been sufficient:
Fuse, blah blah
Screw, blah blah blah
Washer, blah blah
You only need multiple levels of heirarchy when you're a truly huge organisation like the US army. For most ordinary uses, one level is enough; I advise not getting carried away.
Fuse, blah blah
Screw, blah blah blah
Washer, blah blah
You only need multiple levels of heirarchy when you're a truly huge organisation like the US army. For most ordinary uses, one level is enough; I advise not getting carried away.
November 25, 2025 at 11:31 PM
corporation, one level of hierarchy would have been sufficient:
Fuse, blah blah
Screw, blah blah blah
Washer, blah blah
You only need multiple levels of heirarchy when you're a truly huge organisation like the US army. For most ordinary uses, one level is enough; I advise not getting carried away.
Fuse, blah blah
Screw, blah blah blah
Washer, blah blah
You only need multiple levels of heirarchy when you're a truly huge organisation like the US army. For most ordinary uses, one level is enough; I advise not getting carried away.
used over the years and over multiple companies.
And some people haven't bothered with any level of hierarchy, others have gone to the opposite extreme, and the parts look like they've been named in reverse Polish notation.
So there's a second important consideration:
Even for us, and we're a big
And some people haven't bothered with any level of hierarchy, others have gone to the opposite extreme, and the parts look like they've been named in reverse Polish notation.
So there's a second important consideration:
Even for us, and we're a big
November 25, 2025 at 11:28 PM
used over the years and over multiple companies.
And some people haven't bothered with any level of hierarchy, others have gone to the opposite extreme, and the parts look like they've been named in reverse Polish notation.
So there's a second important consideration:
Even for us, and we're a big
And some people haven't bothered with any level of hierarchy, others have gone to the opposite extreme, and the parts look like they've been named in reverse Polish notation.
So there's a second important consideration:
Even for us, and we're a big
I've hit the same problem with my company's IRL parts lists. they have been generated over years and ain't super consistent. The ideal would be much the same way you're talking about here:
Fuse, 5A 20mm 250V
Fuse, 7A 20mm 250V etc.
But you get a mixture of different naming schemes which have been
Fuse, 5A 20mm 250V
Fuse, 7A 20mm 250V etc.
But you get a mixture of different naming schemes which have been
November 25, 2025 at 11:26 PM
I've hit the same problem with my company's IRL parts lists. they have been generated over years and ain't super consistent. The ideal would be much the same way you're talking about here:
Fuse, 5A 20mm 250V
Fuse, 7A 20mm 250V etc.
But you get a mixture of different naming schemes which have been
Fuse, 5A 20mm 250V
Fuse, 7A 20mm 250V etc.
But you get a mixture of different naming schemes which have been
NO! BAD Darren! They have these little custom-designed telephones...
November 25, 2025 at 12:18 AM
NO! BAD Darren! They have these little custom-designed telephones...
Possibly two storeys if you were a DM
November 24, 2025 at 9:54 PM
Possibly two storeys if you were a DM
What, no, you build a shelter out of them
November 24, 2025 at 9:53 PM
What, no, you build a shelter out of them
Yes, all you do is sit staring at the blank sheet of paper until the drops of blood form on your forehead.
November 24, 2025 at 2:45 PM
Yes, all you do is sit staring at the blank sheet of paper until the drops of blood form on your forehead.
... Says some cunt
November 24, 2025 at 2:20 PM
... Says some cunt
But try doing it with mañana and you'll get a cramp in your tongue
November 24, 2025 at 2:14 PM
But try doing it with mañana and you'll get a cramp in your tongue
It's also hard to stop spelling bananana at the 'right' point.
And 'u' and 'e' are just 'n' and 'a' written upside down. Coincidence? I think not.
And 'u' and 'e' are just 'n' and 'a' written upside down. Coincidence? I think not.
November 24, 2025 at 2:12 PM
It's also hard to stop spelling bananana at the 'right' point.
And 'u' and 'e' are just 'n' and 'a' written upside down. Coincidence? I think not.
And 'u' and 'e' are just 'n' and 'a' written upside down. Coincidence? I think not.
Pages? Yeah, ain't got time fo' dat. I'm cool with a few paras though. Sometimes a back story isn't a straitjacket, it's, um support. Or possibly even costume. But really, a character's /story/ begins at the start of the game, so back story should be more like a book intro, not a prequel novella.
November 24, 2025 at 10:26 AM
Pages? Yeah, ain't got time fo' dat. I'm cool with a few paras though. Sometimes a back story isn't a straitjacket, it's, um support. Or possibly even costume. But really, a character's /story/ begins at the start of the game, so back story should be more like a book intro, not a prequel novella.
You don't /have/ to publish the books you wrote in strict chronological sequence...
November 24, 2025 at 9:33 AM
You don't /have/ to publish the books you wrote in strict chronological sequence...
If it won't sell, there's no point publishing it. That's the real cut-off criterion. There's a degree of 'finding the right publisher' and 'finding the right audience' which tilts things the right way, but if you can't be reasonably sure of decent sales, trying afresh may well be more efficient.
November 24, 2025 at 9:31 AM
If it won't sell, there's no point publishing it. That's the real cut-off criterion. There's a degree of 'finding the right publisher' and 'finding the right audience' which tilts things the right way, but if you can't be reasonably sure of decent sales, trying afresh may well be more efficient.
Yes, but you might also want shop names, ship names, tavern names, noble titles, unit names etc. as well, so I'd advise putting those on the minor NPC sheets to avoid cross-referring
November 24, 2025 at 9:22 AM
Yes, but you might also want shop names, ship names, tavern names, noble titles, unit names etc. as well, so I'd advise putting those on the minor NPC sheets to avoid cross-referring
Where are her Uzis??
November 24, 2025 at 12:31 AM
Where are her Uzis??
Keep the advanced tips (Out and then in? Or in followed by out?) for your inevitable book and tie-in video.
November 24, 2025 at 12:27 AM
Keep the advanced tips (Out and then in? Or in followed by out?) for your inevitable book and tie-in video.