Neal Ford of ThoughtWorks chats with SE Radio’s Kim Carter about the skills required to be a successful software architect.
Redirects to legacy blog post.
Redirects to legacy blog post.
A short time ago, I was tasked with finding the right software engineer/s for the organisation I was working for. I settled on a process, a set of background questions, a set of practical programming exercises and a set of verbal questions. Later on I cut the set of verbal questions down to a quicker set. In this post, I’ll be going over the process and the full set of verbal questions. In a subsequent post I’ll go over the quicker set.
Redirects to legacy blog post.
The first thing to clear up is that TDD is not primarily about testing, but rather it forces the developer to write code that is testable (the fact the code has tests written for it and running regularly is a side effect, albeit a very positive one).
Redirects to legacy blog post.
An area I’ve noticed where engineers often forget to think about synchronization is when firing events. It seems to be a common misconception, that all that is needed to keep synchronisation, is to check the delegate (technically a `MulticastDelegate`, or in architectural terms the publisher of the publish-subscribe pattern (more commonly known as the observer pattern)) for null.
Redirects to legacy blog post.
Part two.
Redirects to legacy blog post.
Part one.
Redirects to legacy blog post.
I had a discussion with some work colleges a short while ago, around a couple of different techniques of constructing a class object. The two approaches involved in the discussion where...