Skip to main content

Sorry, Conceptual Fluency Won't Land You a Job

I saw a recent post where a software engineer/programming influencer was encouraging:

If you know how to work with C#, you can learn Java.
If you know how to work with JavaScript, you can learn TypeScript.
If you know how to work with GitHub Actions, you can learn Jenkins.
If you know how to work with SQL, you can learn SparkSQL.
If you know how to work with Angular, you can learn React.
If you know how to work with Databricks, you can learn Snowflake.
If you know how to work with Event Hubs, you can learn Kafka.
If you know how to work with Bicep, you can learn Terraform.
It's not the tools that are important, it's the concepts.

Kudos for speaking the truth. With 20 years of experience in software engineering myself, I whole heartedly agree with her post. But sadly, the market doesn’t value conceptual fluency.

From a job search perspective, conceptual fluency presumes you're networking and already in contact with the hiring manager, they like you, and they are willing to give some "wiggle room" on requirements. There are many candidates who don’t have that luxury. They're stuck looking for work on slop job boards, and when applying in this manner, the ATS that helps the overworked recruiter is configured to match Java, not C#*. Applicants applying cold through job boards or recruiters aren’t evaluated as thinkers, they’re filtered as product.

As the market continues implodes, we're also left with many unemployed, extremely qualified engineers. Employers seem more inclined nowadays to wade through the hundreds of applicants to find the unicorn that matches their reqs than to the dedicate time and resources to train. They also don't intend to keep the engineer around for very long, for example using forced attrition to save on benefits and lower salaries. There's no loyalty and thus no incentive for training.

Fun fact: I once had a hiring manager explicitly say candidates should "learn on their own time" (I withdrew my application).

What's also interesting to think about is the impact that AI coding assistants are having. Most tech stacks are common enough where engineers can use these on a daily basis for their professional work. They don't have to be proficient in React because an LLM will spit out code for them. Critical thinking is still required to solve bugs, but the day to day proficiency is less important now. At least thats what the marketing hype is leading us to believe. I don't see many jobs listings that show the employers have adjusted their mindset to reflect the new reality they're trying to bring about. There should be no distinction between a C# or Java or PHP programmer... it should be just "experienced programmer".

I guess that makes me feel a little better about the decline of Stack Overflow and what it means for the language rankings that reference the site.

Oh, and what does it mean for things like coding interviews? :-D

* Except when it doesn't... but even then it does... because it doesn't.... but sometimes.... depends on who you ask

Comments

Popular posts from this blog

Writing a Minimal PSR-0 Autoloader

An excellent overview of autoloading in PHP and the PSR-0 standard was written by Hari K T over at PHPMaster.com , and it's definitely worth the read. But maybe you don't like some of the bloated, heavier autoloader offerings provided by various PHP frameworks, or maybe you just like to roll your own solutions. Is it possible to roll your own minimal loader and still be compliant? First, let's look at what PSR-0 mandates, taken directly from the standards document on GitHub : A fully-qualified namespace and class must have the following structure \<Vendor Name>\(<Namespace>\)*<Class Name> Each namespace must have a top-level namespace ("Vendor Name"). Each namespace can have as many sub-namespaces as it wishes. Each namespace separator is converted to a DIRECTORY_SEPARATOR when loading from the file system. Each "_" character in the CLASS NAME is converted to a DIRECTORY_SEPARATOR . The "_" character has no special ...

Safely Identify Dependencies for Chrooting

The most difficult part of setting up a chroot environment is identifying dependencies for the programs you want to copy to the jail. For example, to make cp available, not only do you need to copy its binary from /bin and any shared libraries it depends on, but the dependencies can have their own dependencies too that need to be copied. The internet suggests using ldd to list a binary’s dependencies, but that has its own problems. The man page for ldd warns not to use the script for untrusted programs because it works by setting a special environment variable and then executes the program. What’s a security-conscious systems administrator to do? The ldd man page recommends objdump as a safe alternative. objdump outputs information about an object file, including what shared libraries it links against. It doesn’t identify the dependencies’ dependencies, but it’s still a good start because it doesn’t try to execute the target file. We can overcome the dependencies of depende...

What's Wrong with OOP

Proponents of Object Oriented Programming feel the paradigm yields code that is better organized, easier to understand and maintain, and reusable. They view procedural programming code as unwieldy spaghetti and embrace OO-centric design patterns as the "right way" to do things. They argue objects are easier to grasp because they model how we view the world. If the popularity of languages like Java and C# is any indication, they may be right. But after almost 20 years of OOP in the mainstream, there's still a large portion of programmers who resist it. If objects truly model the way people think of things in the real world, then why do people have a hard time understanding and working in OOP? I suspect the problem might be the focus on objects instead of actions. If I may quote from Steve Yegge's Execution in the Kingdom of Nouns : Verbs in Javaland are responsible for all the work, but as they are held in contempt by all, no Verb is ever permitted to wander about ...