As a freelance developer, the most common conversation I have with new clients is about copyright, licensing, and code ownership. It isn't a well understood area for many people, and many other freelancers who I talk to don't really get it, either. So let's talk.
In general, when you create something, you are automatically assigned copyright over it. This means that you have the right to determine who, when, and how the thing that you created is copied. For me, as a developer, any code that I write is automatically copyrighted to me. I can, through a general agreement or a contract gi…
I am helping a couple of friends to learn how to program, and how to build things. Working through Codecademy has helped them get a grasp of the basics of syntax and problem solving, but they pretty quickly grow bored without a real goal in mind.
This is why I tell them to build their own blog, and why I think you should too.
Let's face it, you're not going to knock wordpress off it's pedestal, nor compete with blogger/tumblr/whatever other blogging platforms are popular. It's about building something for you. Something which doesn't affect everyone else, but you can play with, show off, and le…
I'll make this short and sweet. I felt that we needed a new license. Blogfile was/is released under the WTFPL, and it's sub-project, SHITLang was also released under the same license.
I have no interest in maintaining SHITLang, and wanted to discourage people from trying to get me to look at pull requests.
Anyway, today, it is moving to the brand new license that I created (based heavily on the concept of the WTFPL): the Do I Look Like I Give A Shit Public License.
So what should this license be used for?
- You are sick of maintaining a side project
- You really don't give a shit about the project
- You …
Let's talk about how we teach new people to program.
There is a saying which I see getting thrown around frequently in the mailing lists and user groups for programming languages. Everyone knows the saying, and I used the latter half of it as the title for this post.
"Give a man a fish, and you feed him for a day. Teach a man to fish, and you've fed him for life."
I have a problem with recruiters. Shocking, I know. If you ask around developers, recruiters quite often seem to be right near the top of the list for "things which tech would be far better without".
If you're a recruiter reading this, then please don't skip straight to posting angry diatribes in the comment section - I'm happy to explain where my problem comes from, and maybe even how to fix it. If you're not a recruiter, but have run into some of the same problems, then maybe you might even want to confirm that I'm not alone here.
Let's start with a short anecdote. I was recently contacted b…