The Two Classes of Software Engineer

coffee beans scaled

The post The Two Classes of Software Engineer first appeared on Qvault.

“Software engineer” has become a ubiquitous term for people who write, deploy, architect, or sometimes even simply test code. In reality, I think there are two classes of “software engineers”; those who understand computer science well enough to do challenging, innovative work, and those who just get by because they’re familiar with a few high-level tools. The laziness with which the tech industry has adopted the term “software engineer” has made it harder for us to distinguish between the two.

For the sake of this article, I’m going to refer to those who’ve taken the time to study in-depth as “computer scientists“, and those who skipped the boring stuff to learn how to deploy a React portfolio as “developers“.

I won’t be talking about the differences in job titles among software engineers. If that’s what you’re here for check out this other article on how much money different kinds of engineers make.

It isn’t binary, there’s obviously a spectrum of skill

Before anyone gets too upset, let me acknowledge that the technical skill level of all software engineers could be divided into as many classes as there are engineers in existence. I’m trying to point out that there seems to be a great divide between those who have taken the time to learn algorithms, data structures, and higher maths, and those who took an 8-week crash course in web development.

Stop gatekeeping

i am the gatekeeper 41079851

Sorry, that’s not my intention, and I apologize if I’m doing a poor job of expressing my thoughts.

I think the divide is primarily a result of a simple anecdotal observation I keep making: After engineers find a job they like, they stop learning the hard stuff. Many of us browse Hacker News, a coding-related subreddit, or follow tech topics on Twitter. While better than nothing, there’s a big difference in value between brushing up on algorithms and experimenting with a hot new web framework.

My goal is to articulate the importance of continuing education, even after getting that first great job. It doesn’t matter if you got your start by attending college, going to a boot camp, or taking online courses, you can become a “computer scientist” – there’s no reason to settle as a “developer”.

I also want to point out that I don’t think the distinction between the two classes lies simply in a gap of knowledge. Being a “computer scientist” is more about how you approach and embrace learning and less about what you know today. You’ll never know all there is to know about an industry as massive as the software industry, but the way you go about learning (or not learning) is what will make you successful.

But why? I can make six figures without inverting binary trees

It’s true that both kinds of software engineers earn similar salaries in their early careers (see here and here). In fact, often when people take the university route (I don’t always recommend that these days) to learn CS, they have a hard time finding their first job because they never became familiar with modern tools and technologies. Maybe they didn’t even learn how to use Git. The difference is that “computer scientists” have a really easy time learning React, Django, Rails, you name it. On the other hand, a “developer” will have a seriously hard time figuring out how to scale a moderately complex system if they don’t understand Big O.

Over time, and often as soon as the first year of employment, “computer scientists” tend to move towards more fulfilling and well-compensated work, whether that’s well-funded open-source projects, technical leadership, or mission-critical commercial systems. “Developers” tend to continue doing what they’ve always done, learn a new framework, use an ORM to make simple database queries, or render information in a browser using a tool someone else made.

Demand won’t always be higher than supply

Currently, the number of people needed in software engineering is still rapidly increasing, but (anecdotally, and if anyone has good data on this please let me know) it seems when I talk with entry-level engineers that they’re having an increasingly hard time landing a first job. With greater competition at the junior levels, it seems more and more apparent that “get-rich-quick” paths don’t often produce the best results.

If you’re still struggling to find your first job, are wanting to take your career up a level, or you’re simply looking for more job security, taking the time to learn more advanced and specialized subjects is the best path.

How can I become a “computer scientist”?

“Computer scientists” find ways to learn CS in-depth, whether through conventional means like taking classes at a local university or by taking the initiative to relentlessly self-teach online. “Developers” tend to exist on the surface understanding, preferring to learn specific languages, frameworks, and technologies rather than their underpinnings. “Developers” only pick up new skills when they feel the fads of the time are changing.

If you seek deeper technical fulfillment, don’t settle for writing CRUD applications and API calls. Don’t be afraid to watch lectures on YouTube, take some challenging CS courses, or start a for-fun project that will require more technical prowess than you’re used to. If you’re interested in learning CS online, check out my other post, “A Comprehensive Guide to Learn Computer Science Online“.

If you’re worried about not being able to prove your knowledge if you’re just learning in an unaccredited way online, look into CS certifications.

Thanks For Reading!

If you’re interested in furthering your CS career, take our computer science courses

Follow and hit us up on Twitter @q_vault if you have any questions or comments, and if we’ve made a mistake be sure to let us know so we can get it corrected!

Subscribe to our newsletter for more programming articles



source https://qvault.io/2021/03/05/the-two-classes-of-software-engineer/

Comments

Post a Comment

Popular posts from this blog

Why is Exclusive Or (XOR) Important in Cryptography?

Image
If you are getting into cryptography, or just trying to understand the fundamentals, you may have noticed that the exclusive-or operation is used quite often, especially in ciphers. What is XOR ( ⊕ )? XOR, or “exclusive or” operates on binary data. It returns true if both of its inputs are opposites (one false and one true), otherwise, it returns false. An example in go code would be something like: func exclusiveOr(a bool, b bool) bool { return a != b } XOR Cipher – The Perfect Cipher The XOR operation can be used as a simple cipher for encrypting and decrypting messages with a single key. This is known as symmetric encryption. It is interesting to note that if: The key is the same size as the message The key is kept secret and generated truly randomly Then the cipher is impossible to crack. This is known as a one time pad . However, a simple XOR shouldn’t be used in production due to the key length needing to be too long to be practical. Cipher Example A...
Read more

Base64 vs Base58 Encoding

Image
By Lane Wagner –  @wagslane  on Twitter Base64 is one of the most popular encoding formats for representing data. Have some binary data? Base64 encode it for convenient readability and parsing. Base58 is just another encoding format (with 58 characters instead of 64, and has gained popularity largely due to Bitcoin and other cryptocurrencies. When it comes to data encoding, there is typically a trade-off made between: Human Readability: Do humans have a good idea of what is being represented at a glance? Efficient data compression: How many bytes are used to represent the same data? Let’s rank Base58, Base64, and ASCII encoding against each other using these metrics! First: A Note on Binary All data is stored in a raw binary format on computers. These encoding formats (Base64, Base58, and ASCII) are just different ways of reading and writing binary data. For example, in Base64 the binary code 000000 represents the letter A , but in ASCII the binary 00000000 repres...
Read more

(Very) Basic Intro to Hash Functions (SHA-256, MD-5, etc)

Image
This is going to be a basic introduction to hash functions. I will assume most of my audience is here to gain an understanding of why hash functions are used and the basic idea of why they work. My goal is to explain it in a general sense, I will be omitting proofs and implementation details and instead focusing on the high-level principles. Why Use A Hash Function? Hash functions are used all over the internet in order to securely store passwords, find duplicate records, quickly store and retrieve data, and more. For example,  Qvault  uses hashes to extend master passwords into private encryption keys. A longer list of uses here:  https://en.wikipedia.org/wiki/Hash_function#Uses I want to focus on several important features of hash functions, arguably the most important features. Hash functions scramble data deterministically No matter the input, the output of a hash function always has the same size The original data can not be retrieved from the scrambled d...
Read more