dapperdandev

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

[dapperdandev @dapperdandev]

@cagataycivici You could have given us a warning. Instead, you pulled the rug out from under us, released v22, and immediately stranded us on v21 until our companies can approve the expense. I wish you had announced told us at the beginning of a release instead of the end.

[dapperdandev @dapperdandev]

I wish you had done a better job communicating primeng would no longer be open source when v22 landed. Those of us without licenses are immediately stuck on an unsupported version until we pay. Many of us work at companies that have a lengthy approval process for licenses. We understand the need to move away from os. We don't understand the abruptness.

[dapperdandev @dapperdandev]

@wesbos For me, having to use the CLI is a minor inconvenience for the consistently better results Claude Code currently produces.

[dapperdandev @dapperdandev]

@Armandotrue I use this same strategy for roles and feature flags to determine if content is shown. Good stuff.

[dapperdandev @dapperdandev]

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.

[dapperdandev @dapperdandev]

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 modules. Oftentimes, there isn't a class in sight. Just beautiful, OOP-less functions.

[Minko Gechev @mgechev]

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]

@DeborahKurata Looking forward to upskilling. You always find the nooks and crannies where I have knowledge gaps.