else if as an example, Fabio reminds us that we should always try to understand why 'rules' or 'best practices' are the way they are. You might not discover the implicit behavior surrounding your code until you really start asking why things behave the way they do.
A summarized retro on all the interviews taken during a quest to find a new job. Great advice for both those looking to get hired and those doing the hiring.
Do you feel valued by your company? An example of conflict between a developer and employer.
^ that's a direct quote from Batuhan, who is developing his own operating system. The article shares a bit more about what he's building, and the comments tell you why.
Tips on cultivating your problem solving skills!
A thorough guide on how to generate an actionable plan for any web app idea. From defining goals to creating steps to sketching out mind maps.
Why one may think Java is easier to work with than Node, demonstrated with a single page application.
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!