Meanwhile I was reading GOOS I realised about something painful: starting a project hurts. In your daily job, it’s quite likely that you have to work in some brownfield project. Even if you’re lucky enough to be assigned into a greenfield one, starting time will be an small part of project whole life.
Here is when frameworks come to rescue. With promises of fast prototyping using “Convention over Configuration”, frameworks like Spring, Angular o Ruby on Rails will make your life easier when starting your project.
It’s not my intent putting every existing framework into the same bucket, or to diminish the merits of them, but lately I’m not really keen into framework mindset.
So, If you decide going with a libraries, more modular approach, bear in mind that the starting time curve will be higher. Depending on your language/platform there are several ‘accelerators’ to help you:
- If you use Maven as build system you can use one the available archetypes to generate some skeleton for your project.
- Through Yeoman generators you can easily create a prototype of angularjs, backbone or any mvc client, backed by different apis.
- Typesafe activators allow you spiking and exploring Scala and Java technologies like Akka, Play or Spray.
However, as discovery and learning tool, those ‘accelerators’ are awesome. They provide you a running app that you can inspect, debug or whatever without the noise and subtleties of a big project.
Why did GOOS make me think about that? Because writing first an end to end test could be so complex if you don’t really understand your system. Once, @ignasi35 told me:
If you can’t test that bit, you can’t reason about it, so it shouldn’t go into production.
(more or less, it was an informal conversation years ago ^_^ )
To be honest, even if you understand your system, writing an end to end test could be plenty of surprises, so it’s better if we found those as soon as possible.