By estherschindler
via blog.smartbear.com
Published: Feb 28 2013 / 13:09
It’s all well-and-good to suggest that developers, especially on Agile teams, work with end-users to find out what they want the software to do. It’s another thing to get useful information without the aid of mind-reading. Here's how to interview a non-responsive informant and come away with what you need.
-
Inject Controller Libraries Dynamically at Runtime in ASP.NET Web API using Custom Assembly Resolvers
-
Following up on the Design Guidance for Windows Store Apps
-
RavenDB & the magic beans by Ayende Rahien (Podcast)
-
Pre-Process your images with promises
-
Web Performance APIs Rapidly Become W3C Recommendations
-
C# Performance Benchmark Mistakes, Part Two
Add your comment
Voters For This Link (16)
-
estherschindler -
Baustin213 -
Adam_Barker
-
ryanaxford
-
sv117926
-
DJMattybeatz
-
bakercom1
-
roblimo -
rsmiller
-
golku
-
ldh_90
-
pertra
-
mswatcher -
Martyr2 -
hegger
-
agrocks
