Since Jamstack can be such a force multiplier, there are many agencies capitalizing on it to do great work.
And you can still nominate your Jamstack Agency Of The Year.
...if you're quick.
https://jamstackconf.com/jammies/ https://twitter.com/Netlify/status/1429794212422340610
And you can still nominate your Jamstack Agency Of The Year.
...if you're quick.
https://jamstackconf.com/jammies/ https://twitter.com/Netlify/status/1429794212422340610
This is going to be ruddy great! https://twitter.com/JamstackLondon/status/1429755880472514561
@csswizardry @sarah_edo This is the ultimate praise and shade in a single statement.
And not something I can argue with.
And not something I can argue with.
#TweetsRefactoredByMyLegalTeam
In my personal experience, which may differ to yours, "product" and "products" are examples of visually similar and easy to confuse variable names.
Finding a collective noun or compound word instead of "products" seems to save me some mistakes. https://twitter.com/philhawksworth/status/1428656544963497984
In my personal experience, which may differ to yours, "product" and "products" are examples of visually similar and easy to confuse variable names.
Finding a collective noun or compound word instead of "products" seems to save me some mistakes. https://twitter.com/philhawksworth/status/1428656544963497984
@piccalilli_ @bencodezen Got it.
Puppies and kittens only (in exactly even quantities) from here on in.
:)
Puppies and kittens only (in exactly even quantities) from here on in.
:)
@jaffathecake @heydonworks @bencodezen Agreed.
But please don't stop my fun of adopting the following (self-explanatory) variable names:
¯\_(ツ)_/¯
(╯°□°)╯︵ ┻━┻
┬─┬ノ( º _ ºノ)
ノ•ᴥ•ʔノ ︵ ┻━┻
(┛◉Д◉) ┛彡┻━┻
(ノಠ益ಠ)ノ彡
But please don't stop my fun of adopting the following (self-explanatory) variable names:
¯\_(ツ)_/¯
(╯°□°)╯︵ ┻━┻
┬─┬ノ( º _ ºノ)
ノ•ᴥ•ʔノ ︵ ┻━┻
(┛◉Д◉) ┛彡┻━┻
(ノಠ益ಠ)ノ彡
@jaffathecake @heydonworks @bencodezen Does it make the need for thoughtfully naming your variables go away? If so, I'm ready for some fun.
Regardless of the other characteristics of the programming language, if it had a troupe data type, I'd embrace it like a long lost sibling. https://twitter.com/tjcrowder/status/1428665429929644032
@piccalilli_ @bencodezen Note to self:
If you use pseudocode to illustrate a point, make it far more pseudo than you were planning. Or better still, make the point without it.
And perhaps I'll park my tweet about embracing CSS in JS in order to polyfill for "colour" for another day.
If you use pseudocode to illustrate a point, make it far more pseudo than you were planning. Or better still, make the point without it.
And perhaps I'll park my tweet about embracing CSS in JS in order to polyfill for "colour" for another day.
@heydonworks @jaffathecake @bencodezen Fair... the nub of the advice here was just to try to avoid simply pluralizing a noun.
Within that, sure, there are likely some good conventions/preferences to also imply things more deeply about the data type.
Within that, sure, there are likely some good conventions/preferences to also imply things more deeply about the data type.
@jaffathecake @bencodezen Yeah... I thought that after posting too.. but I think that the general point about not simply plauralizing nouns remains.
@Hicksyfern @_phzn @bencodezen That's true.
My code comments are entirely English vernacular here and not intended to have deeper CS meaning. But I think the principle stands regardless if it were a set, list, array, collection, bunch, clutch, gaggle, herd, or troupe. :)
My code comments are entirely English vernacular here and not intended to have deeper CS meaning. But I think the principle stands regardless if it were a set, list, array, collection, bunch, clutch, gaggle, herd, or troupe. :)
@dutchcelt @bencodezen Yeah. It has always felt obvious to me to just pluralize nouns for collections of that noun. And that reads wonderfully. But spotting a missing or a superfluous "s" is so easy to botch, even (especially?!) after staring at the code for a while!
@rem @contentful I've always used the latter. And that's what I hear used by the folks I know who work there.
The amount of time I spend debugging a common mistake dropped considerably after @bencodezen advised me to rethink my naming conventions for collections of things.
Bye-bye "products".
Hello "productList".
Bye-bye "products".
Hello "productList".