Monday 15 August 2011
tips
It’s admittedly rare, but sometimes you see something on Twitter that’s worth preserving and repeating …
“Lesson learned, forgotten, and remembered: Don’t ask users what software should do, instead ask them what problems they’re trying to solve.”
Why is it we so often do the former? Probably because it’s easier!
| Next Post | |||
| Easier property validation with dynamic in C# 4 27 Aug 2011 | |||
| Prior Post | |||
| Semantic Versioning 28 Jul 2011 | |||
| Related Posts | |||
| Browsers and WSL 31 Mar 2024 | |||
| Factory methods and functions 05 Mar 2023 | |||
| Using Constructors 27 Feb 2023 | |||
| An Inconvenient API 18 Feb 2023 | |||
| Method Archetypes 11 Sep 2022 | |||
| A bash puzzle, solved 02 Jul 2022 | |||
| A bash puzzle 25 Jun 2022 | |||
| Improve your troubleshooting by aggregating errors 11 Jun 2022 | |||
| Improve your troubleshooting by wrapping errors 28 May 2022 | |||
| Keep your promises 14 May 2022 | |||
| Archives | |||
August 2011
| 2011
| | ||
Comments
blog comments powered by Disqus