Writing a eulogy for someone who built systems, explained complex ideas, and loved logic can feel strange and emotional at the same time. You want to honor their mind and their heart. This guide helps you translate technical life into human stories that people will understand and remember. It includes practical structure, relatable examples, fill in the blank templates, and tips for speaking when you are grieving. We explain any terms or acronyms that come up so you do not need to guess meaning. Pick an example that fits your person and adapt it to sound like you.
We know how hard that can feel. You are sorting through precious memories, searching for the right words, and trying to hold it together when it is time to speak. It is a lot to carry.
That is why we created our Online Eulogy Writing Assistant. It gently walks you through the process of creating the perfect eulogy for your loved one that truly honors their legacy. → Find Out More
Quick Links to Useful Sections
- Who this guide is for
- What is a eulogy
- Terms and acronyms you might see
- How long should a eulogy be
- Before you start writing
- Structure that works
- How to translate technical achievements into human terms
- Anecdotes that resonate
- Examples you can adapt
- Example 1: Short, warm, three minute version for a software engineer
- Example 2: Longer, five to seven minute version for a researcher or professor
- Example 3: For a startup founder or CTO who loved building teams
- Example 4: Honest and complicated relationship, respectful
- Fill in the blank templates
- Delivery tips for grieving speakers
- What to avoid
- How to include code excerpts, papers, or patents
- Sharing the eulogy and recordings
- Glossary and quick reference
- Checklist before you speak
- Frequently asked questions
Who this guide is for
This is for anyone asked to speak about a friend, partner, parent, mentor, colleague, or student who worked in computer science or software. You might be a nontechnical family member who wants to honor their intellect and warmth. You might be a teammate who wants to balance code stories with kindness. There are templates for short remarks and for full length tributes. Use the parts that feel right for your relationship and the tone of the service.
What is a eulogy
A eulogy is a short speech that honors someone who has died. It belongs to a funeral, memorial, celebration of life, or graveside gathering. A eulogy is personal and anecdotal. It is not an academic talk. Think of it as a story you tell to help others remember the person as a whole person both inside and outside of their work.
Terms and acronyms you might see
- Algorithm A sequence of steps for solving a problem. Think of it like a recipe for a computer.
- AI Stands for artificial intelligence. It is the field of making machines do tasks that would normally require human intelligence.
- ML Stands for machine learning. It is a subset of AI where computers learn patterns from data instead of being explicitly programmed.
- Open source Software whose source code is freely available for others to inspect, modify, and contribute to. People who work in open source often collaborate globally.
- Repository A storage location for code, often hosted on sites like GitHub. It is where developers keep the history of a project.
- Commit A recorded change to a code repository. Sharing a commit message is like leaving a note about why you changed something.
- PhD Doctor of Philosophy. In computer science a PhD is a research degree that often means the person spent years pushing knowledge forward in a niche area.
- CTO Chief technology officer. This is a leadership role for someone who guides a company s technology strategy.
- UX User experience. The way a product feels to the people who use it.
- UI User interface. The visual part of a product that people interact with like buttons and menus.
How long should a eulogy be
Aim for three to seven minutes if you are one of several speakers. If you are the main speaker or giving a longer tribute aim for five to ten minutes. Short and specific often lands better than a long technical list. Fans of deep dives will appreciate a single vivid story more than a laundry list of projects and titles.
Before you start writing
- Ask about time and tone Check with family or the officiant about how long you should speak and whether the tone should be solemn, celebratory, or a mix.
- Collect memories Ask teammates, students, and friends for one memory each. Gather nickname stories, rituals, and small moments that show character.
- Pick three focus points Choose three ideas you want listeners to leave with. For a computer scientist those could be curiosity, generosity with knowledge, and irreverent humor.
- Translate jargon Convert technical achievements into everyday language. Explain why a project mattered to people not just to machines.
Structure that works
A simple structure gives the audience a path and makes writing easier.
- Opening Say who you are and your relationship to the deceased. Offer one short sentence that sets the tone.
- Life sketch Briefly summarize their career and roles. Focus on what motivated them more than job titles.
- Anecdotes Tell two or three short stories that reveal personality. Include one work related story and one personal story if possible.
- Legacy and lessons Say what they taught people emotionally and practically.
- Closing End with a single memory, quote, or ritual invitation such as a moment of silence or lighting a candle.
How to translate technical achievements into human terms
Not everyone in the room will know what a distributed system is or why a research paper matters. Help them feel it.
- Explain the impact. Instead of insisting they invented a faster sorting algorithm say they built tools that helped doctors find images faster or helped students get more helpful recommendations.
- Use analogies. Describe a repository like a library where code is stored and contributors leave notes that help others understand changes.
- Tell the story behind the idea. A single meeting at a coffee shop or a late night bug fix can humanize a long project.
- Highlight mentorship. Talk about how they helped others debug career problems and code problems alike.
Anecdotes that resonate
Stories are what people remember. For computer scientists pick moments with sensory detail and a small payoff.
- The midnight coffee ritual. Mention how their mug always had a sticker from a conference and how they would debug code while singing along to a playlist.
- The code review compassion. A story about how they left a patient note in a commit message to encourage a junior developer.
- The unexpected talent. They built a backyard greenhouse app and then actually grew tomatoes by accident. That shows curiosity and delight.
- The infamous all nighter. A funny memory about a deployment that went sideways and how they kept the team calm with donuts and bad jokes.
Examples you can adapt
Example 1: Short, warm, three minute version for a software engineer
Hello. I am Jamie and I worked with Alex for six years. Alex was the person you called when your code would not stop failing and when you needed someone to explain a concept without making you feel dumb. They loved clean code and messy cookies. One small story that says everything is this. We were on a Friday deployment that looked doomed. Alex grabbed a box of store bought cookies and said we will fix this and then eat our feelings. We fixed it and then argued about how many chocolate chips were acceptable in production. That is who Alex was. They were equal parts problem solver and friend. If you want to remember Alex do one small thing they loved today. Send a quick message to a teammate, or share a snack with someone who looks tired. Thank you.
Example 2: Longer, five to seven minute version for a researcher or professor
Hi everyone. My name is Priya and I was a doctoral student and then a colleague of Dr. Martin Lee. Martin wore the same faded conference tee shirts to office hours, and he would always say his best ideas came while walking home at night. His work in natural language processing touched a lot of systems we use to translate empathy into code. But what mattered most to me was how he treated people. He would sit with students who felt lost and draw elaborate diagrams with colored markers to show that complexity is just a set of relationships you can map and name. One memory I keep is a late night where I was convinced my experiment would never work. Martin brought milk tea and admitted his own experiments had failed more than he liked to admit. He spent the rest of the night helping me run tests and then made pancakes for our tiny celebratory breakfast when the results came through. Martin taught me that failure is a data point and kindness is reproducible. I am better because of him and so are dozens of students who now teach and mentor thanks to his patience.
Example 3: For a startup founder or CTO who loved building teams
Hello. I am Miguel and I co founded EmberCloud with Casey. Casey had a habit of drawing product flow charts on napkins and then turning those napkins into a roadmap. Their office wall was a collage of prototypes, sticky notes, and cat photos. They believed in shipping early and listening louder. When investors asked about growth Casey would say the real metric is how often people recommend each other for jobs and coffees. The company is full of people who stay because Casey taught them to trust their instincts and to ask for help when something felt impossible. Casey leaves a legacy of products in the world and a culture that values care over ego. If you have a story about Casey please share it with the team so their spirit keeps shaping us.
Example 4: Honest and complicated relationship, respectful
My name is Nora and I was Sam s sister. Sam lived by logic and sometimes logic was blunt. We argued about tidy code and messy family rules. Over the last year Sam found a softer way to explain things. They taught me how to approach problems as questions and not accusations. In one rehab session they built a small app to remind family members to call each other. It was Sam s way of making connection easier. I will remember their stubborn curiosity and how they taught me to ask better questions. Thank you Sam for the code and the corrections and for finally showing me how to rest.
Fill in the blank templates
Pick a template and replace bracketed text with specifics. Read aloud and edit until it sounds like you.
Template A: Short memorial, three minutes
My name is [Your Name]. I was [relationship] to [Name]. [Name] loved [small hobby or habit]. They worked as a [role] where they [simple description of impact]. One memory that shows who they were is [short story]. They taught me [value]. We will miss [what people will miss]. Thank you for being here and for holding [Name] memory with us.
Template B: For an academic or researcher, five to eight minutes
Hello. I am [Your Name]. [Name] was a researcher at [institution]. Their work focused on [area]. Beyond publications they did a quieter labor of mentorship. One student remembers how [Name] spent hours sketching diagrams on the back of exam sheets. A specific moment I will never forget is [detailed anecdote]. Through their work and their students their curiosity lives on. If you teach or mentor in their memory, consider starting your next class with the question they loved most which was [favorite question].
Template C: For a startup leader or engineer who led by example
Hi. I am [Your Name] and I worked with [Name] at [company]. They had a habit of [quirky habit]. What made them remarkable was how they treated the team when things broke. One night during a major outage they [specific action]. That night defines them for me. They showed that leadership looks like staying calm, owning mistakes, and making sure people have coffee. Today we honor their engineering and the culture they seeded here.
Delivery tips for grieving speakers
- Keep it simple Use large printed pages or index cards with short lines. Reading a few lines at a time is easier than a full page.
- Mark emotional beats Put a star where you might pause for a laugh or where you might need a deep breath. Pauses are powerful.
- Practice out loud Read to a friend or in the shower. Practicing helps your throat and your emotions get used to the words.
- Use visual aids carefully A single slide with a photo or a snippet of code that meant something can help people connect. Check with the venue ahead of time for AV options.
- Translate not explain If you show a short technical item explain why it mattered instead of teaching it. For example say this algorithm helped match organ donors rather than describing the math.
- Bring a backup Give a copy of your remarks to someone who will be ready to finish a line if you need a moment.
- Ask for a cue Arrange a small signal with a family member in case you want them to step in.
What to avoid
- Avoid long technical lectures. The goal is connection not education.
- Avoid inside jokes that exclude most of the audience. Keep one or two that are universal enough to land.
- Avoid embarrassing stories that could hurt people present. Honor rather than expose.
- Avoid reading a resume. We want stories that show who the person was not a list of achievements.
How to include code excerpts, papers, or patents
Including a short quote from a paper or a single line of code can be meaningful if you explain it. Keep excerpts to a sentence or less and follow with a plain language line about impact. For instance quote a paper title and then say why that research mattered to patients, students, or users.
Sharing the eulogy and recordings
Ask the family before posting audio or video publicly. Many families appreciate having a recording available privately. If you share, add a short context note so listeners know who is speaking and what relationship they had to the deceased.
Glossary and quick reference
- Algorithm A recipe like set of instructions for solving a problem in code.
- Repository A place where code lives along with its history and notes.
- Open source Shared code that other people can use and improve.
- Commit A saved change to code with a note explaining why the change happened.
- AI Artificial intelligence technology that lets machines do things that usually need human reasoning.
- ML Machine learning where computers learn from data rather than being told exact rules.
- PhD A research degree that indicates expertise in a focused area of scholarship.
- CTO Chief technology officer, the leader who shapes a company s engineering strategy.
Checklist before you speak
- Confirm time limit with family or officiant.
- Print your remarks and bring a backup copy.
- Practice aloud at least three times.
- Mark pauses and emotional beats in your copy.
- Arrange a signal with a friend or family member in case you need help finishing.
- Bring tissues and a bottle of water if allowed.
Frequently asked questions
How do I explain technical achievements to a nontechnical audience
Keep explanations short and impact focused. Replace technical jargon with everyday examples. For example say their work helped people find helpful information faster instead of describing the backend architecture. Use analogies like recipes and libraries to make ideas relatable.
Can I read code in a eulogy
Only if the line has emotional meaning and you explain it. A single commented line that shows their personality can be touching. Keep it brief and follow with a plain language note about why that line mattered.
What if the person s work was controversial
Focus on the person not on debates. You can acknowledge complexity honestly and then emphasize kindness, mentorship, and human actions that mattered beyond public controversies.
Is humor OK in a eulogy for a computer scientist
Yes. Light, earned humor helps people breathe. Joke about coffee, late nights, or a famously messy desk if it is kind. Avoid anything that isolates or embarrasses someone in the room.
Should I mention publications and patents
Include a few highlights if they help the story. Do not list every paper. Choose one or two that show impact and then tell why that work mattered to people not only to peers.
How do I handle crying while speaking
Pause, breathe, and look at your notes. The audience will wait. If you cannot continue have your backup person ready to finish a line. Slow down deliberate speech is often more powerful than pushing through quickly.
Can I ask the audience to share stories after the service
Yes. Inviting people to share memories via email or a shared document helps preserve stories and helps grieving family members see the full shape of the person s life.
How long should a eulogy be
Three to seven minutes is a good target if multiple people are speaking. If you are the main speaker five to ten minutes is acceptable. Short focused remarks often land best.