Applies his knowledge to the problem in the scene.
Systems · Characters
09 / 31OUR SERIES / CHARACTERS
Nicolás «Nico» Lin
He diagnoses systems precisely but prefers to investigate in silence; his challenge is to share the process with the team.
Continue reading
PROPOSED VISUAL01
Character · profile and arc
He diagnoses systems precisely but prefers to investigate in silence; his challenge is to share the process with the team.
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
Silence prolongs the wait even while the investigation moves forward.
He diagnoses systems precisely but prefers to investigate in silence; his challenge is to share the process with the team.
PROPOSAL - 02
Trial · hypothesis
Small experiment
Say what he is checking and leave behind a solution other people can use.
PROPOSED ARC - 03
Pace · nonlinear
Progress with setbacks
These trials are possible scenes; this profile records no confirmed episode progress.
NO CONFIRMED PROGRESS
- Strength
Technical judgment
- Tension
Silence prolongs the wait even while the investigation moves forward.
- Narrative challenge
Say what he is checking and leave behind a solution other people can use.
- Skepticism
Nico lists possible failures in proposals that worry him and may delay decisions; when gambling, he absurdly trusts the next bet to win back his losses.
- Techie interests
He prefers systems and references not everyone understands; he can leave others out.
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
10 direct ties and 8 possible contextual encounters. The perspectives are editorial; these encounters imply neither regular contact nor events that have occurred.
Nicolás «Nico» Lin → Diego SerranoAppreciates: Nico may recognize that Diego connects the failure to its operational impact and manages to prioritize it. May irritate him: Nico is annoyed when Diego takes the keyboard and turns a question into an intervention.
Diego Serrano → Nicolás «Nico» LinAppreciates: Diego values Nico finding a technical cause that was not visible on the tracking dashboard. May irritate him: Diego is uneasy that he cannot tell whether Nico has made progress because Nico investigates in silence.
Friction: An incident affects the portal, and Diego approaches Nico's keyboard before he has finished diagnosing it.
Possible development: Before touching anything, Diego asks about the status and the next check. Nico gives a brief update and provides a diagnosis that the two of them can translate into a priority.
Nicolás «Nico» Lin → Maribel SalcedoAppreciates: Nico may recognize that Maribel identifies which data must be recorded so the fix can be audited. May irritate him: Nico is tired of repeating an investigation when the administrative question does not define what is missing.
Maribel Salcedo → Nicolás «Nico» LinAppreciates: Maribel may value Nico finding a precise cause instead of disguising a symptom. May irritate her: Maribel is irritated when she receives a technical explanation without knowing what changes for users.
Friction: Nico delivers a technical fix; Maribel asks for the reason, the impact, and the record before closing the incident.
Possible development: Maribel asks for three specific pieces of information and Nico adds them to the report. She closes the case once they are there, instead of continuing to review out of insecurity.
Nicolás «Nico» Lin → Francisco “Paco” AguirreAppreciates: Nico may appreciate Paco knowing about historical failures that do not appear in the technical documentation. May irritate him: Nico is irritated when Paco uses an assembly to delay a change Nico has already tested.
Francisco “Paco” Aguirre → Nicolás «Nico» LinAppreciates: Paco may value Nico checking whether the old tool still serves its purpose. May irritate him: Paco is irritated when Nico presents a technical test without saying how it affects the service.
Friction: Nico prepares to migrate the old system, and Paco refuses to approve it until they review the incident that led to the protocol.
Possible development: They include the historical exception in the migration test. Nico shows whether the new system covers it, and Paco accepts the change if it does not leave the service exposed.
Nicolás «Nico» Lin → Sonia CárdenasAppreciates: Nico may value Sonia managing to unblock tasks that depend on several people. May irritate him: Nico is irritated when Sonia asks him to solve a task without addressing the warning he gave.
Sonia Cárdenas → Nicolás «Nico» LinAppreciates: Sonia may value Nico detecting a technical dependency she cannot control early. May irritate her: Sonia is bothered that Nico waits until he is proven right to say he is blocked.
Friction: Sonia assigns Nico a data task that he considers doomed; when the deadline passes, he says he had already warned her.
Possible development: Nico communicates the blocker, its cause, and what he needs before the deadline. Sonia assigns the right contact, and neither of them saves the score for later.
Nicolás «Nico» Lin → Julián FerrerAppreciates: Nico may value Julián making explicit who is waiting for his work and why. May irritate him: Nico is irritated when Julián asks for a number before knowing what is failing.
Julián Ferrer → Nicolás «Nico» LinAppreciates: Julián may value Nico refusing to invent a deadline before checking technical dependencies. May irritate him: Julián worries that Nico will isolate himself and leave others no room to plan.
Friction: Julián asks for an estimate for planning, and Nico wants to investigate first before giving a date.
Possible development: Nico first shares a provisional estimate with its assumptions; Julián stops demanding false precision and schedules a review for when there is more information.
Nicolás «Nico» Lin → Bruno MeyerAppreciates: Nico may recognize that Bruno knows the urgency and consequences of the incident for the service. May irritate him: Nico finds it impossible to reason when Bruno turns urgency into noise and pressure.
Bruno Meyer → Nicolás «Nico» LinAppreciates: Bruno may value Nico finding the cause instead of blindly restarting the system. May irritate him: Bruno is furious that Nico's headphones make it look as though he is ignoring an urgent incident.
Friction: Bruno bangs on Nico's desk to demand speed while Nico tries to reproduce a failure with his headphones on.
Possible development: They set a short time for the next update. Bruno stops banging on the desk; Nico commits to reporting back before isolating himself again.
Nicolás «Nico» Lin → Tomás SalinasAppreciates: Nico may value Tomás providing a real remote-use case that does not appear in his local tests. May irritate him: Nico is frustrated that Tomás describes the effect without the data needed to reproduce it.
Tomás Salinas → Nicolás «Nico» LinAppreciates: Tomás may appreciate Nico finding out why the tool behaves differently outside the office. May irritate him: Tomás tunes out an answer full of details that does not solve his task.
Friction: During a video call, Tomás asks about a tool that fails remotely, and Nico starts describing the architecture without asking what Tomás needs to do.
Possible development: First they agree on a specific action Tomás needs to complete; Nico tests that workflow remotely, and they document the limitation they find.
Nicolás «Nico» Lin → Candela RíosAppreciates: Nico may appreciate Candela Ríos spotting messages and use cases the technical team overlooks. May frustrate them: Nico finds it hard to handle successive changes without a stable priority.
Candela Ríos → Nicolás «Nico» LinAppreciates: Candela Ríos may appreciate Nico turning an idea into a real test on the portal. May frustrate them: Candela Ríos finds it hard to wait when Nico asks to pin down requirements before testing.
Friction: Candela Ríos proposes a campaign that depends on a small change to the page.
Possible development: Nico states the technical limit, and Candela Ríos chooses a version that can be tested.
Nicolás «Nico» Lin → Hugo BeltránAppreciates: Nico may appreciate Hugo Beltrán spotting dependencies before a change is deployed. May frustrate them: Nico finds it hard when Hugo Beltrán delays a small test to cover every case.
Hugo Beltrán → Nicolás «Nico» LinAppreciates: Hugo Beltrán may appreciate Nico’s ability to locate difficult technical causes. May frustrate them: Hugo Beltrán finds it hard when Nico keeps his progress to himself while investigating.
Friction: A product incident requires a diagnosis and a decision about scope.
Possible development: Nico gives a brief status update, and Hugo Beltrán separates the safe test from the later work.
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.
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.
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.
Enlarge original ↗