Re-use, improve, contribute – and when someone else is clearly doing a better job, let go.
Free to play
What we’ve seen pretty consistently is that when something moves from a traditional monetization model to free-to-play, you see about a 10x increase in your audience and about a 3x increase in your gross revenue.
Our customers have defeated us… They’re building content that’s just as good or better than what we’re building, and they’re building it at a spectacular rate… We have people who are making $500,000 a year selling content in the Workshop.
[Read More]
Big balls of mud
If you are writing code that may still be in use a year later, balance the convenience factor against the difficulties you will inevitably suffer later.
Large scale software development is unfortunately statistical.
UML is a job smell
It was first added to the list of OMG adopted technologies in 1997
"The Most Dangerous Code in the World"
Our main conclusion is that SSL certificate validation is completely broken in many critical software applications and libraries.
(emphasis original)
Vulnerable software includes Amazon’s EC2 Java library and all cloud clients based on it; Amazon’s and PayPal’s merchant SDKs… Chase mobile banking… any Android app that uses Pusher API to manage real-time messaging (for example, GitHub’s Gaug.es), clients of Apache ActiveMQ servers…
Instant messenger clients such as Trillian and AIM do not validate certificates correctly, either.
[Read More]
"I wish I could never link against a closed library ever again."
via Jeff Atwood, in reply to this:
This is an honest question: Having been in IT and software development for over a decade, I have never encountered a problem that required me to look at the source code. As such, I’ve never really understood the open source movement. I can’t imagine a scenario where the software I am using, the same software used by hundreds of thousands of others, would be broken to the point where I had to go into the source and fix it.
[Read More]