Coding/Programming

I hope i have avoided these particular issues. The already noted belief that "good code should explain itself" means that certainly try to be consistent in variable naming for exampe. Now im individualstic and working alone on my hobby projects so im not one to accept something just because it is standard practice. That these rules usually seem reasonable to me. Something does not became standard pratice without reason after all. So i generally follow them anyway.

Well that is something im worried about.

Edited by Risa123 on Aug 1st 2022 at 11:12:44 AM

With what was said I guess I'll promise to not seek out beta testers on the forums because it would be kinda advertizing and keep apps for personal use. Maybe I could ask the admins at some point about usage permissions, as there is a Laconic overlay extension someone did publish for Chrome Web Store.

Also as someone with database experience, what was said later feels very relatable.

Edited by Amonimus on Aug 1st 2022 at 12:23:04 PM

I would say seeking beta testors falls under the asking for help example Fighteer gave. That say i cannot speak for him.

Edited by Risa123 on Aug 1st 2022 at 11:44:10 AM

Coding specifically for TV Tropes is a grey area. Obviously we can't stop you from writing apps or browser extensions that modify the user experience, but we also can't support them, and using the forums as a venue to promote them could create the impression that we do. We also can't guarantee that any such code is bug-free or non-malicious.

Edited by Fighteer on Aug 2nd 2022 at 8:03:47 AM

I suppose there is a reason why you can't support them ? Not complaining just curious.

Because none of the moderators is a developer for the site and the admins don't have the time to directly support user-developed code. If people start advertising "TV Tropes extensions" it creates the implication that we condone them, and people will ask us for support if they don't work.

In that case you could just create a disclaimer, but as i said im ok with this policy. I can understand that you have probably decided it is not worth any potentional problems.

Recently tried to play with SQL/PHP to see how it would look like if articles (trope/work) and examples were stored separately. You know, just checking. While manageable and auto-crosswicking works, it wasn't fun to design, at all.

I thought the big upgrade when Fast Eddie handed development over to professionals was 2.0.

Said screw it and made automated wick checker in AutoHotKey, didn't forget to put delay this time. What, list all links in the Related tab, shuffle, reduce to 50, copy respective source pages, crop the paragraph with the wikiword and save to a notepad. Because I really like doing two hours of copypasting in two minutes.

Thanks, Amonimus for telling me about this thread!

My Python "Which of the wicks on work page are crosswicked?" checker: here.

And in response to:

Actually, work subpages are easy. Just Request them in sequence and append their extracted wicks to wicksInWorkPage... But that would raise the request count, for one thing. mmm.

...

True, but if an example talks about a wick, then it's probably relevant to have a entry about the work. Probably.

Edited by Malady on Nov 16th 2023 at 1:36:17 AM