Programming

17832 readers

107 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

What's Better For A Project Portfolio: Build From Scratch Or Library Knowledge? (lemmy.ml)

submitted 1 day ago by [email protected] to c/programming

24 comments fedilink hide all child comments

I'm currently working on a project in C where I have a choice between using a library for hash tables or simply creating my own hash table from scratch.

What would look better on a Github portfolio from an employability perspective?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 15 points 1 day ago* (last edited 1 day ago)

Almost my entire career I've worked in open source, so it's very easy to see what my technical work looks like. No one has ever looked at it.

When I have been on the other side, I have looked at the GitHub "portfolio" of junior applicants, but TBH, it didn't bring me much. There will always be lots of opportunities for improvements in those examples, but that's the point - I expect them to improve on the job.

More experienced developers will almost never have significant work on GitHub, and if they do, it's not a "portfolio", but just their past work.