DEV Community

Cover image for 5 THINGS I LEARNED ABOUT OPEN SOURCE DEVELOPERS

5 THINGS I LEARNED ABOUT OPEN SOURCE DEVELOPERS

Helad on December 19, 2019

Source: https://xscode.com/583/5-things-i-learned-about-open-source-developers/ I’ve spent the past 12 months working intensely with open source d...
Collapse
 
alabobriggs profile image
Alabo David Briggs

Really great article. As an open source developer let me do some code review 🙂. The article is quite long and will look way shorter if you list out the five point, I mean the title has a number attached. Also consider using gifs and images where possible to keep the article interesting you know how inpatient devs can be at times especially when it comes to reading. Nice piece man

Collapse
 
fultonbrowne profile image
Fulton Browne

Great article, as an open source developer myself, I totally agree with the compensation thing, I have made around negative 400 USD on my projects and I am testing it on a ROMed S4. to be fair no big corporations use my project and it isn't in a stable release (yet). but I have a feeling that if big corporations do end up using my project there not going to care that some dude in Oregon is trying to make an open source project for anyone to use without ads. To be clear I am not asking that any normal average user give any money and I don't want to force anyone to give money, I just wished 'they' had an idea of the effort put in to the software they get for free.

Collapse
 
attkinsonjakob profile image
Jakob Attkinson

At my previous job the company owner was surprised JetBrains dared to ask for money to use their IDEs.
When I asked for the company to pay for the license I'll use (only) while I work there I was rejected in a terrible way. It felt like my superiors were screaming "why the hell can't you use notepad, you lazy developer... Why do we even pay you?".

Again, I'm talking about IDE I thought it would be the best choice for me to develop the code my boss requested.

(for what is worth, I ended up buying my own license from my first salary and then resigned).

My point is that some companies can't even understand why some tools cost money, let alone the hard work, sacrifices, time, money and all the rest open source devs put up to produce those beautiful lines of code... (all code is beautiful, regardless if it works or not.)

Collapse
 
ajaxboy profile image
Cj

👏👏👏

Collapse
 
peledzohar profile image
Zohar Peled

Thanks, but we're not really that smart... I mean, plenty of other occupations require at least as much or more brain power - doctors, mathematics, astro-physics, the list goes on and on... Writing a program is just like writing in any language - designing code is harder but still no where near what you describe (top 1%).

Anyway, good article, thanks!

Collapse
 
laughingraven profile image
Laughing Raven

Writing code is in no way like writing in a natural language. Programming has much more rigor, both in it's design and in it's implementation. It is more akin to writing a mathematical or logical proof.

Collapse
 
peledzohar profile image
Zohar Peled

Well, yes and no. True, the rules are more rigid and there's very little room to play compared to a natural lanugage, but still, the code writing is not the hard part, which was my main point (though admittedly, not so clear in hindsight)

Collapse
 
laughingraven profile image
Laughing Raven

Having evaluated a lot of open source code as well as closed source, I also have a few observations. Open source code tends to be more poorly engineered, poorly planned and poorly maintained. I blame some of this on the abominable practice of tdd as well as agile development.

Collapse
 
asamsulfat profile image
Nyamuk

5 Things you learned but you didn't give numbering bullet ._.

Collapse
 
attkinsonjakob profile image
Jakob Attkinson • Edited

This article is soo well written that it made me feel bad for the critique it received.

Maybe the title suggested something you didn't find whe you first open it(bullet points), but if it caught your eye you should read it in order to figure out what it is actually about.

Collapse
 
vinceramces profile image
Vince Ramces Oliveros

I skim some articles that are long and did not saw 5 things he learned. Not an intuitive to read.

Collapse
 
aroman012 profile image
Alejandro Roman

He used subtitles for each thing he learned

Collapse
 
ajaxboy profile image
Cj • Edited

Great writing, you're are right. I've been there as an open source person, I did get a few compliments but that was it. Oh yeah worked on it for years 😣

Collapse
 
iamnotstatic profile image
Abdulfatai Suleiman

The article was helpful, The article is quite long and will look way shorter if you list out points

Collapse
 
mubirupatrick2040 profile image
Mubirupatrick2040

Great article, thanks for sharing..