Tinkerers as a source of adding value...

Going after people that tinker with products has been proven to be impossible. They always find a way to make whatever product they choose to tinker with, work in ways that the original manufacturer or producer never intended it to do.

In some cases, they actually make it work better than it did out do the box.

So, why waste resources going after those tinkerers when they could be used of a source of knowledge and hands on experience to make those products better. The value that they bring to the table, is the insight they have to see how they can make things work better. Or, to add functionalities that for one reason or another the original creator didn't think of.

Shooting them down is a case of shortsightedness. Tinkerers are an asset, since they have all what it's needed to help you accelerate the development of your product in a much faster way. And the feedback they give back is, more often than not, more useful than the feedback of the average user.

Not only that, they can be directed more easily to a goal. If they believe in that goal, they can do great things for your product.

Bring them in, let them do their magic. You'll be surprised by the amount of value that they bring in.

Reach out to your community of users...

I can't find a reasonable explanation on why software companies won't open themselves, and seek to use the experience or expertise of the people that form the community of users.

They are losing more than what they could be winning by keeping them out. Not only on profits, but most importantly on expertise that they could tap on to make breakthroughs that are difficult to get from people working in the company itself.

Mainly because people on the outside have a different view, and can bring it to the table. Users can see things than developers inside can't, since users have a completely different viewpoint. From it, they can see things that insiders can't just because they are in a position to actually see that part of the work flow.

Not interacting with the communities that use your software can lead you too loose vital insight on how to better develop it. Instead of trying to cut people from making any change to the software, be the one who leads those efforts and make them be done in a way that's useful for the whole community of users.

If you do so, then you can focus on the core functionalities of the software while making it more safe and robust. Be the one that sets the standards of what it takes to develop add ons or build capabilities that you are not interested or the majority of the users don't want to have.

If you do, you'll find that the resources of your company will be used more efficiently. And the community that builds around you, will take care of those things that you can't take care off for whatever reason.

Done right, it's a win-win solution.

Begin to add value...

I've wonder often when companies will stop complaining about how others do things the same way they do, and start competing with each other by adding value to the products they bring to the market.

As a whole, we should be focusing on building free and open standards on which we all can work on and modify as we want without fear of doing anything illegal. By doing so, both companies and individuals benefit from having a platform that isn't dependent on the wimps and fortunes of a single player or vendor.

By having a free and open standards, there will be true freedom to choose that software or service that best suits our needs without having to worry about if the software will actually work.

This will open companies, and other vendors, to actually work on adding value to their  software. To make their software work better, or do things in a certain way that better suit the needs of their clients. They'd be able to really focus on making great products to their clients, and to work on giving a better service to users of their products.

What's the use of having the best and greatest standard, if it doesn't work as the users need it to work or it doesn't really add any value to work of the people who use it.

I really want, and love to see, vendors competing with software that truly add value to the work of their users. All the while working on free and open standard, to which we all have access to study and add value too.

If we work together, the added value should come sooner rather than latter.

Why I made the move to Linux...

Along the reason I've moved to using Ubuntu as my OS, is that on Windows and Mac I felt that the path they are taking is one on which I had to take whatever Microsoft and Apple wanted to give me.

While on the Linux, I had the choice to pick the distro which configuration better suited what I need and want on my desktop. And in my case it was Ubuntu, since it fits my needs and how I expect my OS to work. On top of that, Ubuntu is a lot more stable than Windows ever was and far easier to configure and use.

My machine is also faster to startup, and to load the software that use. While on Windows 7 I had to wait about 5 minutes for it to start, with Ubuntu it takes about 2-3 minutes to get there. And I use the same machine, so it's a question of how the OS loads.

Not only that, important update and patches on Ubuntu come regularly. Which help keep my system running safe and keep making my computer work better, while all the problems I've come across have been hiccups that where easily fixed with a quick Google search.

On the year I've been using Ubuntu on the daily basis, I haven't come across a mayor problem with it.

Therefore, I highly recommend Ubuntu to everyone who wants to run a safe and stable OS. Specially that just works, and you want to be free from impositions from third parties that believe that they know better than you. With the added bonus that it's really easy to use, and you don't want to get your hands too dirty with on the technical side.

Changes need to be made post haste..

I feel appalled with the idea of even thinking that copyrighting APIs can be a good idea, even if they are just suggesting it.

After all APIs are a set of naming and structure frameworks used to code commands to an intended for a piece of software. Without this command, most software wouldn't run correctly making it worst than useless.

Since the coding certain commands so that the software responds on a specific way, is basically the same every time you have to issue the said command many APIs end up looking pretty much the same way.

Add the fact that when you are coding for the same platform than many others, you're using the same naming and structures frameworks. So, the odds are pretty good that someone already used your API in someway or another to solve the same problem. If that person was able to copyright that particular API, everyone who follows is going to infringe the copyright no matter what they do.

This would make making any new product or service basically inviable, since you can't solve any basic problem without having to pay royalties if the copyright holder decides to license the API to you. If he decides you're a threat, and denies you the use of it he could legally close you by using the copyright law as a weapon.

If governments are really concern to help small and medium companies compete, they need to make sure that copyright and patent laws can be used as a tool to drive them out of the market by bigger companies have demonstrated they'll do so without a second thought.

Let the companies with the best products and services win, not the ones with the most money to pay for the best lawyers.

Embrace tinkers...

I've been wondering for sometime now, how long will take for many companies to stop trying to keep people from tinkering with the software and hardware they produce.

It would be most useful for them to harness the work of the tinkers that work on their products, and use that work to further the development of those products. They should be working more like the lead of a greater project, by doing so they can receive benefits that would be otherwise lost.

Other benefits from embracing the work of tinkers, is that they'll be better salesmen for their products because they know them just as well as the engineers and designers who originally work on the project. And the tinkers are more trusted by the people around them, than a representative of the company would ever be.

Not only that, tinkers can actually help to spot and fix any kind of problem that wasn't seen during the development process in a more effective and timely manner. Thus freeing in-house developers to do other functions that require better equipment, or is more important to the company.

Tinkers are not an enemy, they are a valuable ally that can give a lot more back that he or she can take away.

Don't be afraid to tinker...

Linux, and FLOSS in general, have benefited a lot from people tinkering around the software they use to make it work as they want it to.

From time to time, great things come from those changes. Some don't bring important things, but actually lead to other things that end up being great. The important thing is to actually tinker on the things you believe you can improve, or change to get to work in the way you think they should.

The reality is that it's really hard to gauge the impact of any particular change, but we won't ever know if that change isn't made. And it's always better to know that the change doesn't work, than not knowing that it does.

And who knows, it might not work as you thought it would and still be of great use. That's why it's important to try out the changes you think might work.

It's also important to share and exchange ideas with others that work in the same area that you do, they might have ideas or technical information that you might find useful and put to use to be better able to work on what you love to. Also, by doing so the scope of your project might grow or have a better chance to actually workout as you want it to.

By tinkering your software, and hardware, to make it work or look as you want it to there are a lot of things you can learn. Not only that, there are a lot of good friend to be made by working in projects, or sharing your results, with others.

So, go and tinker away at your hearth content.