Rich visuals.
Editable content.

A tiny garden adventure One little seed. A little water. A little patience. What does a seed need? Water • Air • Warmth Once it sprouts, give it light. Small steps. Something grows. Try growing one seed this week.

Tile-size sweep Question Does more work per tile reduce transfer overhead? CONTROL Same shape and precision VARIABLE 64 / 128 / 256 elements CHECK Correctness before timing Latency by tile size Synthetic example · median latency in ms 33% lower than the 12 ms baseline Test more shapes before choosing a default. Illustrative values; no hardware benchmark was performed. What could reverse the result? Observation The largest tile is slower in the example. Hypothesis More local-memory pressure could offset fewer transfers. NEXT TEST Profile transfers and occupancy across uneven input sizes.

Meet the quiet core A concept for a calmer desktop Designed around airflow A clear path through the chassis Concept direction: accessible vents and a serviceable outer shell Small by design COMPACT Desk-friendly footprint SERVICEABLE Removable outer shell CONCEPT Not a shipping product

Reproducing a ranking rule METHOD Combine two ranked lists without comparing their raw score scales. RRF(d) = Σ 1 / (k + rᵢ(d)) rᵢ(d): rank in list i k: a positive smoothing constant Controlled example: k = 60, with two input lists. Method: Cormack, Clarke & Büttcher · SIGIR 2009 A controlled replication check Toy example · invented counts · 24 queries The fused ranking raises top-three coverage in this example. It does not establish general retrieval performance. What the example cannot establish 01 Generalization A tiny constructed corpus cannot represent production traffic. 02 Causal explanation Repeat with independent queries and ablations to isolate why the ranking changed.

I make complex work easier to use. Product designer / fictional candidate Research-led decisions. Clear interfaces. Careful delivery. Selected project PROBLEM Important tasks were lost in a long list. DECISION Separate today’s work from the backlog. EVIDENCE TO ADD Usability sessions and task completion. What I would bring Research Turn an unclear brief into testable questions. Design Make the next action clear and accessible. Delivery Explain trade-offs and follow the details through.

A club that is easier to join Candidate for student club coordinator Publish opportunities. Welcome first-time members. Make decisions visible. Three commitments for the term 01 Open calendar Publish events two weeks ahead. 02 A clear first step Give newcomers one named contact. 03 Visible follow-up Share decisions after each meeting. Judge the work, not the promise. A short public update every month What happened · What changed · What comes next

Year in review An illustrative operations scorecard 48 releases shipped 92% planned work completed 6 teams supported Synthetic example; not actual organizational results. This week / next week COMPLETED Published the onboarding guide Resolved the export regression NEXT Run five onboarding sessions Check export speed on large files BLOCKER Waiting for access to the shared test environment. Support backlog across four weeks Illustrative unresolved tickets at week end 18 fewer tickets from first week to last

A brighter everyday Citrus fragrance / concept campaign Citrus. Glass. Sunlight. A visual direction built around warmth and texture. Make room for a small ritual. A fictional product campaign Concept artwork, not a commercial offer.

POLICY BRIEF Shared lab booking A fictional internal policy Reserve only the time you need. Release unused slots early so other members can use the equipment. Example policy only; not an official notice. Who can book—and what is required Eligible members Members who have completed the relevant equipment induction. Before each session Confirm the slot and record the intended equipment use. After use: leave the workspace ready and report any fault. Implementation schedule WEEK 1 Publish the rules Collect questions from members. WEEK 2 Run the pilot Monitor slot use and cancellations. WEEK 4 Review the process Adjust the rules based on feedback.

BUILD WHAT PEOPLE USE. A fictional product team is meeting new talent. Product engineer THE WORK Build useful features. Test how they behave. Improve them with feedback. BRING AN EXAMPLE A small project you can explain: the decision, the trade-off and what you learned. Come with a question 10:00 Meet the team 11:00 Show one project 12:00 Discuss next steps Illustrative event schedule