From 6a438a329c9d598d31cf99c2ac65855553a0dbbe Mon Sep 17 00:00:00 2001 From: JoseĢ Mota Date: Tue, 26 Jun 2012 08:22:32 +0100 Subject: Update latest post. --- _posts/2012-06-26-extract-your-business.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to '_posts') diff --git a/_posts/2012-06-26-extract-your-business.markdown b/_posts/2012-06-26-extract-your-business.markdown index 7c3da32..8f00708 100644 --- a/_posts/2012-06-26-extract-your-business.markdown +++ b/_posts/2012-06-26-extract-your-business.markdown @@ -41,13 +41,13 @@ to defy standards by adopting a different solution for a certain problem: any other database; * Perhaps you have a different way of persisting data like Hibernate (if you're using JRuby); -* You want to improve performance by tweaking the frameworks' defaults. -* How about extracting your app into a JSON API and go heavy on Javascript?. +* You want to improve performance by tweaking the frameworks' defaults; +* How about extracting your app into a JSON API and go heavy on Javascript? Change is always imminent. I learned that the hard way and Ruby now gives me confidence upon change. TDD is an awesome leader that _accepts change as a reality and no longer a challenge_. Also, it provides guidelines to better app -design and that increases maintainability. +design which increases maintainability. The framework should only support common tasks, that's why it's called a framework. All the MVC paradigm, boilerplate, persistence, helpers, templating -- cgit v1.2.3-54-g00ecf