A Programmer's List of Lists

Language popularity (Tiobe)  (Java, C, C++, C#, Objective C, PHP, ...)

Linux Flavors (Mint, Ubuntu, Fedora, Debian,.............., RHEL,....)

Free Programming EBooks (courtesy Hacker News)  (Thinking in Java, The Cathedral and the Bazaar, etc.)

NoSql Databases (Hadoop, MongoDb, MemCache, etc.)

Bits of Programming Advice ((Don't make objects that end with 'er'.))

NoSQL Flavors

On my TODO list: try two of these. 

Big Table or Wide Column Store

-          Hadoop/HBase (Facebook)

-          Cassandra

-          HyperTable (Google)

-          Amazon SimpleDB

Document Store

-          MongoDB (JSON documents) (FourSquare)

-          CouchDB (JSON documents)

Key-Value

-          Amazon DynamoDB

-          Memcached

-          Oracle Coherence

-          Apache Voldemort (LinkedIn)

XML

-          MarkLogic

-          Apache Xindice (retired)

PLoP Links And Other Pattern Links

PLoP = Pattern Languages of Programs, a group that collects good patterns like some people collect baseball cards.
Some interesting links:
Books On Patterns
Patterns Catalog
Some Random Interesting Patterns:
Avionics Patterns
Scrum Patterns

Other Links:
Pattern-Oriented Software Architectures
Patterns & Frameworks for 
Concurrent & Distributed Systems - Patterns For Real Time Avionics Messaging in UAV
Great Article on Inversion of Control Layer
Variability Patterns (Software Product Line)

Thought Leaders

Kent Beck
Bruce Eckel
Martin Fowler
Uncle Bob Martin
Joel Spolsky
Scott Ambler

Java And Eclipse Useful Tips and Best Practices

Java And Eclipse Useful Tips and Best Practices

The Joel Test

Do you use source control? Can you make a build in one step? Do you make daily builds? Do you have a bug database? Do you fix bugs before writing new code? Do you have an up-to-date schedule? Do you have a spec? Do programmers have quiet working conditions? Do you use the best tools money can buy? Do you have testers? Do new candidates write code during their interview? Do you do hallway usability testing? Joel Spolsky's Joel Test (How Good is your software team)

Software Architecture Patterns and Best Practices

• The fundamental rule is that all code can depend on layers more central, but code cannot depend on layers further out from the core.  In other words, all coupling is toward the center.   This architecture is unashamedly biased toward object-oriented programming, and it puts objects before all others. Onion Architecture