dapperdandev (@dapperdandev) 's Twitter Profile
dapperdandev

@dapperdandev

Angular & TypeScript specialist since 2016 | Writing clean code, solving real problems, and sharing what works.

ID: 1382375519220420611

linkhttps://dapperdan.dev calendar_today14-04-2021 16:49:52

6 Tweet

1 Takipçi

54 Takip Edilen

Minko Gechev (@mgechev) 's Twitter Profile Photo

I see so much misinformation about AI in developer workflows which unfortunately backfires and makes people skeptical. AI tools are real and they are helpful Ignore absolute statements such as LLMs will replace engineers, and instead focus on enhancing your workflows with them.

dapperdandev (@dapperdandev) 's Twitter Profile Photo

The single responsibility principle isn't just for OOP. We often see the quote "a class should have only one reason to change." Another variation states "a class or module should have only one reason to change." I frequently create barrel files in my TS/JS projects to expose

dapperdandev (@dapperdandev) 's Twitter Profile Photo

Principles are often conflated with rules. By definition, principles cannot be broken or violated. They aren't concretions. It’s okay—and often necessary—to write code that doesn’t strictly follow SOLID principles. Focus more on what improves maintainability and readability.