There really aren't any scenarios I can think of that an element would need to have `grid-column` set without being wrapped in another grid, so for that reason it is generally safer to set `grid-column` on all children…
I fall into category 3 which is why I list it. It's not a technical reason so much as a code style reason so it is definitely subject to the opinions of each developer.
3 reasons that I can think of: 1. You can implicitly return things so it provides nice syntactic sugar 2. Using an arrow function results in `this` being bound in the way you'd expect (coming from something like C++) in…
The company isn't paying for your time in the car but it is paying for the space your desk in the office occupies. Would you argue that someone who drives 30 minutes more to the office than an otherwise equivalent…
On one hand, if you are worth $N to the company sitting in an office and produce the same output working from home, that output is still worth >$N to the company. On the other hand, if the company isn't limited by…
I do agree that debugging async JS code is tricky depending on how your calls are structured. However, JavaScript is definitely debuggable. Stepping through minified code is a solved problem thanks to sourcemaps.
There really aren't any scenarios I can think of that an element would need to have `grid-column` set without being wrapped in another grid, so for that reason it is generally safer to set `grid-column` on all children…
I fall into category 3 which is why I list it. It's not a technical reason so much as a code style reason so it is definitely subject to the opinions of each developer.
3 reasons that I can think of: 1. You can implicitly return things so it provides nice syntactic sugar 2. Using an arrow function results in `this` being bound in the way you'd expect (coming from something like C++) in…
The company isn't paying for your time in the car but it is paying for the space your desk in the office occupies. Would you argue that someone who drives 30 minutes more to the office than an otherwise equivalent…
On one hand, if you are worth $N to the company sitting in an office and produce the same output working from home, that output is still worth >$N to the company. On the other hand, if the company isn't limited by…
I do agree that debugging async JS code is tricky depending on how your calls are structured. However, JavaScript is definitely debuggable. Stepping through minified code is a solved problem thanks to sourcemaps.