A brilliant coder would back up the data before they alter or delete it so they could restore it if, for example, they decided they needed names and contact info for people in the deleted section.
A brilliant coder would understand many databases are multi-relational...meaning the current set your looking at might describe someone as a probation al employee, but it may very well link to another database showing they had decades of employment with the agency.
1 of 4
A brilliant coder would understand they need to find user notes describing the intent and purpose of field content and that often times key words don't match a layman's definition. For example, diverse might describe collecting multiple samples from different geographic areas. Equity might describe ownership in a company. Inclusion might describe the data set can be accessed by everyone in a certain division.
2 of 4
A brilliant coder would understand the implications of data collected across time and that different coding and entry methods may have been as the database evolved.
A brilliant coder would know thousands of records created before computer-based data became the norm exist only on paper and were never transferred in their entirety to the computer-based system.
3 of 4
A brilliant coder would not, under any circumstances, mistakenly report the number $8,000,000,000 when the actual number was $8,000,000. In coding, those commas and zeros are the difference between code that runs and code that crashes.
A brilliant financial advisor would understand the difference between an audit and a compilation.
4 of 4
Tammy Gentzel
Daedalean