201 reputation
19
bio website linkedin.com/in/corylarsoncts
location Milwaukee, WI
age 28
visits member for 3 years, 8 months
seen 2 days ago

I'm a consultant for Corporate Technology Solutions, Inc. I work with clients in the financial services industry of southeast Wisconsin. I have a BS in Software Engineering from Milwaukee School of Engineering, where I graduated in 2008 with Honors.

I enjoy web application development, database design, functional and technical design, professionalism, and multi-tasking. I am fluent in C#, VB.NET, Java, JavaScript, SQL, and a myriad of markup languages. In my free time I like to read, work on cars, and contribute on StackOverflow :)

profile for Cory on Stack Exchange, a network of free, community-driven Q&A sites

Some notable achievements on [so]:


Feb
27
comment If you need more than 3 levels of indentation, you're screwed?
@erisco: I was definitely thinking math and AI algorithms when I said "unavoidable," though my AI book is at the office otherwise I would have given an example.
Jan
4
comment Data validation best practices: how can I better construct user feedback?
Robert, thanks for the suggestions. The books "Don't Make Me Think" and "Elements of Style" have both come up in this thread; I hope to check them out. On the "Undo" feature: are there any techniques related to the Command pattern for web applications? I like the idea, I'm just not sure what kind of complexity it would add to an MVC/MVP/MVVM patterned website (disregarding changes to your DAL).
Jan
4
comment Data validation best practices: how can I better construct user feedback?
@Guarav: Thanks for the update. I've never experienced a site with audio-enhanced validation. I think it would annoy those who don't need it. It would probably make more sense to have that as a configurable option. I'm curious for some more feedback on the topic of audio feedback.
Jan
4
comment Data validation best practices: how can I better construct user feedback?
Thanks 5, I appreciate the feedback. So far most posters' suggestions coincide with my practices, so I must be on the right track. I stick to red text like you mentioned (near the field), and only use alerts as a last resort for unhandled or unexpected errors (AJAX callbacks from a WCF service, for example). On the "please" issue, what do you think about using it outside of the error context, such as "Login failed. Please try again."? To me, that is more pleasant than "Login failed, try again," but maybe that's just what I'm used to.
Jan
4
comment Data validation best practices: how can I better construct user feedback?
"Do you really want to read the selected material?" -- Well, I think so...yes, thanks!
Jan
4
comment Data validation best practices: how can I better construct user feedback?
The book you linked to comes up in several posts, perhaps I'll pursue it. I agree with your first point on Delivery, though I don't implement the other two points on every field. I show restrictions usually only for fields that "Must be unique" or "Must be a valid <blank>" so I can keep the UI clean. Validating on blur is sometimes more work than its worth if you need to repeat the validation server side, but I don't disagree.
Jan
4
comment Data validation best practices: how can I better construct user feedback?
I'm in the middle of exactly what you described for the i18n, with the error strings automatically fed back to me from my domain object validators. I agree with your description for delivery (it's exactly what I'm doing), though the whole first-person entity thing is a bit strange for me. Thanks for your feedback!
Jan
2
comment Data validation best practices: how can I better construct user feedback?
Thanks Guarav. Your answer agrees with most of my own current practices. One thing I'm attempting to refine is how to do the delivery in AJAX powered forms where validation & verification are split or duplicated between the client side and server side. Any thoughts on that?
Jan
2
comment Data validation best practices: how can I better construct user feedback?
I'm all for visual feedback, even eye candy if appropriate. It gets complex when you need to build a system that has to cater to the visually impaired (color blindness or full blindness), so that's why I put emphasis on content over look and feel in my OP.
Jan
2
comment Data validation best practices: how can I better construct user feedback?
I appreciate the feedback, however, let me extend my post by saying that most of the answers to the questions I asked are very obvious, as you decided to point out. I'm less interested in the how and more interested in the why.
Dec
31
comment Data validation best practices: how can I better construct user feedback?
@DVK: Thanks for the tip. I'll check it out.