He understands feed integration and quickly spots mapping errors.
Catalog and professional feed integrations · Characters
22 / 31OUR SERIES / CHARACTERS
Damián Vela
A two-meter-tall techie with a gym obsession: Damián calculates macros more precisely than task hours and turns any break into a discussion about protein.
Continue reading
PROPOSED VISUAL01
Character · profile and arc
A two-meter-tall techie with a gym obsession: Damián calculates macros more precisely than task hours and turns any break into a discussion about protein.
An ordinal editorial scale for fiction writing; it is not an assessment or measurement. Values and future states are proposals; no confirmed progress is recorded.
- 01
Starting point · proposal
He insists his routine is flexible until a meeting coincides with his meal.
A two-meter-tall techie with a gym obsession: Damián calculates macros more precisely than task hours and turns any break into a discussion about protein.
PROPOSAL - 02
Trial · hypothesis
Small experiment
Document one small, reversible change before the end of the day.
PROPOSED ARC - 03
Pace · nonlinear
Progress with setbacks
These trials are possible scenes; this profile records no confirmed episode progress.
NO CONFIRMED PROGRESS
- Strength
Data mapping and integrations
- Tension
He insists his routine is flexible until a meeting coincides with his meal.
- Narrative challenge
Document one small, reversible change before the end of the day.
- Gym obsession
Damián tracks workouts and macros; he gets irritated if a meeting disrupts his plan and may put off documentation.
- Giant · 2 meters
Damián is two meters tall, but dislikes being called on only to move things: he wants people to value his technical judgment.
Enlarge original ↗02
Visual guide · proposal
The visual identity remains a proposal; the sheets serve as documentation and do not approve the animation.
Enlarge original ↗03
Recorded relationships
6 direct ties and 12 possible contextual encounters. The perspectives are editorial; these encounters imply neither regular contact nor events that have occurred.
Damián Vela → Diego SerranoAppreciates: Damián may value Diego spotting the business priority behind an integration failure. May frustrate him: he is irritated when Diego takes over the keyboard while he is still explaining the mapping, then asks for documentation he left no time to write.
Diego Serrano → Damián VelaAppreciates: Diego may value Damián reconstructing a mapping between sources that no one had documented properly. May frustrate him: he is irritated when Damián leaves the ticket half-done to go to the gym.
Friction: The issue is urgent and Damián’s record is incomplete; Diego’s immediate intervention may fix it while reinforcing the dependency he later criticizes.
Possible development: Diego asks before taking over the keyboard, and Damián leaves a brief note before leaving, with setbacks when time is tight.
Damián Vela → Nicolás «Nico» LinAppreciates: Damián may value Nico anticipating which field in the old system still consumes the same data. May frustrate him: he is irritated when Nico lists possible failures without pointing out which one is blocking today’s fix.
Nicolás «Nico» Lin → Damián VelaAppreciates: Nico may value Damián finding where a new feed breaks an old automation. May frustrate him: he is irritated when Damián times every explanation against his gym schedule.
Friction: The new option seems to work, but some records still use the old format and the change remains poorly documented. Nico’s pessimism catches real risks, but can also prolong the decision.
Possible development: Nico chooses a test that addresses his main objection, and Damián leaves a brief record before heading out; they may go back to arguing over every case or just the schedule.
Damián Vela → Bruno MeyerAppreciates: Damián may value Bruno knowing which issues recur and why they affect the next shift. May frustrate him: he is irritated when Bruno treats availability as proof of commitment and uses a dressing-down to get it.
Bruno Meyer → Damián VelaAppreciates: Bruno may value Damián finding specific feed errors and explaining which ticket is blocking support. May frustrate him: he is irritated when Damián leaves to train while a task remains unexplained for the next shift.
Friction: An issue needs coverage, but a schedule does not make personal time automatically available. Damián needs to own his ticket, and Bruno needs to ask for help without intimidation.
Possible development: They agree on who covers the case and when the time will be made up, though Bruno may start ordering people around again and Damián may hide a ticket behind his gym schedule.
Damián Vela → Hugo BeltránAppreciates: Damián may value Hugo calmly reproducing an edge case in the feed before deployment. May frustrate him: he is irritated when Hugo opens seven new tests after Damián has already identified the failing mapping.
Hugo Beltrán → Damián VelaAppreciates: Hugo may value Damián quickly finding the column whose meaning changed. May frustrate him: he is irritated when Damián leaves without recording how he verified the import.
Friction: The fix seems clear, but a record and a minimal test are still pending. Hugo may overcomplicate the cases, while Damián may leave with his explanation unfinished.
Possible development: They define a minimal test, record the result, and leave the other cases as separate tasks, with setbacks for both when time or risk presses them.
Damián Vela → Carmen OrtegaAppreciates: Damián may value Carmen spotting gym or supplement subscriptions that renew while unused. May frustrate him: he is irritated when she counts his private expenses in the same tone she uses to haggle over cents on the portal.
Carmen Ortega → Damián VelaAppreciates: Carmen may value Damián finding why the feed duplicates a charge or confuses two services. May frustrate her: she is irritated when he leaves a change undocumented, then asks her to respect a routine he himself disrupted.
Friction: Both readily track other people’s figures and get defensive when one of their own numbers does not add up. The technical conversation veers into personal spending and habits.
Possible development: They resolve the charge and agree to leave each other’s private accounts alone, though either may bring up a receipt or a metric as a weapon again.
Damián Vela → Celia MartínAppreciates: Damián may value Celia identifying which wording creates a false expectation instead of asking for a general review. May frustrate him: he is irritated when she turns a technical issue into a conversation about his values.
Celia Martín → Damián VelaAppreciates: Celia may value Damián finding why a data point changed category before the error recurs. May frustrate her: she is irritated when he reduces to a field-mapping issue a listing that is communicating something wrong to real people.
Friction: The listing needs to be corrected and its source identified. Celia may moralize about intent, while Damián may stay focused on the technical field without explaining the impact.
Possible development: Celia states the risk, and Damián gives a verifiable cause and solution, though either may revert to their favorite explanation.
Enlarge original ↗