To make a good first impression

n      smile and lean toward others as they talk

n      if standing, keep your body fully facing the people you’re speaking with

n      ask questions and follow up on people’s remarks; and in doing so, focus on opinions and feelings, not just facts

n      don’t interrupt

n      compliment others

n      try to find common experiences or interests

n      mention some vulnerabilities and laugh at yourself

n      draw others out and encourage people to join the conversation

n      put energy in your voice

n      at least at the start, focus on positive comments, not criticisms or complaints

n      offer a variety of topics

n      share observations about everyday life

n      share your passions and interests

n      don’t dwell on the minutiae of your life, especially annoyances

n      remember: people give more weight to their early information (were you engaged, warm, distracted, pompous?) than to later information, so be your most charming at the beginning of the conversation

n      remember: most people are more eager to be found interesting, funny, or insightful than to be interested, amused, or informed by you

Sql Server

What is normalization?
Database normalization is a data design and organization process applied to data structures based on rules that help build relational databases. In relational database design, the process of organizing data to minimize redundancy. Normalization usually involves dividing a database into two or more tables and defining relationships between the tables. The objective is to isolate data so that additions, deletions, and modifications of a field can be made in just one table and then propagated through the rest of the database via the defined relationships.

What are different normalization forms?

1NF: Eliminate Repeating Groups

Make a separate table for each set of related attributes, and give each table a primary key. Each field contains at most one value from its attribute domain.
2NF: Eliminate Redundant Data
If an attribute depends on only part of a multi-valued key, remove it to a separate table.

3NF: Eliminate Columns Not Dependent On Key
If attributes do not contribute to a description of the key, remove them to a separate table. All attributes must be directly dependent on the primary key
BCNF: Boyce-Codd Normal Form
If there are non-trivial dependencies between candidate key attributes, separate them out into distinct tables.

4NF: Isolate Independent Multiple Relationships
No table may contain two or more 1:n or n:m relationships that are not directly related.

5NF: Isolate Semantically Related Multiple Relationships
There may be practical constrains on information that justify separating logically related many-to-many relationships.

ONF: Optimal Normal Form
A model limited to only simple (elemental) facts, as expressed in Object Role Model notation.

DKNF: Domain-Key Normal Form
A model free from all modification anomalies.


Remember, these normalization guidelines are cumulative. For a database to be in 3NF, it must first fulfill all the criteria of a 2NF and 1NF database.