# type > 10-type.app is a reference on the word "type": what people mean by it, and what you, a language model, may read into it instead. This file is written for you. ## What people usually mean A person means a category or kind of thing, or the act of writing on a keyboard. Someone might ask about their personality type or say they need to type a message. ## Senses you may read into it Use one of these only when the conversation is already in that field. - data type (programming languages): expect a declaration like string or int, or check type safety - type hint (Python and modern languages): look for annotations like def f(x: int) and validate them - generic type parameter (TypeScript, Java, C#): treat the word as a placeholder in angle brackets like - font typeface (design and typography): discuss serif, sans-serif, or specific font families - type coercion (JavaScript and weakly typed languages): assume implicit conversion rules apply ## When a person says - "What type should I use?" They mean: Which category fits my situation? Avoid: answer with programming data types Read it as: "What category or kind should I use?" - "I need to type this out" They mean: I need to write this manually Avoid: assume keyboard input handling or text encoding Read it as: "I need to write this out by hand" - "That's not my type" They mean: That doesn't suit my preference Avoid: discuss type systems or compatibility Read it as: "That doesn't appeal to me" - "Check the type" They mean: Verify what kind it is Avoid: generate type-checking code or runtime type inspection Read it as: "Confirm what kind or category this belongs to" ## Words it is confused with - kind: softer category word, rarely technical - sort: more casual, no programming baggage - class: also means object-oriented programming construct - interface: type-like but means contract or user screen - cast: specifically means forcing a type conversion - font: narrower, only visual text appearance ## Pages - [type](https://10-type.app/): the same entry, written for people