285 reputation
19
bio website thepraxis.co.za
location South Africa
age 45
visits member for 4 years, 3 months
seen Nov 20 at 2:44

I am a software developer in Johannesburg, South Africa. I specialise in C# and ASP.NET, with SQL Server. I have, in some way or another, been involved in software development for about fourteen years, but always learning something new. At the moment that is WPF and MVVM. Follow me on Twitter at @bradykelly


Jan
26
comment Where does non-MVVM code belong in an MVVM app?
Yes, I have started that, but it proves one of the more challenging aspects of working in MVVM. I don't want a billion references to 'helper' libraries in each MVVM layer component. Sharing files through symlinks proved close to useless, but I think sharing projects like that might prove more fruitful.
Jan
25
comment Where does non-MVVM code belong in an MVVM app?
Thanks, you confirm the way I am currently doing things isn't batshit crazy. And oh so not proper MVVM.
Jan
25
asked Where does non-MVVM code belong in an MVVM app?
Jan
11
comment Are my novice user stories correctly composed?
As a plus, we teach our users what they want. I work for a large, international security company, and while we allow plenty of room for customisation plugins, we decide how secure the system must be and what it does.
Jan
9
comment Are my novice user stories correctly composed?
I prefer your second example, and the user needs their login account and to enter a password to ensure nobody fiddles with my data, so keep the password in the user story, but minimise its impact. Requirements for password format etc. belong in system owner stories.
Jan
9
asked Are my novice user stories correctly composed?
Nov
30
awarded  Critic
Mar
10
comment Is There a Real Advantage to Generic Repository?
So you're saying that for everyday MVC apps, IDbSet<T> should provide a good enough generic repository to forget about the repository pattern completely. Except for special situations e.g where you aren't allowed any DAL references in your MVC project.
Dec
15
comment Formalizing a requirements spec written in narrative English
Yes, I think I'll start with the UI requirements, as this is closest to what the user wants, then map those back into lower level data and logic requirements.
Dec
15
revised Formalizing a requirements spec written in narrative English
Simplified title to cater for all levels of readership.
Dec
15
comment Formalizing a requirements spec written in narrative English
@RobertHarvey, I am asking for guidance on formally codifying a spec written in natural language into some sort of more formal language suitable for communication in technical circles, and maybe implementation by a validation framework. Nowhere do I ask anything about NLP if you read my question properly.
Dec
14
asked Formalizing a requirements spec written in narrative English
Jul
17
comment How do I draft user stories as a developer?
@GlenH7 I understand this, but my problem is I don't know where to capture the technical stuff. If certain fields are required for a e.g. new employee, I don't want to use a story for each field, but rather "as a user I need to capture field x and y", and "may choose to capture field q and z" type thing. If my quick examples here are the right direction, I will try more exercise that way.
Jul
17
comment How do I draft user stories as a developer?
+1 for Excel spreadsheet is a terrible solution.
Jul
16
awarded  Yearling
Jul
16
asked How do I draft user stories as a developer?
Jul
13
awarded  Commentator
Jul
13
comment How do I treat application aspects with regard to features and user stories?
I like this, even if it doesn't resolve to only one, maybe I could use. "as a user, I would to see these errors like this", "like to be emailed on those errors" etc. But I'm using a tool that requires US's to be under a feature. I would then have one featire for the few error user stories?
Jul
13
comment How do I treat application aspects with regard to features and user stories?
@Euphoric They would apply to the great majority of stories; all stories that involve UI and data store e.g.
Jul
13
asked How do I treat application aspects with regard to features and user stories?