IT Camp 2013
I will speak this year to ITCamp conference on 23rd of May. When I have received the invitation (thanks Mihai and Tudy for inviting me) my first thought was whether I should talk about Unit Testing or something else. Then I started to wander why do I like to talk
I will speak this year to ITCamp conference on 23rd of May.
When I have received the invitation (thanks Mihai and Tudy for inviting me) my first thought was whether I should talk about Unit Testing or something else. Then I started to wander why do I like to talk that much about it, so much that I am seen as the unit tests guy by my colleagues, all the projects I’m involved in have a high accent on unit tests, and I even receive birthday cards with: “no unit tests? You’re doing it wrong!”. There are definitely other interesting subjects to talk about. Then I realized it. Unit testing was the only technique with which I managed to persuade one of my teams to write good quality code, which allowed us to easily change it. All the talks about Design Patterns, programming principles didn’t do it. Unit testing did it.
Therefore, this year I will talk at ITCamp about how to drive your team towards quality code, by writing good unit tests. Today I have started to put on paper some ideas on how to structure and build my talk. I have few more free Fridays to refine it and make it a good talk in which to show my view on how to achieve good code and why would you want that. I hope to see you there!
We share our insights and experiences from working on client projects and teaching developers.
Our articles blend technical expertise with real-world challenges, offering a unique perspective on Code Design.
For us, Code Design means structuring code to ensure predictability and making it easy to manage and adapt long after it's written.
Why Programmers Should Challenge the Stakeholders
Have you ever worked on a state of the art programming project? And then a new requirement arrives, it's implemented and suddenly you're working on a legacy project?
Migrate to Ghost 1.x on Azure
You might remember that I am running this blog on Ghost self hosted on Azure. I wrote about how I've migrated from Wordpress in an older post. Now, I migrated to Ghost 1.x, and in the process I configured a better dev environment for my theme and auto deployment to an App Service from GitHub
Decide between In-Process or Inter-Process Communication at Deploy Time - Part 3
This is the last post from the series on how we could implement a design that allows to decide only at deploy time how two services communicate: in process if they are deployed on the same server or inter-process if they are on different machines. The first post shows where
Decide between In-Process or Inter-Process Communication at Deploy Time - Part 2
This post continues the previous by giving an example on how we could implement a design that allows to decide only at deploy time how services communicate: in process if they are deployed on the same server or inter-process if they are on different machines. If you haven't
Decide between In-Process or Inter-Process Communication at Deploy Time
After a long vacation in October last year, followed by some intensive work at MIRA and InfiniSwiss, now I can make some time to share some more design ideas that I have implemented along the years. I thought to resume blogging with showing how we could design for something which
AppBoot Library
AppBoot is a generic .NET application bootstrapper, we at iQuarc, have put on GitHub a while ago. It started few years back when we were about to begin developing a large enterprise application. Back then, we wanted to use the Unity Container for dependency injection, but we liked the way