Skip to main content

IT Conversations: Lawrence Lessig - Re: Mix Me

While subscribed to it, I have stayed out of the Creative Commons discussions, choosing to focus on the "joy" of development - knowing I would have to get into it at some point later on.

However, I saw that Eric was giving a talk on how to make marketing for geeks more understandable and then just yesterday, I was driving home from a Montreal client visit and listened to this podcast from Lawrence Lessig given at the O'Reilly Emerging Technologies conference in March.

This talk blew me away. It puts every DRM debate into a very basic context - and the possible repercussions of recent actions by the US Supreme court are frightening. The Q&A is especially useful when someone essentially says "I need a license that says don't copy my work, but if you mess with it, that's ok with me". And the discussion that ensues.

In short - our entire society is based on remixing. We remix letters to create words, remix words to create paragraphs, remix ideas into inventions, and so on. So while no, we shouldn't be allowing the pure copying of ideas, we should certainly allow for the mixing of them.

A little similar to Donald Norman's comments as well.

IT Conversations: Lawrence Lessig - Re: Mix Me

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...