Continuous Rewriting - Revision history

Douglassquirrel: /* How? Theory */

2013-09-28T15:40:08Z

How? Theory

2013-09-28T15:38:54Z

Continuos Rewriting: added link to the similar session from last year

2013-09-28T15:35:30Z

How? Theory

2013-09-28T15:26:45Z

Puzzle: created section

2013-09-28T15:15:35Z

How? -Theory: fixed title

2013-09-28T15:15:01Z

How? Practice

2013-09-28T15:08:22Z

How? Practice: added section

2013-09-28T15:04:22Z

How? -Theory: mentioned factplace

2013-09-28T15:01:24Z

How? -Theory: added section

2013-09-28T14:56:21Z

added "why" section

@@ Line 26: / Line 26: @@
 If a piece of software (for example Factplace) has several components in one language with one architecture, single small components (for example, component A) could be rewritten in different ways or languages. The slide shows how component A is implemented in two different languages (A and A').
-(Jason promised to add two links here.)
+(Jason promised to add two links here. One is http://backstage.soundcloud.com/2012/08/evolution-of-soundclouds-architecture/ )
 (Squirrel thinks the links are http://www.slideshare.net/mobile/pcalcado/from-a-monolithic-ruby-on-rails-app-to-the-jvm and http://www.infoq.com/news/2013/05/dystopia-as-a-service .)

@@ Line 1: / Line 1: @@
 = Continuos Rewriting =
-CITCON Europe 2013 4:30-5:30 pm topic.
+CITCON Europe 2013 4:30-5:30 pm topic. See also [[Continuous rewriting]] session from CITCON Europe 2012 Budapest.
 == Why? ==

← Older revision		Revision as of 15:35, 28 September 2013
Line 26:		Line 26:

	(Jason promised to add two links here.)		(Jason promised to add two links here.)
		+
		+	(Squirrel thinks the links are http://www.slideshare.net/mobile/pcalcado/from-a-monolithic-ruby-on-rails-app-to-the-jvm and http://www.infoq.com/news/2013/05/dystopia-as-a-service .)

	== How? Practice ==		== How? Practice ==

← Older revision		Revision as of 15:26, 28 September 2013
Line 34:		Line 34:

	== Puzzle ==		== Puzzle ==
		+
		+	How to find opportunities (paid or open source) where he could exercise continuous rewriting.

@@ Line 19: / Line 19: @@
 Similar to pair programming, one would invest some time in continuos rewriting, but there are benefits.
-== How? -Theory ==
+== How? Theory ==
 (Insert slide.)

← Older revision		Revision as of 15:15, 28 September 2013
Line 30:		Line 30:

	The speaker showed Whooshingby web application that has a slider which determines how much Ruby or Python code the application uses.		The speaker showed Whooshingby web application that has a slider which determines how much Ruby or Python code the application uses.
		+
		+	How to do it? Find some time every week, find a quiet piece of code (that is not changing a lot at the moment) and rewrite it.

	== Puzzle ==		== Puzzle ==

← Older revision		Revision as of 15:08, 28 September 2013
Line 28:		Line 28:

	== How? Practice ==		== How? Practice ==
		+
		+	The speaker showed Whooshingby web application that has a slider which determines how much Ruby or Python code the application uses.
		+
	== Puzzle ==		== Puzzle ==

@@ Line 22: / Line 22: @@
 (Insert slide.)
 == How? Practice ==
 == Puzzle ==

← Older revision		Revision as of 14:56, 28 September 2013
Line 1:		Line 1:
		+	= Continuos Rewriting =
		+
	CITCON Europe 2013 4:30-5:30 pm topic.		CITCON Europe 2013 4:30-5:30 pm topic.
		+
		+	== Why? ==
		+
		+	Business people find smart people that write a lot of crappy code fast. The code does the job done, but it really needs to be rewritten. If you have read Joel Spolsky's blog post on how completely rewriting the code is really really (really) bad, then you know it is not what needs to be done.
		+
		+	The speaker found himself several times in a situation to start working on a project that is in a "needs rewrite desperately" mode. What if we could rewrite continuously?
		+
		+	Every week, even if the code is not broken, we rewrite a piece of code. After a while, all code base will be rewritten. We might not use the rewritten code.
		+
		+	One has to invest a amount of time to do that.
		+
		+	You can rewrite a piece of PHP application in Ruby, another piece in Python, and end up with an application that is written in three languages.
		+
		+	If you rewrite, you end up with better code and you understand the code better.
		+
		+	Similar to pair programming, one would invest some time in continuos rewriting, but there are benefits.
		+
		+	== How? -Theory ==
		+
		+	(Insert slide.)
		+
		+	== How? Practice ==
		+	== Puzzle ==