So nobody should have any legal rights to any reproducible content, for any span of time? I urge you to reconsider your position, mate. And also the fellows who upvoted this. Intellectual property as a concept means that a creative person has at least a chance of make a living out of her/his awesome stuff. Without any ip laws, the end product could be immediately after its risen popularity copied and reproduced by some enterprising gnome. Not that the money flows are not controlled by gnomes, but with ip laws the artist has a chance to earn bread and enjoy success in the rare occasions. What is completely arsewise is the improper magnitude of the enforcement of this as some parties seek, and the fact that national political entities succumb to this maddness. There are indecent things out there, but minimal ip that makea sense is not one pf the, imho. The current levels of enforcement and the level of entitelment sought by the ip holders are crazy, but that does not invalidate the concept. Its just an example what happens when legal bodies either lack the wisdom or are lured by the powerfull with shiny things.

I have a fairly good clue of what's going on since the company I work for (Tekla) got recently acquired by Trimble. Except for long term roadmap, they've pretty much left us alone (at least it seems that way to us programmers). Trimble wants to create a competetive vertical solution in the construction industry to compete with Autodesk's toolchain. Autodesk pretty much dominates the construction industry, and their ecosystem is proprietary and closed. The counterbalance to this is a developing toolchain of tools built around the IFC format which is standardized and open. Trimble already had most of the other pieces in a complete architect-to-the-construction yard toolchain except for an archictecture software, and now they have it. This means, there is now true competition in the construction segment offering information tools, and not only Autodesk and Autodesk. This sort of competition is good, people.At least so far the non-Autodesk parties try to break their dominant position with collaborative tools and an open format. Of course, what the situation will be in the future? Who knows.

This is probably due to the fact that very many young programmers are ever so keen to be in the business... Supply of labour is infinite, filled with enthusiastic young people who are inexperienced in standing up for themselves. With - lets face it - completely undefined end product and whose success is fairly unrelated to the input of the individual programmer. Thats probably why indie games sound like such a great proposition to anyone who is skiled enough to write their own code and design their own game. The first part is not the most difficult one, btw.

Seriously, F# is awesome. These course notes and code examples explain why in far more detail than I ever could. http://www.itu.dk/courses/BPRD/E2010/.

Same use case. Love my Ipad. In a wlan network Readdledoc functions as a wireless file server that you can mount as a regular drive on any os, which is exactly what a caveman like myself who uses plain old file system operations for my document management needs. The downside is the IPad's somewhat clumsy overall file management imposed by the ios.

I've been working in the sofwtare industry since 2007 in a small team (individual projects ranging from 1 to 10 persons). We've always used scrum. Mind you, not by the book but heavily modified to fit our style. Seems to work if all participants are even a bit motivated and not totally clueless about the tasks at hand.

From the pragmatic point of view, there are two issues at play here. One - how to build decent programs that are maintainable and - two - understanding how such a program actually works. If your skills lack in the former, your code is probably near-to-useless in the long term for anyone. If you lack in the second - THE HARDER PART (pardon my caps) - then you are just partaking in a cargo cult that just happens to work because someone left you the tools that luckily get you the job done. I also think the second skillset requires a lot more effort to acquire than the first.