Articles tagged with #software-design (10)
What advice/rules I may give to junior developers about the Ruby on Rails app design?
This article is not only relevant for Rails developers, but also
very general. I feel that rails devs need more support here, because
Rails makes it especially hard to use magic.
Make sure to open the hood and understand how the engine ticks!
The original article where Alistair Cockburn describes
is the best intro and a good read,
no matter what year it is.
Continue reading →
This topic came up today when we discussed the #crewmeister API, and made me think.
Until I remembered that we once in a project used to use the pure
POST params, which are basically key-value pairs.
And the question also reminded me of my PHP times, there
the server-side knew how to handle a key which looks like
and builds and array. But when I ran into that problem back then
we used to use python and there we didn't have that.
There are seven kinds of coupling.
Unfortunately I missed Franziska's session at SoCraTes 2015 on this topic, but fortunately she wrote about it, make sure to also read through her commits backwards, of course :). Very nice and readable! An article "Kickstart your next project with a Walking Skeleton" she referred to, that explains the process too. While reading more and more of the [c2 wiki] I am asking myself where is the difference to a spike which Kent Beck defined as
I was about to write a "Handler" class. But I remembered that the "er" classes are not so good.