4 ms·
I like your last sentence. I am also sceptical if this is a good thing. And with reason: If you are working as a skilled software architect - and you work on pr
by dataguy 16y ago
I like your last sentence. I am also sceptical if this is a good thing. And with reason: If you are working as a skilled software architect - and you work on projects under NDA or other laws/contracts for a long time, it could definitely come to the result that you do not have "current code" somewhere out there on github and such sites.
And not everybody has the time or the reason to contribute or start an open source project. That even becomes more critical if you want to do other things in your non-working time than coding.
If you have the chance to work for a company where you are allowed and instructed to work on open source projects and technology, then you are lucky. But I doubt that the major of software designers does so.
- jonpaul 16y agoYa but I think you're missing an important point. Having an active Github can demonstrate a developer with passion instead of one who just sees it as a job.
- Retric 16y agoI know way to many passionate, articulate, and terrible programmers to think passion a good thing. I also know plenty of really great programmers who don't find coding a challenge after all these years. On average I think passion speaks more to youth than the ability to get things done.
- jrockway 16y agoWhat does he do with the other 16 hours of his day? If I can hire someone who spends 41 hours a week programming, with 1 hour of work that I can actually see, that is going to be a big advantage over someone who claims they are a super-genius architect. Because the first person has documented proof of ability, but the second person just says he's really good. Don't worry, though. I work with "C++ experts" who don't realize you have to allocate memory before writing to it. Knowing how to program is not a prerequisite to all programming jobs.
- dalore 16y agoOnly 41 hours a week? Where do they work and are they hiring?
- jrockway 16y agoAnywhere? I've never had a job that required more than 40 hours a week.
- billybob 16y agoSome jobs don't "require" more than 40, but when your fellow developers are always there earlier and later than you are, and when your performance reviews go from bad to good after you ratchet up your number of working hours, and when your assignment list keeps growing longer and more urgent, you get the message.
- dpritchett 16y agoThis is probably a sign to change your situation. Start working 40 hours a week, expect bad reviews short term, build a huge open source portfolio using the extra 10-20 hours/wk you've created for yourself by opting out of the sick system. Next year, you have a better job elsewhere.
- deleted 16y ago[deleted]
- jrockway 16y agoThis means it's time to change employers and get your 30% raise.
- philf 16y agoI suppose you also need to sleep, so that's 8 hours left of which you spend some preparing/eating food, maybe some sports every once in a while, shopping, socializing etc. Anyway, I'm pretty sure there are people who, while having a passion for software development, feel like doing something else for a change after 8 hours in front of a computer.
- raghava 16y ago>>work on projects under NDA or other laws/contracts for a long time There are firms that actively ask people NOT to post code outside (citing IPR); and at times, even go ahead and mention that anything a person on it's payroll writes (even if written in leisure time or at home off work), belongs to the firm. The 'extended workplace' clause in terms of contract could be suitably flexed.