Every Tuesday we round up the previous week's top posts based on traffic, engagement, and a hint of editorial curation. The typical week starts on Monday and ends on Sunday, but don't worry, we take into account posts that are published later in the week. ❤️
A well-curated list of resources can be a powerful tool when it comes to your developer education. Thanks to @adiatiayu for putting this thoughtful collection together!
@carstenbehrens was having a hard time finding the perspective of a German self-taught developer — so they wrote one!
Great work on this Jenkins primer, @mariehposa ! If you’re looking for more info on the what, when, and why of Jenkins, look no further!
In this article, @allenheltondev shares the 5 different types of diagrams you should make depending on 5 different audiences. Super fascinating and interesting.
As @sanspanic says, outwardly inaccessible words can be demystified pretty easily. That’s exactly what this post seeks to do with pure vs impure functions.
“[When it comes to documentation] your first step is to admit to pretty much anyone and everyone, including yourself, that this is hard.”
Great read on an important topic 👀
@anuradha9712 explains that both debouncing and throttling are meant for performance optimization -- and the answer about which to use depends on the context. Take a look!
That's it for our weekly wrap up! Keep an eye on dev.to this week for daily content and discussions...and if you miss anything, we'll be sure to recap it next Monday!