The 'clean code' rules for writing a software engineer resume
Happy Saturday and welcome back to the newsletter! As always, read on for some of the best software engineering insights, opinions, and news, from Triplebyte’s Compiler blog and around the web.
//From Compiler
Applying ‘clean code’ sensibilities to write a performant technical resume
Most software engineers write for a living. That is they sit down at a keyboard and write code. If all goes well, Clean Code, a popular mantra that describes code that's readable, simplistic, and is shaped in logical clarity, is the final product. In many ways, what goes into writing clean code is also useful for crafting an effective technical resume – or the other kind of writing that some engineers may find more foreign or challenging. This blog by Leet Resumes founder Marc Cenedella walks through these parallels one at a time. read() | share(HN) | share(Twitter)
Type erasure in Swift: How to avoid it (and its perils) completely
Ahh Swift protocols and generics. With all their possibilities for meticulously crafted hierarchies, they should be the things of an OCD dreamworld ... but alas. Here is a blog that touches on the limitations of Swift type erasure, and what you can do instead of using them. read() | share(HN) | share(Twitter)
//Around the web
🤔 “Coding is increasingly less about lines of code and more about problem-solving with data.” Here’s a new and insightful blog from freeCodeCamp. It walks through the different things, beyond programming chops, that an engineer needs to make sure they have in skillset in order to stand out in the 2021. One good point in the mix:
Try to be a “product person”. If you can look at the bigger picture and think creatively about making an application appealing, you’re going to be far more valuable than someone who just writes code from day to day.
🖼 Front-of-the-front-end and back-of-the-front-end. Still feeling out your place in the stack? Here’s a piece by web designer Brad Frost explaining that the new reality of front-end work is that it’s really two jobs:
A succinct way I’ve framed the split is that a front-of-the-front-end developer determines the look and feel of a button, while a back-of-the-front-end developer determines what happens when that button is clicked.
Bad news, though, is that both jobs still specialize in JavaScript! Also, I’m personally curious whether being a master of both areas (what Frost considers to be increasingly more rare) make you a full-stack-front-end dev? read()
⌨️ Will Python get faster in the future? “Impossible … but one can dream.” Pablo Galindo, a software engineer at Bloomberg and one of the five members of the Python Steering Council within the Python Software Foundation, gave an interview with VentureBeat this week about his thoughts on the language and where it may go from here. One thing that seems “impossible,” Galindo said, was that the language would ever reach the kind of speed that engineers seek in other modern languages like Go. Some of the reason behind that is the “baggage” the 30-year-old language carries, he said. But improvements to Python are still coming strong, and his biggest wish is that users of the it would be receptive and not so scared of things “breaking” regarding the kind of changes that need to happen to keep the language in tech stacks around the world. Check out the full interview to read all of Galindo’s comments, including a shoutout to the famous/infamous pattern matching feature coming in Python 3.1 later this year. read()
🚀 Your mars + software engineering content of the week.
//Jobs
Some companies hiring engineers on Triplebyte right now:
Check out Triplebyte’s Actively Hiring page to find more companies that are looking for software engineering talent right now!
Triplebyte helps engineers assess and showcase their technical skills and connects them with great opportunities. You can get started here.
If you just happened upon this newsletter, subscribe with the button below to get new editions sent right to your inbox.