Skip to main content

Don't Print

Dont print that email/document. Its not a request. Its a real, honest, warning. Dont do it. You must be really out of this world, or of the last millenium, or simply a silicon dimwit to use that printer instead of using it electronically.

dont_print_emailsIn the first place, you are consuming (carelessly) yet another enviromentally expensive resource. No, not the paper. The Tree (do you know how long it takes for a tree to be ready for paper manufacturing? and all those chemicals used to make it?). On the other hand, it is much easier to search an electronic catalog than manually looking up a drawer full of business requirements in hard copy. Instead of printing those comminucation emails, jira tickets, corporate bills, use case documents (and the list goes on..) - scan them / store digitally. Many of these start off as electronic documents. Use those. You can make it worth even more by using Google Desktop search or similar tools. Much worse is printing books/study material for *reference*. Are you kidding? For *reference*?? BUY that book (Bookmakers are many times envorimentally friendlier, than printing in a brand new A4 papers from staples), if you cant read it off the monitor . Again, searching is so much easier, quicker and productive, if you are looking up the digital version.

You really have to print? REALLY! Chances are you DON'T - REALLY. Look for alternatives. Make that *looking* a habit. Tell others. Stop them from using the printer. Shoot them if you need to (Ok, that - I am kidding..). If you are a manager, encourage people to go green. Use no (or minimal) paper. It saves you a ton of money. Better yet makes you a pleasant tree hugger.

If you STILL have to print (you have to read this all over again :D)-
  • Use both sides of the paper.
  • Use that paper used on only one side.
  • Make use of print preview and reduce errors.
  • Reduce font size, spacing, extra line breaks - feel victorious even if you save one page!
  • When you are done put that in a *recycle* bin.

I hope this makes you a better user of paper. If you find this a little harsher than you thought, keep that rolling everytime you go near a printer :P

Read more about this revolution

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>