Joseph Petersen

When evaluating engineers: Soft skills > Coding skills. In software engineering, we often get caught up in the technicalities - the languages, the algorithms, the data structures. But is that all there is to it? Let's take a step back and look at the bigger picture. What is the ultimate goal of software engineering? It's about creating value for customers, using technology as a tool. When hiring software engineers, it's easy to get swayed by impressive tech skills. But I urge you to first look for a product mindset. This is someone who understands that their role is not just to write code but to solve problems and create value. Next, look for creativity. In a field that's constantly evolving, the ability to think outside the box is invaluable. Enthusiasm is another critical trait. A passionate engineer will not only do their job but also do it with enthusiasm, constantly striving to improve and innovate and spread the energy to the rest of the team. Tech skills? Yes, they're important. But they can be learned and honed over time. Remember, we're not just building software. We're building solutions. We're building value. And to do that, we need more than just coders. We need problem solvers, innovators, and passionate creators. So, the next time you hire a software engineer, look beyond the code. Look for someone who can bring value to your product and customers. What do you think? I'd love to hear your thoughts and experiences. #softwareengineering #hiring

53

3 Kommentarer

I don't want to be impressed by your code. Ever. I want to understand your code. Always. Clever code is confusing. Impressive code is unnecessary. Engineers who flex often later forget. If you really want to impress me and my team, here is how to do it: - write descriptive variable names - write descriptive function names - make them long, when necessary - break your code into multiple lines - make your code describe itself like a book I like my code to read like a novel, even if that means it's longer. I like confusing code to clarify itself by using variables to explain how it works in parts, one bit at a time. No more confusing logic. No more out-of-date comments. No more head scratching 6 months later. Now that is impressive code.

33

7 Kommentarer

Over the past few months I’ve written an extensive tutorial on how to build software applications with Node.js and React. I’m sorry to tell you that this experience didn’t teach me anything about B2B sales, though. But hopefully, it’s still useful for some people out there. From the introduction: The approach of this tutorial is to teach its readers how to build a fully working software application from zero to production. This means two things: 1. You are not required to have done any kind of software development before getting started with this tutorial. It will introduce and explain everything that is needed to build applications in full detail, assuming no prior knowledge or experience. This is the “from zero” part. 2. Building on the foundational knowledge it teaches in the first half, the tutorial will then, step by step, guide you through the process of building a real, full-fledged, and completely working software application, again explaining every detail along the way, and shows how to “deploy” that application — that is, how to make that application available on the Internet for anyone to use. This is the “to production” part. Speaking of B2B sales: I’m afraid you cannot buy this tutorial. That’s because I’m making it available for free, as a series of posts on my blog. The first three parts are already published: https://lnkd.in/e2XCYm3p https://lnkd.in/eW7wUc_d https://lnkd.in/eAU6kgH9 No, you do not need to sign up to my newsletter to get access to the tutorial. That’s mainly because I don’t have a newsletter. Also, no need to follow me (although admittedly, it might help to get you notified whenever I’m publishing a new chapter). Furthermore, please don’t be disappointed if clicking on the tutorial links won’t present you with a cookie banner. That’s because my blog doesn’t use any cookies. No, not even those from Google Analytics, as I’m not using that either. This means I will have no idea how many people will read the tutorial — which makes sense because let’s face it, who is going to consume this kind of long-form, deep-dive technical content nowadays anyway. And in text-only form, of all things! Should you nevertheless decide to dive into the text, expect to learn how to program using JavaScript and TypeScript, how to use these languages to build rock-stable backend applications with Node.js as well as elegant frontend applications with React and Redux, and finally, how publish a complete and integrated software solution on Amazon AWS. Ok, that’s it. If you want to access the bonus chapters, simply subscribe to… — just kidding. There are no bonus chapters. Everything you need to learn to build useful software products is right in the… normal chapters, I guess? Happy reading!

30

1 Kommentar

Six months have passed since the extensive rollout of GitHub Copilot to Volvo Cars' developer community.​ "We expected significant efficiency gains of approximately 20%, but tasks like unit testing have surpassed expectations and seen gains of up to 40%", says product developer Sabina Edenlund, who sits on Volvo Cars' Gen AI committee.​ GitHub Copilot assists developers with testing, explaining, and generating code, and can support the advanced ‘autocompletion’ of coding. ​ ​ ➡ Learn more how Volvo Cars benefited from GitHub Copilot: https://lnkd.in/dPfGruTq #GitHubCopilot #DeveloperProductivity #MicrosoftAzure

1