Every Monday we round up some of the last week's top posts, comments, and tweets. If you have any feedback, please leave a comment. â¤ï¸
Almost any programmer will tell you that the best way to improve your skills while also creating something you can demonstrate to potential employers is to focus on some side projects. But first you need to have a side project, so Sam Jarman lists a few ways to rev up your imagination:
One of his suggestions–finding ways to automate personal tasks–was well received:
Yes. Automating is good. Making thing more searchable is good, too. As for me I think the nice idea it is to make things more searchable indexing in Elasticsearch? For instance by consuming RSS feeds..
"One of the best things about Node.js is its massive module ecosystem," writes Dominik Kundel. So what did that motivate him to build? A module that reads the emojis from a string input and returns their shortcodes. Watch how he does it:
It feels like every week there's a top dev.to post about Go. This week, it's Francis Sunday showing us how to build a RESTful API in the language:
There are so many languages, libraries, frameworks, etc. out there that it's difficult (and daunting) to try to figure out exactly what you need to know to be a sufficiently prepared full stack developer. Sam Jarman (who cracked this week's roundup twice!), runs down his list:
SOLID principles were introduced a few decades ago by Robert C. Martin as standard for maintainable and flexible software design, and today they're still a quite useful set of guidelines. Theofanis Despoudis walks us through the five core ideas:
Chris Dodds is tired of seeing only success stories about DevOps–"tales of bold IT leaders transforming their business and steering big corporate ships into the future," as he puts it–so he wrote up some "dirty secrets" about the DevOps failures you see fewer stories about:
There's so much praise for flexible work environments and working from home, that it can be easy to look past some of the pitfalls of such a set-up. Charles Villard, who works remotely himself, explains some of the dangers of WFH:
That's it for our weekly wrapup! 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!