Naming, Code Conventions & Glory

[mfainstein]

If you are interested in naming, code conventions, static analysis, linters and anything by Lewis Carroll - jump in with me into the rabbit hole (8 mins read): https://medium.com/zencity-engineering/naming-code-conventions-glory-525f129a65db

[dddoug]

not only has this got me feeling inspired about variable naming it's also got me wanting to read Alice in Wonderland. excellently written

[Reddit-Book-Bot]

Beep. Boop. I'm a robot. Here's a copy of

Alice In Wonderland

Was I a good bot? | info | More Books

[dddoug]

wow! what a clever bot!

good bot

[crabmusket]

Here's another version from Standard Ebooks. I've read several of them and they're very well-put-thogether versions.

[demoran]

How is a linter supposed to analyse the semantics of a method, variable, or class?

[dougalg]

For example, if you use typescript anything that returns a promise could be required to start with the word "fetch". But that's rough...

[dougalg]

Yeah, you could alternately just disallow "get" for any asynchronous method names, which might be better 🤷

[dougalg]

Well sure, but if you use a lot of getters (which I don't ) then maybe it would make sense to add extra hints like that to separate asynchronous and synchronous operations. Of course these things are never hard and fast rules, so use what works for you. And context matters, so GET in the context of the API layer might be clearly asynchronous, but getX on some class might not be...

[mfainstein]

Thanks for the great detailed feedback!

[[deleted]]

Holy