Paramdeo Singh @oedmarap@fosstodon.org

@binyamin Interestingly, Google and other search engines will show subdomains of a website as separate results, which is good to ensure your own properties are on the front page if for example you use "blog.binyam.in".

However, you'll get more canonical traffic and backlink ranking if everything is hitting one domain. Doubly so for IndieWeb/microformats2 markup.

You'll have to maintain two separate sites if you go with the former, but I understand the content vs. playground angle.

@0PT41N Duck yeah!

@mycroft Not unethical at all. The world moves on, and in the best of scenarios you can take that profit and actually use it as a resource to effect meaningful change; an ethical ulterior motive.

Otherwise, it'll run it's course, with or without your intervention. So you might as well extract from it what you can and then repurpose as necessary.

IMHO.

@lig No worries, to each his own. Once you find something you're comfortable with, use that.

@lig Exactly, yep. Given the ratio of sensible two letter words vs. two letter acronyms (there are more of the latter than of the former) this shouldn't be a problem.

@lig I think you misunderstand what I'm trying to say.

The baseline rule is the character number. This is the default. ID fits here when it's the second term after 'object' simply because it's <3 chars.

The proper-noun supersedes the above rule (on occasion). IATA fits here after 'airport' for example.

Edge case will happen but the above should cover ~90% of naming situations (and that's the goal, really).

@lig Nothing. Proper nouns should always be all caps if they're an acronym, e.g. UN, UNICEF, IATA, NYC, GCP, AWS, etc.

@lig IATA is a proper noun (International Air Transport Association).

@lig Exactly the reason I don't use camel case. 🙂

But I'm just suggesting adding _some_ type of sanity checks into the naming schemes. Edge cases will happen but not very often.

@lig Well to my point, ID isn't a proper noun (acronym), so it falls back on the character-limited rule without any further context.

@lig Exceptions for proper nouns yes, e.g. orgFSF, orgEFF, amountBTC, amountUSD, airportJFK, etc.

@lig I hear you. If you're coding as part of a team/org then naming conventions are forced upon you.

In that case, might I suggest going for a more structured approach.

If the second word has less than three letters then capitalize it, otherwise use camel case.

E.g. objectID, objectRef, objectName, targetDB, targetArr, targetArray, etc.

Hope that helps. 👍

@lig Just echoing similar sentiments here, I would go with 'object_id' as I personally find camelCase to be horrifyingly unreadable.

@pheonix Interstellar. They had Kip Thorne vet all of the theoretical and astrophysics that were used in the film.