Michael TharringtonThis weekly roundup highlights what we believe to be the most thoughtful and/or interesting discussion of the week. We're also be highlighting one particularly cool comment in each installment. 🙌
The DEV Community is particularly special because of the kind and thoughtful discussions happening between community members. As such, we want to encourage folks to participate in discussions and reward those who are initiating or taking part in conversations across the community. After all, a community is made possible by the people interacting inside it.
Discussion of the Week
For this week's discussion, I'd like to put the spotlight on @adrvnc's "Open Discussion: What Tips Do You Have For Writing Clean Code?" as it spurred some really thoughtful and friendly debate between folks.
It's cool to hear differing opinions on what constitutes clean code and the different routes or rules folks follow when trying to craft clean code themselves.
Hopefully, there's a bit of helpful advice for everyone in this discussion. And hey, never too late to drop your thoughts if you have your own perspective on clean code to share!
Comment of the Week
Comment of the week goes to @kspeakman for this brilliant and concise bit of advice to the prompt "What misconceptions do early-career devs have about this work?" that @ben kicked off:
I can imagine that early days it'd be easy to get hyper-focused on the technical bits and lose sight of the actual problem you're solving. I appreciated how Kasey crafted this explanation and spoke from personal experience, openly sharing that this is something that has tripped them up in the past. Always nice to hear advice that is empathetic and understanding, yet pointed and practical.
What are your picks?
There's loads of great discussions and comments floating about in this community. I urge you all to share your favorite comment and/or discussion of the past week below in the comments. And if you're up for it, give the author an @mention — it'll probably make 'em feel good. 💚
That it's all about the technical details. They are important, but getting the details perfect won't matter if the business problem is misunderstood. You'll build a solution to a problem they don't have and create new problems. I did that more than once in my career.
I good indicator that there is a misunderstanding is when you get into a coding conundrum. Meaning you had to solve a technical problem that doesn't make sense to you. It kinda gives you a weird feeling like something is missing. Learn to listen to that and ask questions until you figure out what's missing.