Grind 169 Leetcode questions
An updated version of Blind 75
Filters:
- View All Questions
- Order by Difficulty
- Group by Topics
# | |
# <Node tree=Array.new([value, left, right]) parent=Node node_index=(1|2)> | |
# | |
class Node < Struct.new(:tree, :parent, :node_index) | |
def value | |
@value ||= tree[0] | |
end | |
def leaf(index) | |
tree[index] ? Node.new(Array(tree[index]), self, index) : nil |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't