[LRUG] Difficult second album

[Stephen Masters]

That’s pretty much the approach taken in Martin Fowler’s book “Refactoring”, so maybe a scan of that might provide some ideas for structure. Doing a quick search for “architectural refactoring” gives plenty of results on the topic, so it may be worth taking the approach of how to implement some of those ‘named’ refactorings in a Rails application. Alternatively, it might be worth naming Rails-specific problems and proposing associated refactorings. If they don’t already exist, coming up with names could be half the fun. :)

Steve


On 28 Oct 2013, at 23:09, Mark Burns <markthedeveloper at gmail.com> wrote:

> Thanks Paul,
> 
> It's a good point, you're right. It's difficult to sketch out exactly how much information to convey and at what level to pitch it at.
> 
> I like the siren call idea. If you see pattern A, you might want to try solution B.
> Solution D is also relevant, but maybe not until you start to get C happening.
> 
> It would be good to express a few examples of well known maxims/idioms and what issues these solve. Along with situations where they may not be appropriate.
> 
> Maybe with examples simple enough that anyone can imagine the progression through into larger and more complex systems, even if they haven't experienced that progression first-hand. 
> 
> Basically, I can't teach you Thai, Vietnamese or Japanese, but I could help you learn to spot the differences between them. You can learn a few greetings and recognize them when confronting them, but you're going to need to do some self study to learn anything of value, and you'll need to live there to be fluent.
> 
> I think I'd probably want to focus more on aspects of moving away from monoliths if focusing on anything. Especially as that probably sounds closer to that title.