|
Hey Pythonista,
What is the last piece of feedback you got on a Pull Request?
For most developers, it’s usually:
-
Silence.
-
Nitpicking about variable names or PEP8 formatting.
-
The dreaded..."LGTM" (Looks Good To Me).
"Looks Good To Me" is the worst. It's a career killer.
It feels good in the moment because you get to merge the changes and close the Issue, but often it means you learned absolutely nothing. In short, you're operating in an echo chamber and reinforcing your own bad habits.
I was looking at a list of "Essential Code Review Tips" on we put together a little while ago, and it reminded me that most developers have to beg for this kind of feedback at work.
In the PDM program, we don't treat code reviews as a box-ticking exercise. We treat them as one of the primary vehicles for your growth.
Here's the difference between a standard workplace Code Review and a PDM review:
-
We focus on Architecture, not just Syntax: Most peers just check if the code runs. We look at design. Is this scalable? Is it decoupled? We force you to think about the broader context of the system, not just the 10 lines you changed.
-
We teach you to detach Ego from Code: The source of most imposter syndrome is thinking that a critique of your code is a critique of you. We train you to view feedback as data and not an insult.
-
We refuse to let you hide: "Keep PRs small" is a common tip, but in PDM it’s a rule. We force you to break complex problems down into shippable chunks. No massive commits, which means no hiding messy logic in 1,000-line updates.
Reminder: You can't become a Senior Developer in a vacuum. You need a Senior Engineer looking over your shoulder, challenging your logic, and showing you the "why," not just the "how."
If you are tired of "LGTM" and want real, architectural feedback that pushes you to the next level, we need to talk.
Book your strategy call here and let’s talk about your code:
https://calendly.com/pybites/coaching
Julian + Bob
|
