This morning’s walk was accompanied by [Tiago Rodrigues](https://twitter.com/trodrigues) (excellent) curation and commentary on [Adam Yeats](https://twitter.com/adamyeats) tweets on open source and (mostly) [James Seymour-Lock](https://twitter.com/JamesSLock)'s replies.
[Please read it](https://storify.com/trodrigues/why-i-don-t-like-open-source-a-play-in-3-acts). Carefully. Get all the way through and reserve judgement (if any) for the end.
It’s not the first time Adam’s thoughts have inspired a [blog post](/2012/12/18/contributing-to-the-web-community) either! These are my thoughts on open source, contributing and the points raised in the discussion.
[](https://training.leftlogic.com/buy/terminal/cli2?coupon=BLOG\&utm_source=blog\&utm_medium=banner\&utm_campaign=remysharp-discount)
[READER DISCOUNTSave $50 on terminal.training](https://training.leftlogic.com/buy/terminal/cli2?coupon=BLOG\&utm_source=blog\&utm_medium=banner\&utm_campaign=remysharp-discount)
[I’ve published 38 videos for new developers, designers, UX, UI, product owners and anyone who needs to conquer the command line today.](https://training.leftlogic.com/buy/terminal/cli2?coupon=BLOG\&utm_source=blog\&utm_medium=banner\&utm_campaign=remysharp-discount)
[$49 - only from this link](https://training.leftlogic.com/buy/terminal/cli2?coupon=BLOG\&utm_source=blog\&utm_medium=banner\&utm_campaign=remysharp-discount)
This post is partly edited, but quite long, so might not be 100% coherent. For that, I’m sorry!
Our web community distorts expectations[](#our-web-community-distorts-expectations)
(Not) contributing to open source isn’t the problem. The pressure coming from external and internal sources telling us that we should be contributing is invalid, in that it should not exist, but it does.
How we think people see us is only a reflection of how we feel about ourselves. The project getting the most retweets today is not representative of real work. Nor is the person with the most followers the better human being.
There is distortion in the web community that you need to learn more, contribute more, work more, know everything, be on the latest technology, and so on. Unsubscribe. Unfollow. Turn off alerts and notifications (or at least make your "quiet hours 6pm-9am). Find other human beings.
I want to say that Adam’s tweets are not the fault of open source, but our industry’s distortion. But his tweets and the subsequent replies prompted me to also write down my thoughts about open source that I’ve been mulling over the last few years.
What does open source really mean?[](#what-does-open-source-really-mean)
It means [different things to different people](https://github.com/nickdesaulniers/What-Open-Source-Means-To-Me). That’s okay.
To me, it means:
Welcome. Welcome to this code I wrote. Help yourself to bits you like or need. Help make it better for others. Help make it yours. Help make me better with your suggestions, changes or discussion. Use the code in any way you want, in ways I never thought of. And if the projects I created lives on without me, then open source has worked.
You need to decide what it means to you, and what it looks like. Which leads me to ask: is a project really open source?
There are two kinds of open source projects[](#there-are-two-kinds-of-open-source-projects)
There’s the big, high profile projects and then there’s everything else.
When I’d hear "open source", I’d think: Linux, Apache, Firefox, bootstrap, ember, node, etc. i.e. big fucking high profile massive open source projects with a fuck tonne of code\*.
\* Okay, there’s also a decent number of sensible codebase sized projects that are used a lot, passport for node for instance
This is Type One.
Type Two open source projects are the kind of project where the source is open, and the license is "meh"/"whatever I always use but don’t really understand". For me this is MIT. But that’s beside the point.
The source is available. Just like the web. View source. It’s the kind of open source that I’m familiar with (obviously there’s discussions around licenses, but that’s for another day).
Type Two projects: the kind where the source is just somewhere on the web, is the kind that, if we’re honest, hardly anyone else is going to contribute to. I’ll be lucky if anyone actually uses it, let alone skims the code.
This second type, it could be closed source. It could be something that was never uploaded to the web. But it was. This is the majority of open source projects today. Very much like the late 90s when there were sites offering JavaScript …files (because library and framework really doesn’t apply) that gave you menus, hover effects, basic whiz bang stuff. Except now it’s up on Github or npm (or whatever you Ruby folk use!).
If someone sends a pull request to one of these projects, there’s a few things that can happen: it’s ignored/forgotten about or it’s blindly merged "meh, cool" (there’s other outcomes too!).
For me, putting code in github as "open source" is for two main reasons: 1) so if I lose the code locally, I can find it again (fingers crossed Github doesn’t vanish too quickly), 2) I can’t be arsed to pony up the pitiful amount of dollars for more private repos.
The majority of the repo owners on the type one projects are companies. It’s their product. The majority of type two, are individuals. Let’s remember that perspective. Contributing to the small ones isn’t a big deal and potentially contributing to the big ones might be like pissing in the ocean.
Contributing to open source[](#contributing-to-open-source)
I can’t speak for Adam, but it sounds like he’s either felt pressure to contribute to some projects either externally or internally. I could be way off based, but I do know people who’ve felt this way. Heck, I feel this internal pressure sometimes.
Contributing (code) to the Type One projects isn’t something you can do with a few hours. So seriously, if you feel this pressure: stop it.
It takes hours, if not days to become familiar with the codebase. Then creating a bug fix or a new feature isn’t quite as simple as "hacking some code in". If it’s a high profile project, it’ll come with tests and coding guidelines. That’s more work, and you’ve not even contributed a single line yet.
For context, in late-2000s, I partook in a [jQuery day long sprint](https://web.archive.org/web/20130512035317/http://docs.jquery.com/JQuerySprint) to fix bugs. I’d say I knew jQuery pretty damn well at the juncture. By the end of the sprint, I’d managed to confirm just one bug, and pretty much have an idea of what caused it.
"Contributing to open source" is a long term commitment, and you do have to pick and choose. There’s a few people like Substack filling npm with his node modules is great, perhaps reinventing every wheel, but he’s also doing it to [cover his living](https://gratipay.com/substack/). But these people are the exception. This isn’t a lifestyle that’s available to most people (and frankly, npm is running out of useful names for projects!).
Ask yourself what is open source. Ask yourself if you want to contribute to that, and if you do (want to contribute) ask yourself why.
Hiring purely based on open source contributions[](#hiring-purely-based-on-open-source-contributions)
…is bullshit.
But maybe, maybe some companies will exclusively hire you based on your open source contributions. Honestly, if that’s the case, it’s more likely you’re not applying for the job, and in fact the company is head hunting you.
It is true that an "open source" project is seen as a reference of work. But it’s also a stale reference of work. And importantly, it’s not the only reference.
Take my open source [inliner](https://github.com/remy/inliner) project for instance. The code is appalling. There’s outstanding open issues and pull requests. This is an open source project that is not representative of my current skills. Yet it’s still open source. I wouldn’t put it forward as my best work.
[JS Bin](https://github.com/jsbin/jsbin) is probably a better example of my work, but honestly, the code is not my best foot forward. In fact, I’ve had job offers based on the companies associating me with the project, but I know for certain that they’ve not looked at the code.
Hiring decisions are mostly based on some early criteria that’s utterly arbitrary. Like "do they have a degree", or "do they have a github account", or "what is their personal interest". The reason: to reduce 100 CVs down to a manageable number that you can actually interview.
When I interviewed [Fabien O’Carroll](https://twitter.com/allouis_) in late 2013 he had limited open source projects I could look at (which I would have skimmed to get an idea of scope of projects he works on), which is fine, and he couldn’t really share his company’s code.
With all my interviewees I asked them to write me a hangman game in JavaScript, and not to spend more than 2-4 hours on it (in their own time). I would pay each an honorarium for their time, because it was likely they were already employed and would have to do it out of hours. Personal time is valuable, and no one has an automatic right to it.
His code was decent, but that’s not what got him the job. During the interview, when asked if there was anything else he was interested in, he struggled then eventually mentioned he built a chess timer (in wood) that he could use with his then-girlfriend. That’s what got him the job, and that same sentiment is what I saw over the following year. That detail doesn’t belong on github, isn’t part of our community, but is part of an interview.
Never undervalue what you do. Everyone is unique. Some people aren’t right for some jobs, but you github streak says positive and negative things.
If you can’t contribute: you’re not part of the community[](#if-you-cant-contribute-youre-not-part-of-the-community)
Arguing that someone should get a jobsworth position\* because the work 9-5 (or whatever extra overtime) is bollocks. It’s not the first time I’ve seen it either. This kind of sentiment is utterly selfish and narrow minded.
\* It’s worth pointing out that James' tweet was [between friends](https://twitter.com/JamesSLock/status/553546788779859968)
The people who have a high chance of working on extra curricular projects are likely to be single, not terribly social and in their 20s. Why? Because when you’re on your own and younger, you have more energy, and you need less sleep. When I was in my 20s (and married) I was hacking until 2am in the morning. What was my code like between 10pm and 2am? Shit. In fact, it’s taken me years to realise that when I’m not on form (i.e. past 6pm) that it takes me twice as long, if not more, to complete a simple task. A complex task is unlikely to get fixed.
Our brains fuck with us when we deprive it of rest. Tell yourself you have RSI. If you have RSI, you rest. You move away from typing at a keyboard because if you push it, it hurts. Take that approach.
Now that I’ve got young kids, when I leave the office, someone will ask "what are you up to this evening?". The same as every other evening: I help put the kids to sleep, I cook (or help cook), I eat, I got to bed. I love that I’m with my family, and it’s enough for me. There is no time for coding in that evening.
My thoughts[](#my-thoughts)
I’ve got another post that I’m writing about "what I love about the web", which is sort of related: enjoy what you do. Question where the pressure comes from. If possible, focus on what you love and ignore the noise of "hey, look at my cool thing".
There is this weird pressure to get a "name" in our industry. But fuck, seriously, you are amazing. You work hard and you should be proud of your work irrespective of whether others can see it in the open.
You come first, not your code or someone else’s project: you.
For me, my family comes first. Work and code isn’t even a distant second. It’s taken me many years of working silly hard and silly hours to work that out. Now that I understand that, life is better.
Published 9-Jan 2015 under #web. [Edit this post](https://github.com/remy/remysharp.com/blob/main/public/blog/dont-like-open-source.md)
Comments
Lock Thread
Login
Add Comment[M ↓ Markdown]()
[Upvotes]()[Newest]()[Oldest]()

The Ders
0 points
4 years ago
It’ll be a cold day in hell before I find an open source project that doesn’t have a stubborn developer gatekeeping contributions and running it into the ground with a dunning-kruger inspired management style.

Johaness
0 points
5 years ago
I take my time to read your text and I highlight this part\ "It takes hours, if not days to become familiar with the codebase. Then creating a bug fix or a new feature isn’t quite as simple as "hacking some code in". If it’s a high profile project, it’ll come with tests and coding guidelines. That’s more work, and you’ve not even contributed a single line yet."\ That’s too obvious for seniors, I think most seniors should in fact stay away from open source, let it to cool young guys with spare time. We above 30’s don’t have that time we should spend it on important things not debugging someone else project without any such of reward.
In fact, most my career was spend on open source stuff, because my background is from South America, countries like Brazil, Mexico, Central Americas, Argentina don’t have money or they don’t want to pay for software period. Try convince your boss that they need to pay for using any such of IDE which could fosther your development and be very stable. They will say "just stick with Eclipse it works" but in fact, most of times you lost time trying to figure out, configuring and dealing with bugs on those open source free stuff that never will with strong software closed like Intellij or Visual Studio… if we have a bug on oracle we call em and say "hey whats going on?" they are obligated to solve that shit and send us kind of Patch, that’s same for any real good companies. Try the same for any obscure garbage open source api, people just ignore your bugs, I seen so many bugs addressed to that Eclipse IDE and they just refusing! "That’s not our problem" "try that a b c x obscure procedure" "try using linux it won’t works good on Windows" but most companies around the world still use Windows because Office!
I’m just tired of so much pain on the opensource, java etc stuff, really, I think money is on closed source that’s why Apple IOS is so much superior and worth more money for devs than Android. That’s a fact.\ Most comments from people with that funny names from South Americas underdeveloped countries should be ignored, people there don’t value free time and will have a lot of headache and panic but only to justify that crap "anti american" feeling against Microsoft, USA and every big company that’s why they love opensource. They even will refuse use the word American because they believe that’s wrong and they are American too. That’s another discussion but opensource really sucks because when it fails that’s so much pain and you cannot blame none, most of times you don’t have choices.

Tim Lawrence
0 points
7 years ago
Old thread I know but I feel compelled to comment :-)\ A large part of the premise here appears to be that contributing to OSS should be in your own time. In a world where a large portion of software & infrastructure delivery tools rely upon OSS I would hope that many companies would allow employees to contribute code to relevant projects during their day job. It is certainly encouraged where I work. This is not something that is confined to small companies either. Last week I was at a meetup at Fujitsu where they claimed to be in the top 5 contributors to a major OSS project. The same companies who are hiring people based on OSS contribution are also trading on the fact that they have people contributing. Clearly this has not always be the case so there will be a lot of people out there looking for a role who cannot necessarily back this up. For me not being able to demonstrate OSS contribution is fine as long as you can prove you have understood it’s value to my business and can in some other way prove your credentials as a practitioner.

Johaness
0 points
5 years ago
you have false hopes, companies won’t allow that never. time is money.

roosterscrow
-1 points
9 years ago
all through my 20’s I used OSS without contributing, now I’m married in my 30’s and starting to produce free services and contribute to OSS. If you’ve heard of the 3 phases of life…learning, earning, and giving….maybe once you’ve retired you’ll be contributing a lot? Anyway, I’m now successful enough to not care about getting paid for every hour of work, I give a lot of money to charities, and I’m starting to give my time back to the open source community that saved me so much time in my 20’s. I’m just naturally drawn to it now...and it feels good dammit. Gotta disagree with you, I’ll continue contributing my shitty code out of pure selfishness.

Johaness
0 points
5 years ago
give what? that’s stupid. give your free time for unknown people is the most idiot thing I ever heard

Patrick2001
0 points
9 years ago
Well, I just lost my long original reply. So here is the short version:\ First, open source means +/- the same to me. It is a good definition.\ Second, I disagree that "This second type, it could be closed source", because then I could not run jsbin on my own account, where I am in control of the data ("just for fun", not really using it extensively…). :-) And because this is overdue: Thank you (!) for making it available open source.\ Third, I disagree that "This second type, it could be closed source" because of point one in the below article; It helps me create quality software and it just makes my life better in general, as it enables me to just "check what is wrong" when debugging.\ Fourth, it is not true because you can learn so much by reading source code, which I often do "just for fun".
…
Point 1 advice in the article by Brandon Rice (2015-01-15):\ "1. Maintaining Situational Awareness (Reading Code)\ \[…]\ In software development terms, maintain awareness of your\ surroundings by reading code. Read the code that other members of your\ team write. Read the third party library code in your application.\ Before charging ahead to implement a new feature, read the code that\ might be affected and understand the implications of the needed changes.\ In many cases, you may spend more time reading code than writing it.\ That’s a good thing." — [http://www.blrice.net/blog/…;](http://www.blrice.net/blog/2015/01/15/investigating-higher-quality-software/)

Paul C. Shirley
0 points
9 years ago
Great article!\ I have always felt "bad" about not having the time to contribute to Open Source while also feeling that I really should so that I can show my coding abilities.\ As mentioned, I am, like most people, in the position where I would not be able show source code from my job,\ This article has helped me to realise that I shouldn’t feel that way.\ Thanks.

Vinay Raghu
0 points
9 years ago
I have heard the "people don’t have time for OSS" argument before. Frankly, there are very few companies that would refuse to hire you. If you can’t show code you have written before, they usually just give you a test to judge your skills. That test is done even when you do have OSS contributions.
I’ve contributed, sometimes regularly to projects I care about. I think its a good deal to be able to do that.
But there is value in open source guilt and building something that you can’t maintain over time. That’s when OS contributors resort to kickstarter campaigns to maintain their repos.
All in all, thought provoking post. We need more people arguing about things outside of tech. My resolution for 2015 is to pursue a lot of my other passions outside of web dev, especially reading and writing. But also some outdoor fun.
That doesn’t mean OS is bad or there is a terrible expectation from the community or employers. I agree this needs to be handled with care, but I don’t see a BIG problem in the first place.

Mehdi Shojaei
0 points
9 years ago
I think if we have really a good idea to improve an open source project, we can do it. Not only for joining the contributors of that project but to really improve it. And yes life is first.

ShirtlessKirk
0 points
9 years ago
For the last four years I’ve been commuting to London to code all day. The commute time was minimum 5 hours a day. Every day. This is on public transport where there is little to no connectivity, so no chance of quickly looking something up to fix an annoying bug in my personal code. No one gets overtime as a developer in UK so I’m not about to work extra hours for free anyway.
After 9 hours at work combined with 5 hours of travelling every day, the last thing that I or my wife would want is that the second I get home - bear in mind I haven’t eaten for 8 hours either, and she’s waiting to eat with me - is that I hack away at some code "for fun".
I have one Gist on Github. One. And it was a first iteration of a CC number check function that I never got around to updating and others have since improved upon. It was good enough that Yelp contacted me about using it (3 years after the fact, but whatever). I’m a bit proud of that, but also sad that I couldn’t contribute more; I’ve got a project idea that stewed for years until computers and connectivity got fast enough for me to do it.
But I simply don’t have the time. Or the inclination to deny my wife the 2 hours a day I get to see her, as she is far more important to me than a fucking codebase. I’ve got hundreds of saved pages on Evernote and Pocket that can aid me to realise this magnum opus; I’ve certainly got the skill to create it. However, I’d like a life that doesn’t involve staring at a screen all hours of the day.
If that means some employer won’t hire me because I’m not "contributing" then I don’t want to work for them anyway and I hope their business crashes and burns. I have more important things to worry about than their bottom line.
꧁ Arya Princess ꧂
0 points
19 months ago
5 hours to go back and forth to work every day? How about change the place you live?

Dave Stewart
0 points
9 years ago
I totally get all points in this post, and a bunch them in the comments.
The thing for me about open source, is that’s a chance to write some long-lasting, quality code, that solves real problems (be it a gist, jQuery plugin, or full-on framework) - rather than thrashing out the lines under tight client deadlines, that will last a campaign only, and will never really be appreciated for its elegance and beauty.
Most of my open source projects are spawn of real-world requirements, and the desire to take a really good idea, make it all that it could have been, polish the details, then release it to the world. (FWIW I’ve been [writing and releasing code online, for free, since 2001](davestewart.io/posts-by-date/)).
It’s also the reason in my latest contact I’ve negotiated a 4-day week. I want the best of both worlds, and if I had a family, I’d be able to fit that in as well.
Lastly, the side of open source that is REALLY hard is the final polish and documentation. That’s the side of things they don’t tell you about, and where a project can easily live or die.
I guess it just depends on your motivation for doing it in the first place. As I said, I do it for the joy of crafting something "just-so". If someone feels like they should be doing more Open Source and they’re not, they could always help themselves and just go to less conferences ;)

jerome\_etienne
0 points
9 years ago
personnaly i do look at how people code before hiring a coder. and i dunno any better source that the code they wrote before. So opensource code because it is the only source availble. (to read previous code without opensource doesnt seem reasonably feasible without breaking the law, nda, lawyers etc…)
You say hiring based on opensource code is 'bullshit'… and advice to make a 4h test ? i dont understand. you even say 2h..
You expect to know the quality of a coder in 4h ? the interviewed is in a stressfull situation, aka being measured to get a job. he is not familiar with its environment. it is only about a very specific problem. The personn productivity is very low compared to its usual rate.
I dont understand… this seems much less efficient than to look at the code the personn wrote during years over multiple project in its natural environement seems way more representative to the personn ability.

rem
0 points
9 years ago
Just to be totally clear, I’m saying not hiring because someone doesn’t contribute to open source is bullshit.
It’s not my advice, it’s something I do, allowing the potential interviewee, in their own time, days before the interview, to complete a task that I set. This allowed me to assess two candidates code that otherwise did not have much if any code in the wild.
I hope that clarify what you were confused about.

jerome\_etienne
0 points
9 years ago
thanks for answering and clarifying.
This indeed sounds different from the title in the post "Getting a job based on contributions is bullshit.". if you got time, it may be good to update this title to avoid confusion.

rem
0 points
9 years ago
Updated (a couple of days ago) - cheers for the feedback.

Tim Lawrence
0 points
7 years ago
\#1 merged ;-)

Justin Marsan
0 points
9 years ago
While I’d really like to argue, yourself being rather "famous" and all that kind of makes it all sound like rich people saying money doesn’t bring happiness… I’d like more people to know about me, how great I am and that I know stuff…
But nobody does. No employers do, and even if it’s not entirely true, I feel like if I was famous in the dev world, had projects with thousands of stars to back me up, thousands of followers and a website that says I publish books, write articles and give conferences, and somewhere mentions that I also work at X or as a freelancer, things would be much easier for me.
I’m not saying I disagree, I’m just saying if so many people believe it, maybe it’s because it’s not entirely false, and the fact that you don’t see it may be because you’re on the side where the grass is indeed greener.

rem
0 points
9 years ago
This "fame" you talk about. Let’s put it in perspective. I’ve been working professionally on the internet since 1999, and I’ve been publishing my blog here since 2006 (and the first few years we [dull](https://remysharp.com/2006/09/01/flickr-geo-tags) as hell!).
I’d admit, some people know my name and my work. But that’s kinda because I’ve been around for quite a long time, and I keep just posting the odd thing here and the odd thing there. It all adds up.
"Fame", as we commonly know it, is actors, etc, on the big screen. They get handsomely rewarded for that class of fame. If I’m famous, what has it got me? I’m not saying I am, I’m putting it in context.
Well. I’ve had the great privilege of being travelled to a few countries that I wouldn’t have travelled to otherwise. However, some people have non-web based jobs where that’s normal. My friend is a top HR person in her company, she’s flown to New York, Japan and more.
There’s downsides to flying, alone, not knowing anyone, being horribly sky, being away from family, etc - but that’s not my point.
Beyond that? Not much. In the 8 years I’ve been running my own business, the best my "name" got me was a client willing to wait 3 months until I was available.
The real benefit of being "famous", and hold on to your seats because this is huge (and I actually mean it): making friends in my adulthood that I would otherwise never had made.
Writing a book? Anyone can sign up to that. Personally, I suck at writing books. I struggle to keep my blog running if I’m honest (and I cheat by having a backlog of drafts ready so it looks like I’m publishing more regularly).
I’ve never worked at X company. I worked at Digital Look. Heard of it? Nope, most people haven’t. My own company, the one I run, most people don’t even know it either. It’s [Left Logic](http://leftlogic.com) in case you wanted to know!
You, and only you, have the power to be who you want to be. When I left my employer to run my own business, I said to a friend "I know no-one in Brighton, they’re all 'famous'". Know what I did? I went to the pub and met these famous people, and it turned out, they were people. Not famous, just people.
The web is amazing. You have the exact same access to the world as I do. And yes, twitter followers helps your voice getting heard further, and so does blog subscribers, but if you really want your voice heard, you don’t shout loud, you just keep talking.
Just to add, I don’t just see the pressure, but I feel the pressure of having to know everything all the time, all at once. I do feel like an imposter. I hate that /something/ in our web community turns me into a green monster (no pun intended).
But I get home, and I try, day by day, to close my laptop and ask myself: what’s more important? Work or my children. Work can be fun, and yep, kids are hard, but it’s them, every, single, time.

Justin Marsan
0 points
9 years ago
First of all thanks for the honest answer, I’m glad this is turning in, at least for me, an interesting conversation that hopefully changes my opinion on things.
When I talked about fame, I meant that you have 38K followers on Twitter, and 3K on GitHub. I’m sure people don’t stop you on the streets for autographs but whenever you decide to share some random though or a piece of code you hope not to lose, it’s seen by hundreds of people whom, if they don’t know you for what you’ve done at least see you as the guy with thousands of followers.
Sure you got that built over time, and that’s a part I ignored in my first message but that I do need to acknowledge, I agree, but the result today, maybe not for you, but for some other people are huge. Take Chris Coyer’s Kickstarter reaching like $90k or so if I remember correctly, it’s not "up to you" to do that, you have to be someone before. Just like you can’t just announce you’re publishing a book about atomic design and have hundreds of people RTing it or preordering. It doesn’t work that way in the muggle world.
You’re probably not the "right" person for me to rant about, because as you state, you haven’t had much benefits from your internet-dev-scene fame, nonetheless, I still feel like having a huge audience and credibility built up changes a lot of things, even only on the work side of things.
That being said, I absolutely agree with your opinion on work-life balance, and I don’t have much to add on the topic of giving back to the community and all that. I realize now I’m a bit off topic and ranted about a very small part of your whole article, so I’ll leave this discussion where it is, thanks for your answer :)

Bevan Stephens
0 points
9 years ago
Fantastic post, This has made me think twice about a few things. And made me feel better about some pressure that I have felt recently to 'contribute back to the community'. Since having a child, I’ve quickly realised that working in the evening on passion projects has had to stop. At least until they leave home :-)
I also used to think that 'making a name for myself' was important but I’d rather just focus on trying to improve peoples live by good design, and enjoying the process while I’m at it.

Nathan Gloyn
0 points
9 years ago
You’ve hit the nail on the head about the people who have time to do a lot of out of hours work, as soon as you have kids things change and you do have less time for extra curricular activities be it kite-surfing, wood working or contributing to OSS.
Strangely enough I’ve had more than one conversation about this just recently (one just this morning by chance) perhaps it’s going to be a theme in 2015

paulleader
0 points
9 years ago
Spot on.
Where did this idea come from that being a developer meant you were supposed to do it all the time, every day, that it’s supposed to be your work and your hobby?
Almost no one else does that. There are a lot of industries where people work long hours, but when you leave work you stop and do something else. Even when people take their work home they don’t do it as their hobby.
Even most artists, if their art becomes there job, have a split between work and not-work.
I’ve a five month old son and I’ve come to the conclusion that while I’d love to do the odd side-project, after a day at work, playing with him and putting him to bed, the last thing I’m in the mood for after is opening my laptop and spending another few hours writing code. I just want to sit and read a book with a glass of wine in my hand and relax for a bit.
And you know what? I no longer give a crap if people look down on me for it.

James Jackson-South
0 points
9 years ago
I like this post, a lot. Thank you for writing it.
I have a very weird love/hate relationship with open source. I have a couple of projects that have become fairly successful and I have reaped benefits from those contributions. I’ve made great friends and learned much more than I would have simply doing my day job. It’s helped me to gain employment also.
My work/life balance however is a mess. The commitment of time I make to my projects far exceeds what is healthy for me. The competition to make a "name", gain followers, the ever increasing feeling of imposter syndrome has drained me and left me contemplating at times whether I should find a new career path. The pressure, both internal and external is huge.
"You come first, not your code or someone else’s project: you."
Could not ring truer. It echoes the sentiment of a great friend and developer Douglas Robar https://twitter.com/drobar who has been giving a talk recently in the Umbraco community about being real and ensuring that you live your life with no regrets. I agree with it wholeheartedly and it is an ideology with which I fully intend to live my life in the future.

Tiago Rodrigues
0 points
9 years ago
I would also propose reading James Coglan’s great post about this here: [https://blog.jcoglan.com/20…;](https://blog.jcoglan.com/2013/11/15/why-github-is-not-your-cv/)

Andi Smith
0 points
9 years ago
Great post, says everything I was thinking. There is a weird pressure, I see many devs (myself included) feel this pressure and it is silly. We are all amazing!
[Commento](https://commento.io)