How Larry Page Changed Meetings At Google After Taking Over Last Spring

• Every meeting must have one clear decision maker. If there's no decision maker -- or no decision to be made -- the meeting shouldn't happen.

• No more than 10 people should attend.

• Every person should give input, otherwise they shouldn't be there.

• No decision should ever wait for a meeting. If a meeting absolutely has to happen before a decision should be made, then the meeting should be scheduled immediately.

Read more: http://www.businessinsider.com/this-is-how-larry-page-changed-meetings-at-google-after-taking-over-last-spring-2012-1#ixzz1jK8m4Hva

Winners and Losers in Business Open-Source Software

Application Server/Web Server:

• Trending Up: Node.js and NGINX
• Trending Level: Tomcat and Apache HTTP Server
• Trending Down: JBoss and GlassFish

Frameworks:

• Trending Up: Rails
• Trending Level: Spring, Grails, Struts
• Trending down: (none)

Databases and Big Data:

• Trending Up: HBase, Hadoop, MongoDB
• Trending Level: MySQL, PostgreSQL
• Trending Down: CouchDB

http://www.dzone.com/links/r/winners_and_losers_in_business_opensource_software.html

Are You Making These 7 Productivity Mistakes?

Mistake #1: Cutting Back on Sleep
Mistake #2: Multi-Tasking
Mistake #3: Doing Everything Yourself
Mistake #4: Focusing Solely on Numbers
Mistake #5: Eating at Your Desk
Mistake #6: Checking Email Frequently
Mistake #7: Pushing Yourself Hard

http://www.dzone.com/links/r/are_you_making_these_7_productivity_mistakes.html

Top Ten Idea Killers in Software Development

Source:http://www.computer.org/portal/web/buildyourcareer/Nosce-te-Ipsum/-/blogs/top-ten-idea-killers-in-software-development


10. "This is good enough" 

9. "This is how it was always done"

8. "There isn't enough time to do it right"

7. "This requires core architectural changes"

6. "Management has not prioritized it"

5. "There is already a lot on our plate"

4. "Our software is very complex; we have to be careful about making changes"

3. "No one is asking for it"

2. "We have to have consensus"

And the #1 idea killer in software development is

1. "It can't be done

How to Prevent a SQL Injection Attack

Reference: http://www.dzone.com/links/r/how_to_prevent_a_sql_injection_attack.html




1. Patch your SQL server regularly
2. Limit the use of dynamic queries
3. Escape user input
4. Store database credentials in a separate file
5. Use the principle of least privilege
6. Turn magic quotes off
7. Disable shells
8. Disable any other DB functionality you don’t need
9. Test your code

Be a Better Java Programmer: A Reading List by Binu John

Reference: http://www.informit.com/articles/article.aspx?p=1757633