• 0 Posts
  • 128 Comments
Joined 3 years ago
cake
Cake day: August 11th, 2023

help-circle
  • I will argue for standardization/normalization here though. If the change isn’t significant enough or fundamentally needed to achieve something that need or REALLY want, why does it matter if it does catch on?

    Like I would rather people make 100 useful things, than polish/refactor/tweak things a 100 times causing everyone to have to learn a 100 new UX changes (yes we are users of the frameworks and languages, though are just different UIs and how we use it is our UX)




  • Zen of python (PEP 20):

    Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren’t special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you’re Dutch. Now is better than never. Although never is often better than right now. If the implementation is hard to explain, it’s a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea – let’s do more of those!


  • The rule I see is functions should be fairly atomic and almost obvious what they do in context of the code.

    At least for my small brain that’s how I like it. I can understand some complex abstractions but rembering that actually this function behaves in three different ways depending on what flag is set is awful. It means you could look at one example and be totally wrong in another. Ideally you could guess the functions purpose even in a black box setting based on inputs outputs and the name should then make it obvious.