Hot answers tagged

2

Be careful of using methods that would prevent some of your users from entering their actual names. Names are extremely personal and being told 'you can't use your real name' isn't going to sit well with everyone. I remember dealing with a customer at least once a month who was upset that she couldn't use her hyphenated name (this was a rarely-accessed ...


1

First, I would make a collaborative glossary with the client to make sure there is no ambiguity about the industrial jargon. Then, I would identify high level entities, and list every attributes belonging to them. Each attribute should have a name, a business description and a data type. For the how-to, I suggest a simple XLS or Google Drive Spreadsheet. ...


1

You could use keywords and delimiters to have the code automatically parse the text and format it in a small preview window. For your example: John Doe // First line is always the name @ Company Best Inc. // use @ symbol to denote company name line disc this, this and that. // the line starting with the disc keyword is the discussion info appt ...


1

Sanitizing user input doesn't imply you change or restrict input, it simply means you handle it safely and escape it when necessary to prevent exploits like XSS attacks. If you're saving the data to a database, use parameterized queries. Even if your specific database doesn't support them directly, often times many libraries can add a simple wrapper over ...



Only top voted, non community-wiki answers of a minimum length are eligible