This is a weekly roundup of awesome DEV comments that you may have missed. You are welcome and encouraged to boost posts and comments yourself using the #bestofdev tag.
@xbluelight offered a thorough list in response to Which movies or series about programming would you recommend?:
Comment Not Found
Replying to What conventional wisdom in software is wrong?, @katafrakt points out one principle that can oftentimes be ignored:
That two similar-looking pieces of code must alway be abstracted out, because DRY.
@cristinaruth shares their perspective into What helps build developer confidence?:
- Try something even if it's hard.
- Celebrate that you did it! 🙌
- Remember to celebrate your small wins.
- Be kind to yourself and be your own personal cheerleader, especially through failures.
- Remember to appreciate and thank others so they can appreciate themselves.
@nitya offers some awesome guidance on how to set your team up for effective distributed and asynchronous work in the How does your company deal with massive time zone differences between teammates? thread:
Subscribing to this discussion immediately 😍
As someone who works on a distributed team and is also a remote worker, the challenges are along two fronts:
- How do you make sure information is shared in an inclusive way (localization, respect working hours)
- How do you collaborate when you are not necessarily in compliant time-zones
What I've seen/learned are:
- Ensure that all meetings occur in duplicate - every region should have at least 1 friendly time option
- Record all meetings - folks can catch up if they miss out
- Shared documents - write everything and allow for async comments that everyone can see
- Compromise - take the occasional early morning or late night call so others enjoy regular hours
- Provide enough runway time for decisions - allow everyone to have a chance to watch/read and weigh in (36 hrs at least)
Curious to learn from others.
@evanplaice shares a helpful reply to What is the difference between a Library vs A Framework?:
A library augments code. Ie it adds capabilities.
A frameworks provides the foundation of all your code.
If a library breaks, parts of your codebase may break but the overall codebase will likely still function.
If a framework breaks, nothing will work.
Changing a libraries is low-impact. Changing a framework usually requires a full rewrite.
See you next week for more great comments ✌
Top comments (4)
Congrats to @xbluelight , @katafrakt , @cristinaruth , @nitya , and @evanplaice for making the list this week!
Oh wow - thanks @peter - this has made my day! ❤️
Thanks! I'm really glad it was that comment
I know how frustrating it can be to try to get a grasp on a topic and everything written/said about it is conflicting. It's not much but I hope it provides some clarity for others.
Kudos Peter