Chapter 1: Understanding Your Programming Portfolio

What should you emphasize in your programming portfolio?

While I can’t quantify the exact number of lines I've coded over twenty-five years, it's certainly well over a million. And while Python is part of my toolkit, it represents a mere fraction of my output. I often rely on having documentation at hand before releasing any software. However, if I start with well-defined specifications, I believe I can produce the required code, provided I feel motivated to do so. Motivation plays a critical role in this field.

A proficient Python developer doesn't necessarily have to be a master at programming as a whole. Everyone has their strengths, and it's unrealistic to excel in every area. However, if you're capable of tackling both the backend and frontend aspects, and if you can seamlessly integrate various technologies through APIs, you’re already ahead.

Ultimately, while it’s challenging to be proficient in all aspects of programming, being resourceful and quickly finding the information needed to write effective code can be advantageous. Yet, in a job interview setting, simply reciting theoretical knowledge without concrete examples of your accomplishments won't leave a strong impression.

Many recruitment agencies conduct preliminary assessments, where candidates are tasked with coding a portion of a program from scratch. This approach raises questions about its effectiveness. After all, writing code on a different machine under time constraints can be daunting.

To truly gauge a programmer's abilities, spending time with them while they tackle real-world programming challenges is essential. For instance, if I were to present my resume from a programming perspective, mentioning over a million lines of code across thirteen languages doesn't convey much.

While I can proudly state my significant contributions to the development of a silicon compiler, this information may not resonate with recruiters or hiring managers. Therefore, when crafting a resume, it’s better to remain somewhat vague yet honest about your proficiencies, such as mentioning your familiarity with Python in areas like network applications or graphical interfaces, without quantifying years of experience or lines of code.

The number of years in the industry or code lines produced doesn't reflect the quality of work. I recall the outdated practice from the 80s of asking, "How many lines of Fortran can you produce per hour?" This metric is not a true indicator of programming talent.

Instead, it's more valuable to articulate what you can create at a conceptual level or in terms of user experience. This is particularly relevant in the realm of Python, where many individuals mistakenly consider themselves proficient just because they can seek help from forums. While this isn't inherently negative, it doesn't necessarily equate to being an exceptional programmer.

If I were to assess someone’s programming skills, I would first explore their understanding of Assembly language. This is just a playful jab, but understanding the fundamentals of programming is crucial for optimization. However, we must also consider a candidate's grasp of object-oriented programming (OOP).

Can they adapt to both OOP and low-level optimization? This can be a challenge for many competent programmers. If we ask a candidate to write a function that opens a socket for a network session in C, it may serve as a test, but it doesn't genuinely showcase their skills.

In recent years, I have shifted my evaluation approach. Instead of focusing on specific languages or functions, I ask candidates to address architectural or organizational questions related to software development. For instance, I might ask, "How would you design an application to help users navigate to their appointments via geolocation, incorporating an A* pathfinding algorithm?"

This type of inquiry reveals whether the candidate can initiate programming and likely requires proficiency in at least three different languages to succeed. Therefore, this should be highlighted on a resume to effectively demonstrate that achieving such tasks is not trivial.

Yet, given the often significant discrepancies between what resumes claim and actual skill levels, it's essential to approach the reality of one's capabilities with humility.