"Name your variables properly, *fool*", the programmer scoffs.
"Nobody will know that `t` is the time elapsed. The name should be descriptive" they mutter through gritted teeth as they block the PR.
A moment of pause. They exhale briskly through their nostrils and the rage subsides.
Composure regained, the programmer returns to their component building. Here is where the real work is happening
`class="ml-5 mr-2.5 px-6 py-3"`
@Robb The component probably looks like this
```
const SubscribeHeading = ({ channel} ) =>
<div class="ml=5 mr-2.5 px-6 py-3">Subscribe to {channel}</div>
```
There is already a perfect name for the component, having a redundant `class="subscribe-heading"` won't be much helpful right? 🙈
@oxalorg Utilities definitely have their place, but I'm not sure a class name would be redundant. If I needed to tweak the SubscribeHeading component – for example, if it was nested inside a masthead – then direct access through the cascade with `.masthead .subscribe-heading` could be handy.
I'd probably swap that div out for a semantic heading element though. The JSX component name isn't going to appear in the browser and the markup doesn't suggest that this component is actually a heading
Robb
Mitesh Shah