Commandments of Good Code

#1

Post by zgoldberg » Wed, Jul 15, 2015, 4:09 PM UTC

Commandments of Good Code
zachgoldberg.com

Re: Commandments of Good Code

#2

Post by collyw » Wed, Jul 15, 2015, 6:02 PM UTC

These are actually quite good. I was expecting some cargo cult Agile related nonsense "always do 100% test coverage, blah blah".

Re: Commandments of Good Code

#3

Post by kylnew » Wed, Jul 15, 2015, 6:29 PM UTC

I'm down with "All (ok most) programming languages are simultaneously good and bad". I assumed it would go on to discuss Javascript, but nope. Which really goes to show how true the statement is.

Re: Commandments of Good Code

#4

Post by bradhe » Wed, Jul 15, 2015, 11:10 PM UTC

> * Key Value Stores Redis / Memcache

> * No-SQL land: MongoDB/Cassandra etc.

> * “Traditional” Schema’d SQL: Oracle/Postgres/MySQL/Amazon RDS Etc.

> * Hosted DBs: AWS RDS / DynamoDB / AppEngine Datastore

> * Heavy lifting: Amazon MR / Hadoop (Hive/Pig) / Cloudera / Google Big Query

> * Batshit crazy stuff: Erlang’s Mnesia, iOS’s Core Data

Cringeworthy to be sure.

Re: Commandments of Good Code

#5

Post by zgoldberg » Wed, Jul 15, 2015, 11:50 PM UTC

bradhe wrote: post #4

> * Key Value Stores Redis / Memcache > * No-SQL land: MongoDB/Cassandra etc. > * “Traditional” Schema’d SQL: Oracle/Postgres/MySQL/Amazon RDS Etc. > * Hosted DBs: AWS RDS / DynamoDB / AppEngine Datastore > * Heavy lifting: Amazon MR / Hadoop (Hive/Pig) / Cloudera / Google Big Query > * Batshit crazy stuff: Erlang’s Mnesia, iOS’s Core Data Cringeworthy to be sure.

Do you disagree with the point?

Re: Commandments of Good Code

#6

Post by zgoldberg » Wed, Jul 15, 2015, 11:51 PM UTC

collyw wrote: post #2

These are actually quite good. I was expecting some cargo cult Agile related nonsense "always do 100% test coverage, blah blah".

Thanks!

Re: Commandments of Good Code

#7

Post by zgoldberg » Wed, Jul 15, 2015, 11:55 PM UTC

kylnew wrote: post #3

I'm down with "All (ok most) programming languages are simultaneously good and bad". I assumed it would go on to discuss Javascript, but nope. Which really goes to show how true the statement is.

Ah! Good point! A complete brainfart on my end. Definitely should've included javascript as an example.

Re: Commandments of Good Code

#8

Post by bradhe » Thu, Jul 16, 2015, 1:47 AM UTC

zgoldberg wrote: post #5

bradhe wrote: post #4

> * Key Value Stores Redis / Memcache > * No-SQL land: MongoDB/Cassandra etc. > * “Traditional” Schema’d SQL: Oracle/Postgres/MySQL/Amazon RDS Etc. > * Hosted DBs: AWS RDS / DynamoDB / AppEngine Datastore > * Heavy lifting: Amazon MR / Hadoop (Hive/Pig) / Cloudera / Google Big Query > * Batshit crazy stuff: Erlang’s Mnesia, iOS’s Core Data Cringeworthy to be sure.

Do you disagree with the point?

1. "No-SQL land" - Most of those things are NoSQL databases? 2. ""Traditional" Schema'd SQL" - Amazon RDS isn't a database, and those are relational databases. 3. DynamoDB has effectively the same data model as Cassandra. 4. "Hadoop" isn't a database. Cloudera is a database vendor. EMR (what you call Amazon MR?) is Hadoop as a Service. 5. I don't even know what to say about the "batship crazy" thing.

Every data store has a model. Typically we classify them based on their model.

Re: Commandments of Good Code

#9

Post by zgoldberg » Thu, Jul 16, 2015, 4:14 PM UTC

bradhe wrote: post #8

zgoldberg wrote: post #5

Earlier quoted context omitted.

Do you disagree with the point?

1. "No-SQL land" - Most of those things are NoSQL databases? 2. ""Traditional" Schema'd SQL" - Amazon RDS isn't a database, and those are relational databases. 3. DynamoDB has effectively the same data model as Cassandra. 4. "Hadoop" isn't a database. Cloudera is a database vendor. EMR (what you call Amazon MR?) is Hadoop as a Service. 5. I don't even know what to say about the "batship crazy" thing. Every data store…

ah, ok, I understand your complaint. I actually agree with you, I was definitely playing fast and loose with classifications there. That said, my point wasn't about how to classify data storage systems, so much as to emphasize the fact that there are many options and that the architect should be thinking really hard about existing options before rolling their own.