Fuck It Principle

June 11, 2008 § Leave a comment

In software development, being able to say fuck it, and not implementing the not-so-important features is a good thing.

By saying Fuck It(TM):

  • There’s less code to debug.
  • There’s less features to unit test and functional test.
  • Security schema protects less things.
  • There’s less complication (in an already complex application). See: Feature Creep
  • Deadline does not get pushed further and further.
  • It prevents a decently good idea becoming stupid, by having too much features.

As a reminder, I must never ever attempt to add too much Cruft.

Fuck It is more or less similar to YAGNI, as 1 reader pointed out.

Hope this post can be a helpful reminder for readers as well.



Tagged: , , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

What’s this?

You are currently reading Fuck It Principle at RAPD.


%d bloggers like this: