Contents tagged with Test Driven Development
-
Hiring for TDD .NET engineers in Washington DC
Thycotic/LogicBoost is hiring for .NET engineers at our office in downtown Washington DC. This is a team that has been doing Test Driven Development and Pair Programming since 2004 (very mature agile team). This is an amazing environment to work with great engineers in a team-based atmosphere (free lunches on Wednesdays, loads of personal development and learning is at our core).
-
Pair Programming and Pandemics
Pouya has posted about the dangers of illnesses when Pair Programming on our team blog.
-
Stinky PartialMocks?
Jimmy has posted about PartialMocks on the team blog. This has been a recurring discussion on our team and it is worthwhile thinking careful about whether to use PartialMocks and if so, what is an appropriate usage …
-
Refactoring logic from an ASP.NET page
Kevin has posted about refactoring some simple logic from an ASP.NET page and breaking it out into a separate class (Single Responsibility Principle) to make the code more maintainable.
-
SRP with the DC ALT.NET User Group in Alexandria, VA
Last Wednesday (3/25/2009), I presented at the DC ALT.NET User Group in Alexandria. Thank you to the groups organizer, Matt Podwysocki for inviting me.
-
Speaking on Refactoring at RockNUG in March
I will be presenting on Refactoring in C# at the Rockville .NET User Group (RockNUG) on March 12th 2008 at 6:30pm.
-
Secret Server 4.0 has shipped!
-
Do you have what it takes to be a Thycotic TDD Developer?
Thycotic is gearing up for a new product development cycle and we are looking to grow our team of passionate test-first developers. Our team is one of the best places to learn and improve your agile development skills. -
Refactoring example in C# and VB.NET
Our very own Bryant Smith has revamped his conversion of Martin Fowler's refactoring example (originally in Java) to now cover both C# and VB.NET.
-
Whitespace is a code smell
Do you space out your code so there are line breaks between the pieces of logic? Why do you think this is necessary? Typically this is done to separate chunks of logic so that they can be easily distinguished. If it is a complicated enough chunk, then it may even make sense to put a comment at the top of the chunk. At this point, the Agile police will jump on you and tell you to turn your comment into a method name and perform an Extract Method refactoring. This is great practice (fellow Agile police member here!) and it makes a lot of sense since it abstracts the concept and makes the code more self describing.
Thycotic