Development Time vs. Flexibility vs. Security
Unless you are willing to sacrifice a lot of time to make an application flexible AND secure, you will have to choose one or the other. In this example, I compare Myspace profiles and Facebook profiles.
Myspace offers very much flexibility for users on their personal profiles. Unfortunately, they chose to allow users to embed HTML code, which opened the door for countless security violations. They saved development time at the expense of security.
On the other hand, Facebook left users with fewer options for their profiles. Therefore, they insured security, but saved development time at the expense of flexibility.
Fast-forward a couple of years to Facebook’s release of their application platform. This time around, they sacrificed development time for a combination of flexibility and security.
More From Brainfuel
Brainfuel Recommends
- Community vs Fan Club (Aaron Post)
- Ruby Time Limitations (Millarian)
- The Allegory of Time Investment (Brian Shaler)
![Recommend [ChrisTingom: Brainfuel]](http://s3.amazonaws.com/arkayne-media/img/logo-recommend-us.png){kind=logo}
Checkout Marc Andreessen’s analysis of the Facebook Platform. Fascinating stuff.
The previous Comment was posted on June 19, 2007 at 12:01 pm
Wow, that’s a crappy chart, Brian.
The previous Comment was posted on June 19, 2007 at 4:47 pm
I have to agree, Chris. It’s definitely not an awesome graph.
The previous Comment was posted on June 20, 2007 at 2:26 am