-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/04/13 13:42, Alem Biscan wrote: > For a job interview I am required among other things to create a phone > book application.
It would be easy to spend a year on that! You are probably better off showing something short, simple and understandable first. "Smart and gets things done" is what many look for. Then show how deep down the rabbit hole it could go depending on how comprehensive a solution is needed. Let's start with this amusing nonsense: > Name Surname You fail pretty much all 40 of the issues listed here: http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ I did a phone sync application a while back (BitPim) and here are some relevant issues: - - users have more than one computer/device/place they run the app - - they can't all talk to each other at the same time - - contradictory changes can be made - - phone numbers need labels (eg "home", "work", custom values) - - there can be more than one of each label - - numbers need to be prioritised (eg home1, then work1 for one user, cell1, home1 for another) - - numbers can have punctuation, spacing and other symbols and they matter - - normalizing numbers is hard and best done in the UI (eg converting 011 or 00 to +, 1 prefix in the US) - - the same principles apply to most other fields (eg addresses, names) - - you need to be able to recover any record and its values for any (reasonable) point in the past. This provides undo and removes the need for explicit load/save commands - - if you have to interoperate with anything else then they will have mangled the data in unbelievable ways - - if you have to interoperate with anything else then they will use different and inconsistent labels, tags, field names etc - - if you have to interoperate with anything else then you will need to use a probabilistic matcher to link records between your system and theirs - - if you have to interoperate with anything else then you'll want to store some of their mangled data and ids to make future matching easier - - almost every system like this ends up "intelligently" duplicating all the user records at some point. Think about prevention and how the user recovers (undo from earlier is a great help) Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlFl2XgACgkQmOOfHg372QRe1gCfaHfvyOp2o3mEZHZ1A+C26Eq6 K68AoJElmUjyyber54x4c0WNHsl/yFSm =AHms -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
