Famously used in popular UI library shadcn/ui, This probably the most efficient way to write tailwind classes

Simplicity is hard to sell. It’s not sexy; it’s boring; it’s predictable. Everyone says they want to keep it simple, but their ego won’t let them. They have to be sophisticated.

The unwritten rules of engineering are the hidden insights that are not taught in school or in books. Here are the things I wish I knew.

Tech debt should not be seen as burden, we only lack the context to understand the tradeoffs we made

10x developer lone wolf is overrated, it's not about being the best developer, it's about being the developer who makes everyone better.

Husky is a convenience, it meant to give developers faster feedback loop - formatting, linting and even commit message checks. But somewhere along the way, the projects grows and we start piling up with full type checks, tests or even build because "we have to catch the issue early".

Separation of Concerns is commonly misunderstood as just splitting code into files. It’s really about defining clear responsibilities in your system. We’ll also touch on how coupling and cohesion play a role