Posts

Showing posts with the label Programmers

SOFTWARE ENGINEER VS. PROGRAMMER: WHAT’S THE DIFFERENCE?

Image
While the tech unemployment rate rests at  1.3% , recruiters are scrambling to find, hire and retain strong candidates. In order to bring in the right people, you need to know who you’re looking for first. The  demand for software engineers  is on the rise, but the role is often conflated with programmer and developer positions. While it’s ultimately up to the employer’s discretion on how to title open roles, tech recruiters should understand some of the commonly discussed differences. In this article, we’ll distinguish software engineers from programmers and highlight six key differences between these roles. Use this resource to  recruit smarter  and source better tech candidates. Table of Contents What Is a Software Engineer? What Is a Programmer? What Is the Difference Between a Software Engineer and Programmer? WHAT IS A SOFTWARE ENGINEER? A software engineer is often called a developer, but IT professionals and  tech recruiters  know there is a  difference b

Clean code, dirty code, human code

Image
Last week, Dan Abramov posted a very personal and humbling blog post entitled  Goodbye, Clean Code . I saw a tweet about this in my timeline and, being a long-term proponent of “clean” code, TDD and things of that ilk, I was naturally concerned. Here’s what I replied with. Daniel Irvine @d_ir @dan_abramov  You’re conflating two separate things. One is the desire to write clear, well-structured code. Another is your belief that your code is more valuable than that of your colleagues. I fear you’re missing the more important lesson. Human code > clean code > clever code > dirty code 15:00 PM - 12 Jan 2020    1   25 I dislike Twitter because it’s so hard to find any nuance to arguments. So in this post I’ll explain what I mean by  human code . It’s easier to blame code than it is ourselves I think it’s wonderful that Dan is blogging about deeply personal experiences in his career. Many programmers who become team leads will have had a similar experien

Why Companies don't recruit Junior develpopers

Image
  I hate to spill the beans so early but companies  do  hire “junior” developers or as I’d like to call it early career developers. The only catch is that companies are playing the classic game of playing hard to get. That is unless you’re some kind of a super genius unicorn programmer. But for most of us early career devs we rely heavily on internships, referrals, and noteworthy projects to get us a real shot with a company. Otherwise, if we went to a mass job board and tried to “cold apply” to a job posting we’d be eaten up by resume algorithms before a recruiter even has a moment to give us their notorious 1–3 second glance. So if companies are playing hard to get then what’s a newbie developer to do? Well, like I just said internships, referrals, and project collaborations are key. In addition to that going to local meetups, signing up for hackathons either online or in-person and actually talking to your LinkedIn contacts helps. If you really want to step it up a notch you

What do software developers, programmers or coders do after coding the whole day

Honestly, in the past I would have told you I spend hours every night learning new technologies and frameworks while pouring hundreds of hours into pet projects I never finished…. However, today, I’d tell you this: What I do that helps me be a better developer, is I leave it (to the best of my ability) at work. I focus on my well being. I focus on getting enough sleep. I focus on eating well. I focus on exercising. Most importantly, I focus on enjoying the life I am working for. I make sure I have hobbies I love. I focus on my relationships, and family building. Maintaining mental health is critical to being a successful developer. You can’t code well on 3 hours of sleep and 4 red bulls forever. You can’t write a good web api when you’re thinking about your wife asking for a divorce because you are always on the computer. For me, it’s absolutely critical that I take care of my life so that I may have a clear conscience to focus on my work. I constantly remind myself, I work

Duties of a software developer

Image
What Software Developers Do Software developers are the creative minds behind computer programs. Some develop the applications that allow people to do specific tasks on a computer or another device. Others develop the underlying systems that run the devices or that control networks. Duties Software developers typically do the following: Analyze users’ needs and then design, test, and develop software to meet those needs Recommend software upgrades for customers’ existing programs and systems Design each piece of an application or system and plan how the pieces will work together Create a variety of models and diagrams (such as flowcharts) that show programmers the software code needed for an application Ensure that a program continues to function normally through software maintenance and testing Document every aspect of an application or system as a reference for future maintenance and upgrades Collaborate with other computer specialists to create optimum s

The Difference Between a Programmer, Developer, and a Hacker

Image
There is often  spirited discussion and debate  about the differences between Programmers, Hackers, and Developers. Most descriptions I’ve seen are flawed in at least one serious way, so I wanted to assemble my own—hopefully more accurate—definitions. A  Programmer  is someone who can solve problems by by manipulating computer code. They can have a wide range of skill levels—from just being “ok” with basic scripting to being an absolute sorcerer with any language. A  Hacker  is someone who makes things. In this context, it’s someone who makes things by programming computers. This is the original, and purest definition of the term, i.e., that you have an idea and you “hack” something together to make it work. It also applies to people who modify things to significantly change their functionality, but less so. A  Developer  is a formally trained programmer. They don’t just solve problems or create things, but do so in accordance with a set of design and implementation principles