51–60 of 64 posts
I do see the value in having some sort of "portfolio" piece to show off your skills and if I have spare time (and I never seem to have much) I may do a small project and put it in the public domain. Obviously there's a limited amount of time that I can put into something like that.
Anyone know how a developer in situation 1 can get a job? I am a game developer, and many game companies have two qualities: 1, they demand lots of time. 2, they do either very specific work related only to their game, or they do things that can be re-used, but then this mean it become very valuable internal tech and must NOT be shared with competitors. Currently my lifestyle is: wake up, drink tea, wear something, g…
Earlier quoted context omitted.
> It's a groupthink thing that I personally try to avoid Because the Good Ol' Boy network of references and handshakes is a groupthink thing you've gamed better.
Huh, I wonder what that means.
I dislike how this is trying to make this about oppression. In particular, the "or maybe they're female" toss-in is just dumb. Contributing to open source, blogging, and having a code portfolio are all relevant to assessing your competence as a developer. Being female is not. Whether or not you have a github account and contribute to OSS is something you have control over (unless your previous employer prohibited it…
The problem is that a lot of us have lives outside of work, and work is proprietary software. I hit this problem in my latest job search. I had a limited presence on github and a rarely updated blog... if you'd asked me 4 years ago, I'd have nothing. Which doesn't mean I'm not a good coder. It means I have a wife and a family and non-coding hobbies, and I'm not 25 with the ability (or desire) to code until 2am every…
With that in mind, let's imagine a manager hiring engineers for a project built on top of an OSS stack. Sometimes that stuff won't work right, and sometimes--I'd argue usually--the right answer is to just fix it. And you're looking at a developer with experience doing just that and someone who hasn't. One has taken the initiative to learn their way around the internals of the tools they use and the other may or may not have. Who do you pick? Contributing to OSS is not just a badge of honor here; it's what's left behind by good development work.
Sure, some jobs don't have that. Maybe it's a video game built on some proprietary toolkit, maybe it's a low-level library written from scratch. But surely those aren't the employers who care so much about your Github account, right?
Depending on the type of work you do your code would not go on github. If you write code for drivers for IR cameras in C or fix bugs in FORTRAN you won't be putting your stuff on Github or contributing to stackoverflow. Github/stackoverflow is, in my opinion, more catered towards the mobile/web/C# community. Military, medical equipment and aerospace software developers prob don't use it either one very much.
I don't see the parallel between github and Stack Overflow. I can understand why programmers in certain industries and companies won't be posting their code on github. If all of the code you write professionally is proprietary, it makes sense that none of it would wind up in github public repositories. But even if I'm writing proprietary code, I can still ask questions about it on Stack Overflow, and answer other peo…
Github: 329,678 Search language:ada 720,910 Search language:fortran 6,034,816 Search language: c# 44,430,272 Search language:javascript
The two services are heavily used by the C#/web community. mobile too but I did not include numbers
Earlier quoted context omitted.
Huh, I wonder what that means.
"I'm presumptuous and have little perspective into how work actually gets done," would be a good interpretation.
As opposed to doing your own research and developing your own standards.
Maybe other peoples' definitions are different. That doesn't make either of us presumptuous or ignorant, but you could have laid out your definitions before slinging the insults.
Earlier quoted context omitted.
> It's a groupthink thing that I personally try to avoid Because the Good Ol' Boy network of references and handshakes is a groupthink thing you've gamed better.
Huh, I wonder what that means.
> A Good Ol' Boy network is a wonderful example of groupthink: "If my friends like this person, they must be good!"
> As opposed to doing your own research and developing your own standards.
> Maybe other peoples' definitions are different.
Earlier quoted context omitted.
"I'm presumptuous and have little perspective into how work actually gets done," would be a good interpretation.
A Good Ol' Boy network is a wonderful example of groupthink: "If my friends like this person, they must be good!" As opposed to doing your own research and developing your own standards. Maybe other peoples' definitions are different. That doesn't make either of us presumptuous or ignorant, but you could have laid out your definitions before slinging the insults.
Depending on the type of work you do your code would not go on github. If you write code for drivers for IR cameras in C or fix bugs in FORTRAN you won't be putting your stuff on Github or contributing to stackoverflow. Github/stackoverflow is, in my opinion, more catered towards the mobile/web/C# community. Military, medical equipment and aerospace software developers prob don't use it either one very much.
+1 for FORTRAN. And there still is DOD market for COBOL. None of that shared.
p.s. is there a language called Babbage?