This book explores techniques for crafting clean JavaScript code, covering the basics of JavaScript, modern syntax, design patterns, and best practices for maintaining code quality. It delves into real-world examples and discusses the four tenets of clean code: reliability, efficiency, maintainability, and usability.
The Pragmatic Programmer is a book that centers on how to use software to solve problems effectively and how to grow as a developer pragmatically. It was first published in 1999 and a 20th Anniversary Edition was released in 2019. The book emphasizes key qualities such as being an early adopter, having fast adaptation, inquisitiveness, critical thinking, realism, and being a jack-of-all-trades. It uses analogies and short stories to present development methodologies and caveats, including concepts like DRY (Don't Repeat Yourself), YAGNI (You Aren't Gonna Need It), and rubber duck debugging. The book covers topics such as writing clean code, estimating software delivery, instituting change, combating stagnancy, and making software processes resilient and efficient through automation and testing.
It’s another potluck! In this episode, Scott and Wes answer your questions about MDX, portfolio projects for junior devs, code commenting, CSS property order, and more!
Sanity - Sponsor
Sanity.io is a real-time headless CMS with a fully customizable Content Studio built in React. Get a Sanity powered site up and running in minutes at sanity.io/create. Get an awesome supercharged free developer plan on sanity.io/syntax.
Netlify - Sponsor
Netlify is the best way to deploy and host a front-end website. All the features developers need right out of the box: Global CDN, Continuous Deployment, one click HTTPS and more. Hit up netlify.com/syntax for more info.
Show Notes
02:18 - I’m curious to know what you guys think of MDX. I’d love to learn more about pros and cons, if you guys had a chance to use it.
08:49 - Where would you put business logic in Vue.js middle- or large-scale applications? I try to put business logic in store but it makes hard to maintain such store, even with splitting to actions/getters/mutations files. I ended up using vanilla JavaScript files, where each file is a class singleton. I was wondering: is it a good solution or do you have better alternatives in mind?
12:07 - I commonly find myself engineering complex programs and left flabbergasted on how to express these ideas to other people when the need arises that I need to explain them and remember why I did them a certain way. How can I get better at conceptualizing intricate design patterns or functions as well as have better memory recall for these abstractions?
18:02 - Can I get recommendations for a junior dev portfolio? What five projects you would recommend to build that will significantly help in getting a job as a front-end web dev and why?
21:13 - I am now working on building a minesweeper game with React. You know how on a computer you right click to flag and disable a cell? I am thinking of doing a press and hold on a mobile device instead. I am not sure how to do either (the right click logic or the press and hold). How can you listen for these events in React? Can you help with some guidance or resources? :)
30:00 - What are your thoughts on SailsJS as a Rails-equivalent framework in Javascript? They recently released version 1.0 and I’m wondering if I should start using it in projects or if I should wait to see if it pans out.
34:35 - How do you go about creating reusable React components (reusable from project to project)? Do you create packages and publish them to NPM? Or do you have another method for storing code for components that you will likely need to use again?
38:33 - Thoughts on shadow dom / custom elements? Would you use them in your own projects?
40:49 - How do you organize CSS properties within a rule and why? Random, alphabetical, logical groupings, etc.
46:04 - Have u ever used the 2nd parameter of JSON.stringify for anything useful?
48:00 - Getting my first dev job at an actual software company a year ago opened my eyes to the vast difference between educational repos and the absolute jungle that can be enterprise code bases. I’ve also learned the importance of writing code that will be readable later - ensuring any hacky workaround is replaced with a pattern seen elsewhere in the code base, etc. My question is - are there resources on these sorts of topics for folks trying to break into the industry? A lot of tech topics revolve around how to get your code to run, which feels to me like only half the battle. Where can juniors find resources on robustness?
Links
××× SIIIIICK ××× PIIIICKS ×××
Shameless Plugs
- Scott: All Courses - Sign up for the year and save 25%!
- Wes: All Courses - Use the coupon code ‘Syntax’ for $10 off!
Tweet us your tasty treats!
Syntax - Tasty Web Development Treats 
