What part of your developer growth is basically invisible?
Posted by alkeshjethva@reddit | learnprogramming | View on Reddit | 4 comments
I noticed something.
People can see resumes.
People can see projects.
People can see GitHub profiles.
But a lot of things seem hidden:
- bugs that took days to figure out
- architecture decisions
- mistakes that changed how you think
- tradeoffs you learned from
- random things that finally clicked
If someone looked at your profile today, what part of your actual growth would they completely miss?
JGhostThing@reddit
Things are only invisible if you don't bring them up. You have two main places to bring them up in writing: your cover letter and your resume. The cover letter is slightly less formal than the resume. I would put important projects in the resume.
Jazzygogo@reddit
Well if you are using the project for a portfolio, you could document your journey in a markdown file. There you could write what you got stuck on, how you solved it, why you made a certain decision over another etc. That would strengthen the project as a portfolio.
owp4dd1w5a0a@reddit
This. I keep a BUILDLOG.md, a DECISIONLOG.md, and a CHANGELOG.md in my personal projects for this reason.
pastordiddy2@reddit
spending 3 days chasing a phantom bug only to realize it was a single typo in the config file. the mental toll is completely invisible but permanent lol