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?
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?
It’s better that you don’t use resume driven decisions. Just do whatever you are interested in.
Should I put my Prison Architect mod tool on my resume? /s
Unironically yeah, sitting on the other side of the table it’s painfully obvious when people do resume projects. I’d rather talk to you about something you’re passionate about.
I mean, the more I think about it, the more I think it might be relevant. They’ve got this very bizarre format (instead of something like JSON) and I wrote a thing to parse it and format it back out.
The joke being “Prison Architect” (especially as a game) sounds very bizarre to be on a resume.
You don’t have to mention the name of the game. Simply mention the language, and what the mod does.
Unironically yes and it may be a fun conversation. But you may end up being hired as a toxic middle-manager with that experience.
Back to procrastination it is! \s