Earlier quoted context omitted.
Not to be rude, but why do you think that contributions to in-house/closed-source projects should count as contributions to open source? By definition, if you contribute to an open source project, you should be able to point to the public code you wrote. What you're describing is basically previous work experience (which is already on your resume).
I am talking about contributions to open-source projects under the name of the employer. I have signed NDAs with clauses that state that as an employer I am responsible for the maintenance of the internal systems including the bug fixes to whatever project the system depends on, but later there are clauses that prevent me from identifying myself as an individual contributor to these open-source projects, I have to us…
How to present a GitHub project for your resume (2016)
31–40 of 89 posts
Re: How to present a GitHub project for your resume (2016)
#32Earlier quoted context omitted.
You jest, but it's clear you've not tried to make that product, as it is much harder than it sounds if you count "make it past their spam filter" as delivering email.
I've made that product. I've had 10 customers ask me for that product with a straight face. The spam filter isn't a concern if it's an intranet product -- at worst, it's a support call which leads to some instructions on the page. It still saves them from buying some amount of printer toner and using fax lines. Everything else there is true to some degree, which captures the spirit of writing resumes. (IMO the bigges…
I've done the same, its a classic corporate warfare tactic, there exists an agreed on paper form to standardize the demarcation point between two warring internal groups (and all internal groups are at war because of stack ranked management reviews, formal or otherwise...), someone on the home team was manual data entering that paper form into "something" now you can push that labor cost onto the other side who now do the manual data entry for the home team. For bonus points toss each data entry into a database and provide some manner of weekly reporting via web or email cron job, maybe some dynamic error checking at data entry time. Classic weapon of internal politics. I've made a lot of money off this, historically.
There's a whole universe of MBA companies out there that see computers abstractly as mere fancy electric typewriters, merely a modern Linotype machine, its just a modern mimeograph nothing more, a way to format manual data entry for other humans to read and manually data enter in something else. Computers that don't compute or have flowcharts, merely manual human I/O devices. Adding the slightest bit of automation can blow the minds of business people.
Beware of the inner product effect. A simple web form that emails the ticketing system in restricted cases can eliminate enormous amounts of manual data re-entry if it happens enough, but trying to turn it into a generalized tool will merely result in a "simple web form" that becomes more complicated than the ticketing system everyone was avoiding because it was too complicated for end users. Don't write a feature complete 100% wrapper for JIRA with the expectation it'll be simpler, thats not going to turn out well. Of course in corporate warfare sometimes punishing the other internal department is more important than making things simpler and faster for all, and if it gets your team out of the data entry task and puts them on the data entry task, well, the guy on your team who signs your paychecks is going to be happy with you.
Re: How to present a GitHub project for your resume (2016)
#33True. We don't ask for GitHub links because they are pointless from a screening perspective. I'm happy to talk about them during an interview, but if I see a github link in a CV, there's little chance I will visit it. (Source: I'm a hiring manager at a tech company, have been in a similar position at previous jobs for several years).
The fact is, as a hiring manager, I would have no time at all to do anything if I start looking at all my candidates' github links. I would be more than happy to look at a portfolio showing products built by them, if they look interesting, I can ask technical details during the interview.
Re: How to present a GitHub project for your resume (2016)
#34I definitely make this mistake. I have a handfull of maintained projects, but nearing 100 repos, most without readmes, many are just random ideas The last time I interviewed the technical interviewer actually had me go over my openEtG project, & dive into the guts of the AI's eval. They also stumbled upon https://github.com/serprex/brainwebfuckassembly which ended up having a profanity filled interview They started t…
My difficulty with interviews is, I'm a fairly good programmer. But when asked to put these kinds of things into words, that's just not how my mind works. I see the patterns in abstract ways, and I know which ones to use when. And I can write clean code pretty well. And if presented with a concrete problem to solve, I can communicate effectively on how to solve it. But during interviews, or any kind of abstract discu…
That is not only between persons: I can get myself into a talker's mindset in a couple of days just by reading, drawing diagrams and generally doing anything that increases self confidence.
My actual coding abilities drop in the process because the ability to see abstract graphical patterns decreases.
On my best coding days I'm barely able to utter a coherent sentence at the end of the day.
Re: How to present a GitHub project for your resume (2016)
#35Earlier quoted context omitted.
I am talking about contributions to open-source projects under the name of the employer. I have signed NDAs with clauses that state that as an employer I am responsible for the maintenance of the internal systems including the bug fixes to whatever project the system depends on, but later there are clauses that prevent me from identifying myself as an individual contributor to these open-source projects, I have to us…
Was a justification given for this? The company doesn't seem to be gaining from keeping the identity of the contributors secret (if they wanted to mask the fact that they were using a particular piece of OSS I could kind-of understand that -- but doesn't seem to be the case here). Is it really as spiteful as "we don't want you to gain personal credit for work we're paying for"?
Re: How to present a GitHub project for your resume (2016)
#36I definitely make this mistake. I have a handfull of maintained projects, but nearing 100 repos, most without readmes, many are just random ideas The last time I interviewed the technical interviewer actually had me go over my openEtG project, & dive into the guts of the AI's eval. They also stumbled upon https://github.com/serprex/brainwebfuckassembly which ended up having a profanity filled interview They started t…
Re: How to present a GitHub project for your resume (2016)
#37Re: How to present a GitHub project for your resume (2016)
#38Earlier quoted context omitted.
My difficulty with interviews is, I'm a fairly good programmer. But when asked to put these kinds of things into words, that's just not how my mind works. I see the patterns in abstract ways, and I know which ones to use when. And I can write clean code pretty well. And if presented with a concrete problem to solve, I can communicate effectively on how to solve it. But during interviews, or any kind of abstract discu…
I often see an inverse correlation between being able to "talk about code" and actually producing good code. That is not only between persons: I can get myself into a talker's mindset in a couple of days just by reading, drawing diagrams and generally doing anything that increases self confidence. My actual coding abilities drop in the process because the ability to see abstract graphical patterns decreases. On my be…
Re: How to present a GitHub project for your resume (2016)
#39Earlier quoted context omitted.
My difficulty with interviews is, I'm a fairly good programmer. But when asked to put these kinds of things into words, that's just not how my mind works. I see the patterns in abstract ways, and I know which ones to use when. And I can write clean code pretty well. And if presented with a concrete problem to solve, I can communicate effectively on how to solve it. But during interviews, or any kind of abstract discu…
I often see an inverse correlation between being able to "talk about code" and actually producing good code. That is not only between persons: I can get myself into a talker's mindset in a couple of days just by reading, drawing diagrams and generally doing anything that increases self confidence. My actual coding abilities drop in the process because the ability to see abstract graphical patterns decreases. On my be…
He's very charismatic and a great speaker, and he has a successful business selling his experienced expertise and advice.
But having pair-programmed with him many many times during that time, I was surprised by his inability to discuss real-world coding problems and their potential solutions beyond more than a superficial level.
What I took from that experience is just what you said: there seems to be an inverse correlation. I could produce code that solved complex problems thoroughly and bug-free, and he could talk about them in an abstract way, but neither of us could do the other part.
Re: How to present a GitHub project for your resume (2016)
#40I definitely make this mistake. I have a handfull of maintained projects, but nearing 100 repos, most without readmes, many are just random ideas The last time I interviewed the technical interviewer actually had me go over my openEtG project, & dive into the guts of the AI's eval. They also stumbled upon https://github.com/serprex/brainwebfuckassembly which ended up having a profanity filled interview They started t…
My difficulty with interviews is, I'm a fairly good programmer. But when asked to put these kinds of things into words, that's just not how my mind works. I see the patterns in abstract ways, and I know which ones to use when. And I can write clean code pretty well. And if presented with a concrete problem to solve, I can communicate effectively on how to solve it. But during interviews, or any kind of abstract discu…
I could tell you when a sentence had a problem and how to fix it. What I couldn't do was tell you why something was wrong in the language of talking-about-language. Basic parts of speech, sure. Past that I was lost. It took learning a fair bit of French in a formal setting to get that stuff to stick. I think the problem was that I didn't need those words to think about my native language[1]. It just happened for me. Learning a foreign language made it easy to pick up the vocabulary, because I actually needed it to talk about what was going on.
Point being that maybe there's a way to pick up some of the lingo by finding a way to need it. Maybe learn a radically different programming language from what you're used to.
On the other hand I find that even a not-especially-deep understanding of how things actually work makes some of these named concepts and patterns look like really obvious and not-needing-their-own-words cases of some more fundamental thing, so if it's that giving you trouble then I'm not sure what to do about that or how to make you need those words enough to learn them. Some significant percentage of the time I end up re-casting "complex" ideas as an implementation/combination of some simpler or more fundamental thing(s) I already know, which turns out to be an exact match for how the thing actually works and leaves me wondering entirely WTF all the fuss is about, and usually thinking I don't actually understand it long after I in fact do because everyone writing/talking about it is using mysterious, magical language. Being able to communicate with people who prefer to... I don't know, come at problems from the other direction I guess, is a problem I continue to have.
[1] N.b. I would eventually have needed them to develop further, and I picked up some really bad habits in high school that harmed the quality of my writing but helped me make mandatory page counts so I definitely had room to improve.
[EDIT] embarrassing farther/further error. The finer points of usage remain a struggle.