Open source software is a very interesting thing and I love partaining in it beacuse it's quite simply free experience and learning to become better at what I do. A wonderful deal. It is very understandable that big corporations and some others aren't for open source adn are in fact very much against it. One has to agree, the job of youth is to rebel and the job of the big and powerful is to prevent rebellion.
Having an open source project or two myself I was beginning to look into the licensing part of it. There are obvious problems with GPL as it is a viral license in that it spreads and spreads much like herpes. Every time a project kisses another they instantly both have herpes.
However there are many instances in my own use of my own projects where I directly violate GPL due to deals struck with clients in order to be paid for my work. I am after all developing something for a well defined client according to their specifications and needs. Even though I am allowed to eventually release this into the wild they do not want me to do so immediatelly.
Projects are very difficult to develop when everything has to be buitl from the ground up, so I have some building blocks ready. Due to my own inexperience these are GPL'd and thus potentially dangerous. So far I have gone against the license in order to avoid too much danger, but this is wrong. What is there to do other than find another license you might ask? See, the problem is there are many licenses and all almost completely nonunderstandable to me because they're filled with lawyer garble beyond my comprehension.
The answer is thus to create my own license to fit my needs, but to do this I need someone to put it in lawyer speak. Those somethings cost a lot of money. Therein lies the problem.
Continue reading about LIcense
Semantically similar articles hand-picked by GPT-4
- <insert deity> bless opensource
- I am not an entrepreneur, I am an indie web developer
- Why I only work with startups
- Why you should never write a book in .doc
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️