The other side of the moon We’ve all heard about the Test-Driven Development, but how about the reversed approach – Developer Driven Testing (DDT)? What can we gain and what can we lose by writing our code before writing tests? Let’s explore this approach to software development, which implies setting up QA processes without a QA team.
All code is guilty until proven innocent Test Driven Development (TDD) is a software development process in which a developer writes test of their code before writing the code itself. The test-first concept encourages repetition of very short development cycles with the writing of just enough code to pass the test.
The Disruption Technology disruption has already disrupted. Everything has changed with the pace of digital revolution, from our everyday lives to the way how we work and code. The fast moving and diverse environment of web development is no exception. During the recent years everybody in the web community speaks about the MEAN stack. What are they discussing?
In recent times, software development has become all about frameworks. Why? The main reason is that creating from scratch such a sophisticated program as a web application may take a lot of time and efforts. Don’t take it wrong – I mean not the “Hello World” type of apps but those that provide excellent user experience and are ready for production.
There’s a bunch of the most discussed questions on the Internet, and one of them certainly is: “Django vs Rails: which one to choose?”. Both of them are open source web frameworks that provide all the necessary functionality for developing web applications, which relies on MVC model (in Django, “view” part is placed in templates, though).