AWS Builder Center
Looking Good Before Being Good

Looking Good Before Being Good

In software engineering, your profile can grow faster than your skills. This is about living with that gap—and studying until you eventually catch up.

In software engineering, people often see your work before they see you work.
They see your GitHub profile, résumé, open source contributions, and whatever projects you decided were worth pinning. As a student, that matters a lot. There is no long career behind your name yet. A recruiter or engineer has to judge you from the small amount of evidence you can give them.
So you make that evidence look good. You clean up repositories. You learn how to write documentation that someone else can actually follow. You contribute to projects you respect. Eventually, your profile starts looking like the profile of an engineer.
Then you close GitHub and get stuck on a Python loop for forty minutes.
You know exactly how much you still don't know.

The gap

That part is humbling.
You can have pull requests merged into serious open source projects and still struggle with a LeetCode Easy. You can know enough Git to work comfortably across branches, resolve conflicts, review diffs, and contribute to a large codebase, then forget how to implement something you learned in a data structures class.
It creates a strange gap between how you look from the outside and how competent you feel when the editor is open.
I used to think that gap meant I was doing something wrong. Maybe I should stop worrying about GitHub and go study until I was "good enough" to deserve the profile.
But I don't think there is a point where that happens.
There is too much to learn. Algorithms, data structures, operating systems, databases, networking, debugging. Then there are the things you only learn after working with other people's code for long enough. None of it arrives at once.
There is no commit that changes your status from beginner to engineer.

In the meantime, you study

So I have become more comfortable with a simple idea.
In the meantime, you study.
Take the opportunities your current work gives you. Keep the nice GitHub profile. Be proud of the pull requests you managed to get merged. Put the project on your résumé if you built something worth showing.
Then go back to the basics.
Solve the stupidly simple problem that somehow took you an hour. Read the code you barely understand. Search the concept you are slightly embarrassed to have forgotten. Break something. Figure out why. Come back tomorrow and do it again.
For a while, your GitHub profile might be ahead of the engineer behind it.
That's fine.
Keep studying long enough, and eventually you will open that profile and realize something:
You caught up.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article