5 ms·
I really don’t see why these things are relevant at all. It’s a personal Github profile. Why would anyone add thoughtful readme’s or a clean coding style if th
by Aeolun 8y ago
I really don’t see why these things are relevant at all.
It’s a personal Github profile. Why would anyone add thoughtful readme’s or a clean coding style if they’re the only contributor?
I mean, those things are great of course, but not sure if I’d expect it on Github.
- david-s 8y agoSome use GitHub as a portfolio, it seems. Mine is/was mostly a dumping ground of half finished ideas in my college days.
- seba_dos1 8y agoMy GitHub/GitLab profiles are full of hacky, ugly games written at game jams in 48 hours, often just by me or me plus some artist, with just one end-goal: to be able to present it at the end of the event. A README file is the last thing needed there :P
- solarkraft 8y agoI 100% disagree. Even just saying that it was hacked together gives some context for 1) Why the code looks so unconventional 2) What you do in your spare time.
- akerl_ 8y agoContext for whom? My target audience for my personal projects is myself. Any company that assumes their recruiting org is the target audience for my personal projects is setting themselves up for disappointment.
- yjftsjthsd-h 8y agoSure, but we're in a discussion of what recruiters look for. If you only code something for yourself, that's fine, but if you want it to be taken well when job-hunting, you should make it at least minimally presentable (i.e., a recruiter can tell what they're even looking at).
- TheRealPomax 8y agoin which case you wouldn't have put your github profile on your resume, so there is no issue. That's not what this question was about, thought.
- chillacy 8y agoTell us in the readme if you make it public. You gotta think, who is reading this? That goes beyond documentation to code itself and any communication you do.
- godelski 8y agoRepositories are public for a lot of reasons, a lot of which are not "I want to show this off to a potential employer". Let me give some good reasons, that's not an exhaustive list. - It is the default. - Free private repos are new and no one is going back and making things private. - If you are working with someone it is many times easier to make it public. - You want to share code with someone, public is easier than making them a collaborator. Honestly I don't think a lot of people, if any, are reading the stuff I have on GitHub.
- seba_dos1 8y agoI put my things public on GPL out of principle, because there are some people playing those games, so I want to provide all necessary freedoms to them - even if nobody is actually interested in exercising those freedoms, because well, those are shitty jam games.
- seba_dos1 8y agoOf course, I can talk about that. Pointing it out in the README file during the game jam would be the worst use of time available there, though, and even now I have better use of my time than adding it to all of my past ~50 projects like that. This profile is my personal space where I can put any junk I want to. When you're a recruiter randomly looking at that profile, you won't know the context. If you want to know the context, ask about it. It's not my responsibility to provide it in my personal space. (plus, what I do in my spare time is the last thing the recruiter should be interested in, unless I mention it to them myself)
- ModernMech 8y agoOstensibly, you put your code on Github for others to read, use, and maybe even contribute to. If you have a project that you didn't care enough to write cleanly, or even document in the most bare minimum of ways (a helpful README to contextualize the code) then why are you even putting it online? It's just going to reflect poorly upon you. If all your Github repos are as described above, people are going to (rightly) assume that's how you treat all of your projects, even those you are paid for.
- cimmanom 8y agoThat’s quite an assumption to make about intentions. Repository hosting is also a way to back up your code or make sure it’s available on multiple devices. Until very recently, you couldn’t do that and keep your code private on github without paying. So (unless they want to also maintain a bitbucket account) people dump stuff there for reasons other than explicitly wanting to share it with the world or show it off.
- ModernMech 8y ago> Until very recently, you couldn’t do that and keep your code private on github without paying. Ok, but now you can. > people dump stuff there for reasons other than explicitly wanting to share it with the world or show it off. Maybe, but that doesn't change the fact you are sharing it with the world and you are showing it off, and if you put a bunch of sloppy inscrutable code on your GitHub, people are going to assume you tend to write sloppy inscrutable code, especially if you don't contextualize it with a Readme. That's just the reality of it. The real big assumption here is thinking people aren't going to judge you by how you present your work online.
- Aeolun 8y ago> That's just the reality of it. Given that I don’t, and am in a position to hire people tells me this isn’t as hard and fast as you present it.
- 8y ago
- BjoernKW 8y agoIf you use your GitHub profile as part of your personal brand / marketing then these things absolutely are relevant. As a developer in a professional context you'll hardly ever work alone or be the sole contributor. Even if you use a GitHub profile just as your personal code repository code still is communication, even if it's just with your future self. Therefore communication skills are crucial. A well-thought-out README file and consistent, readable code help others to understand your work. These aspects often are more important than what the code accomplishes. Working, even efficient, but unmaintainable code is a risk. Ultimately, code is a precise specification of what the software at hand is supposed to do. If that specification is hard to understand it'll be much less useful.
- RussianCow 8y ago> If you use your GitHub profile as part of your personal brand / marketing then these things absolutely are relevant. The problem is when others assume this on your behalf. I would take a lack of proper readme as a signal that the repo isn't intended for viewing and judgement by others, not as a signal that the candidate has poor communication skills. If the repo is for a library that the author has published and is marketing for production use, then sure, but I'd wager that does not represent the vast majority of repos on GitHub, and to assume otherwise is foolish in my opinion.
- peruvian 8y agoI use to think this way then I started working in the real world with developers who coded and documented work code cleanly but had messy GitHub profiles especially because until recently private repos were not free. A lot of people don't care about perfectly formatted READMEs, commit comments, etc. if they're just hacking on the weekend on something small... and that's fine. Nowadays unless you pushed your profile and repos hard in the resume or interview process, I couldn't care less if the rest of the interview went fine. Worst case scenario they're "forced" to write good documentation as part of the job - not everything we do at work is natural or fun for us.
- stevekemp 8y agoThe assumption is that if you have a personal github project then you're doing it because it interests you, you're passionate about it, and you're not doing it just for money. If a developer writes sloppy code when they're doing it for passion, then that doesn't show them at their best. Of course we all have repositories, tools, or code, that was just thrown together to solve an immediate project but in general I'd expect something that is a labour of love - not a project for work - to be something that they'd put more effort into.
- systematical 8y agoI write verbose readme files with examples of how to use my libraries because it's what I expect of other engineers. I do the same for private repos.
- your-nanny 8y agoif you are linking to it in your resume than you are showcasing it. if you are showcasing it and it's a scrapheap, folks straight not going to be impressed. I think the obvious thing to do is create a showcase profile and a scrappy scratchpad profile. keep the former clean and polished
- closeparen 8y agoPersonal projects can give signal about someone's interests, level of investment, sense of adventure, etc. They're also often an explicit relief valve from "dotting the Is and crossing the Ts" at work, so not a great way to assess professional/production code quality. If I see a tower of inscrutable Haskell on someone's Github, that is a great thing: both that they have the urge to do it, and the good sense to scratch that itch away from the company's codebase.
- k__ 8y agoYes, sounds like BS to me. But on the other hand I'm no employee and don't know the "virtues" employers look for, haha.
- hacym 8y agoYou're right -- if they don't feel like they need to have clean, maintainable code on their own personal work, why would they feel like they need to do it at work? That's a red flag.