'Clean Code' by Uncle Bob is a good place to start when answering these questions.
And here I was, almost agreeing. Clean code is defining quality through aesthetics, and that book is a very bad advice of how to define anything
'Clean Code' by Uncle Bob is a good place to start when answering these questions.
And here I was, almost agreeing. Clean code is defining quality through aesthetics, and that book is a very bad advice of how to define anything
Tortoise might be fine too
Besides, they say ‘read really old texts’ as if this is easily achieved right now, which it is not
I think, e is silent in baked and not in naked. But that's kind of like Sean Bean
Yeah, there are maybe a couple of reasonable ideas like using background and making comments stand out more, but that's it. Especially weird is the idea about light theme not being used because of syntax highlight
I watched me fail for much longer
But there's a caveat 🌚
Same as many long debunked concepts, sometimes even declared wrong by their own original author, it will continue to have followers and will never completely fade away. For this reason I don't think that talking about it sometimes is a wrong thing
Just wanted to get back to tell that I tried graph1 to mess around with non-linear projection, it seemed like an interesting crate but it felt like it's a bit too low level for doing a GUI with it.
Agree, setting up rustfmt and then battling other developers about it's settings is not very fun. But having a standard tool with configurable settings that can be stored right in the repository is immensely better than not
“Why” comments are of course included in “we don't need that” category
Well, they claim that statistically the problem became less severe, so maybe it does work