Geeky Jokes

Q: How do you tell an introverted computer scientist from an extroverted computer scientist?
A: An extroverted computer scientist looks at your shoes when he talks to you.

Q: Why do programmers always mix up Halloween and Christmas?
A: Because Oct 31 == Dec 25!      

     

Opposites attract...
Wife: "I'll be right back!"
Me: "I'll be left forward"

 
Software is like sex: It’s better when it’s free.

Unix is user friendly. It’s just very particular about who its friends are.




and finally a Java Joke......

Q: Why do Java programmers wear glasses ?
A: Because they don't C#

Quote of the month

I don't really have a "quote of " this or that but here it is anyways...   If you have to think hard to figure this out you are a point-in-case.

Caveat Emptor: The cost of software
maintenance increases with the square of
the programmer’s creativity.

First Law of Programmer Creativity,
Robert D. Bliss, 1992

micro service - a new development paradigm?

Succinct description of what makes up a mircro-service. 

• Each application only does one thing
• Small enough to fit in your head
• Small enough that you can throw them away
• Embedded web container
• Packaged as a single executable jar
• Use HTTP and HATEOAS to decouple services
• Each app exposes metrics about itself 

from this presentation 

50 servlet interview questions:

See it here

Continous Delivery

Great quicky intro...

http://fernandorubbo.blogspot.com.br/2012/07/continuous-delivery-why-you-should-be.html

Agile for the lone developer

Practices adopted from Agile Teams:

• Create clearly defined, small chunks of work (i.e., user stores)
• Hold daily “standups” before starting work each day
• Keep track of how long it takes you to do tasks and how many tasks get completed in a sprint
• Communicate frequently with the client, to provide regular updates and product releases and solicit feedback and input

Common Red Flags in Java Development

Java developers with few years of experience can quickly figure out the description for the below red flags.

• Use of == (rather than .equals) with References
• Use of .equals (rather than ==) with Enums
• Magic Numbers and Literal Strings
• String Constants
• Use of Java's "Goto"
• Depending on Scope for Appropriate References of Variables of the Same Name
• Mismatched equals(Object) and hashCode() Methods
• Lack of Javadoc Comments
• Implementation Details in Methods' Javadoc Comments
• Comments in the Source Code
• Implementation Inheritance (extends)
• Dead Code
• Commented Out Code
• To-Do Statements
• Compiler Warnings and IDE/Tool Warnings/Hints/Findings
• Compiler Warnings and IDE/Tool Warnings/Hints/Findings Turned Off
• Too Clever / Science Fair Projects / Over-Engineered / Premature Optimization               

For succinct description see the original post