Issue 10

Today’s Issue: Why developers should learn design and how you should be learning new concepts.

Welcome to #10.

First Up - Should Developers Learn Design

As a software developer working on a team, you’ll likely interface with designers at some point or another in your career. Learning to understand design—whether it be UI, UX, or another aspect—will not only make you a more well-rounded developer but also help bridge gaps between these two disciplines.

By understanding design principles, you'll be better equipped to implement designs that are not only visually appealing but also user-friendly and intuitive. This knowledge can help you provide valuable input during the design process, identify potential issues, and collaborate more effectively with designers. Additionally, learning design can expand your skill set and make you a more versatile and valuable member of the development team.

Additionally, having a design-oriented mindset helps you make thoughtful decisions when crafting user interfaces and experiences. This can result in better-designed applications that are intuitive and enjoyable for users. Ultimately, understanding design principles allows you to contribute meaningfully across the entire software development lifecycle—from ideation through to implementation.

Second Topic - How You Should be Learning

As someone who’s been new to the field, I remember how challenging it was to learn to code. From wrestling with complex topics to figuring out how new concepts connected with everything I’d learned before—it was tough. One mistake I made (and I know many of you are making too) still stands out: falling into tutorial hell.

Sure, tutorials are a helpful resource, but if all you do is watch them, you won’t actually retain much. You’ll forget what you spent hours watching, and the concepts will go in one ear and out the other. Don’t believe me? Try this: Watch a tutorial, don’t take any action, and then attempt to implement what you learned a week later. Chances are, it’ll feel like starting from scratch.

It’s easy to watch something—just like bingeing Netflix (trust me, I get it)—but the hard part is taking action. And that’s the part that matters most.

The best way to learn is by building projects and applying what you’re learning in real-time. Use your new skills to create something you wish existed or rebuild an app you already use. What’s important is that you take action—this applies not only to software development but to life in general. For the purpose of this newsletter, though, we’ll keep it tech-focused.

So go out and build something!

Interesting Plugs

• Remix released the prerelease of React Router v7

• React on the Server is better than PHP

• How does React render? Check it out here

Job Board

• Front End Developer - React with SensorTower

  • Salary: $115,000 - $145,000

  • Experience: Good experience with React and TypeScript with some bonus points if you’ve used testing frameworks like Jest and Cypress

• Software Developer with Euna Solutions

  • Salary: Just says competitive

  • Experience: 2+ years as a software developer

  • Tech Stack: JavaScript, TypeScript, C#, AWS, SQL

Till Next Time

I hope everyone enjoys this post. If you take anything away from it, it’s to stay out of tutorial hell and take action! Also, I know some of you have asked for more junior-level positions to be posted, but since this newsletter is really global with the majority of my readers being spread out across the US, I try and only post remote roles which usually require a few years.

If you're a junior developer looking to get your first role, reach out to me as I offer mentorship!

Have a great weekend and as always, happy coding!