Permalink
Browse files

Merge branch 'master' of github.com:newhavenrb/railsconf2012

Conflicts:
	Sustainable-Productivity-with-Rails.md
  • Loading branch information...
benjaminoakes committed Apr 24, 2012
2 parents 7ae305f + 3ab0401 commit 917a3638af9608ba9f8b19bcebc6ddef462d2e08
Showing with 78 additions and 1 deletion.
  1. +51 −1 Sustainable-Productivity-with-Rails.md
  2. +27 −0 Ten-Things-You-Didn't-Know-Rails-Could-Do.md
@@ -83,6 +83,56 @@
* Language shapes the way we think and code
* > Follow these principles and you'll find your code remains flexible, easy to change, and fun to work on, ten years from now - SOLID OO Design, Sandi Metz, Gogaruco 2009
+### @ZachMorek
+
+* How do we keep being productive, after the project begins aging
+* Rails is not optimized for sustainable productivity
+* Prototype - first few iterations, rails is perfect for this
+* Your application - many many iterations
+* Easy
+* Simple
+* Rails is easy, not simple. Complexity of interleaving parts
+
+### Data
+
+* Data that lacks integrity are harder to understand
+* `validates_uniqueness_of`
+* Rails provides no solid way of uniqueness exceptions
+* `has_one`
+* Exceptions in this race condition
+* Stranded records on create/delete at the same time
+* High risk of data corruption
+* Rails does not suport database constraints
+
+### Code in the small
+
+* Reification, make something abstrat0 more onccrete or real
+* How classes fit in should be documented, that code can't speak for itself
+* Answer important questions, should it be restarted, does it have any downstream impacts, is that important
+* Consistency is a form of documentation. Multiple implementations of the same thing mean developers start asking quesitons instead of doing something more useful
+* Stupidity multiplies (99% effective developers, 10 developers...)
+* github/square/cane forces you to look at ugliness of code before commits
+
+### Code in the large
+
+* Define the relationship between our app and the rest of the world
+
+* Dependency on 3rd party code should go thru an interface that is shared
+* Thin layer in between. Ex: `user_cache` instead of `REDIS`
+
+* Article, Draft, Published
+* Using an aggregate
+
+* Integration test - controllers
+* Functional test - controller
+* Unit test - model
+
+* Suggestion...
+* Acceptance - whole system
+* Integraiton - code against code
+* Unit - do our objects do the right thing and are they conveninet to work with
+
## External Links
-* [Some related website](http://www.example.com/)
+* [Cane](https://github.com/square/cane)
+
@@ -383,6 +383,33 @@ ensure EVERYONE learned something from the talk.)
Slides are coming online, at http://speakerdeck.com/u/jeg2
+### @zachmorek
+
+42 things you didn't know
+
+On Rail 3.2.3
+
+1- Friday hugs
+
+Rails application in one File
+TODO / FIXME / OPTIMIZE - rake task
+Sandboxing console
+Non WEBrick Servers... `rails s thin`
+Tap into config
+
+rake db:migrate status
+User.uniq.pluck(:email)
+Event.group.count
+
+Full text search in postgres
+
+Different database for each user
+Atomic file writing - `file.atomic_write("#{id}.txt")`
+Deep merge of hashes
+someHash.except(:user\_id)
+Erb comments
+
+
## External Links
* [Friday hugs](http://fridayhug.com)

0 comments on commit 917a363

Please sign in to comment.