thoughts.

Moved to NY with JH on April 11, 2026. I want to keep my thoughts vague in a way where it's applicable and possibly helpful to everyone.

vague thoughts.

• have an emergency fund.

You don't know what's going to happen in life. You don't know who will be there to support you. My fear of being dependent prevented me from relying on others. Sometimes you're your own limiting factor. This time I was lucky, but I like to think I built toward my luck by making sure to have a cushion.

• be friendly and kind.

I have had the fortune of meeting really amazing people. Being an introvert, none of these new relationships would have formed if I decided to stay nonchalant. I'm most grateful for my own luck of creating relationships where the counterparts are so very loving and caring. Meet new people, build relationships, it will lead to many journeys that bring you closer to some of your goals.

• read and exercise and do fun things.

"Work hard, play hard." Give yourself the flexibility to do fun things by working hard when you should be working hard. Don't let laziness cause time to slip away. Learn things, grow and get better. Keep up your health. Laugh.

Do I think that the ideas and concepts in this book are important? Yes. Do I think that I needed to read this book to know it? No.

The most important reminder in this book, for me, was to embrace boredom. Only when people overcome the minute distractions and desire for quick gratifications, and truly allow ourselves to be bored, can we achieve deep work. For software engineers, This is so true. From pursuing a career with a clear skill-gap to now relying so heavily on AI such that we know what we made moreso than how we made it, we are susceptible to becoming obsolete if we allow ourselves to fall in love with instant gratification of getting something over the finish line without understanding the system we built.

I like to create project guidelines using AI. This way I can build for myself and learn how to build things and even more importantly, learn from mistakes. For example, I let AI write a repository with broken-down PRDs of implementing an image processing pipeline. I will use this repository to learn Golang. I will go back to 2022 and write the code myself because I need to understand the "why not" just as much as the "why".

This learning will only be achievable if I prevent myself from seeking the unuseful joy of quick-turned-long scroll sessions. I take from this book the idea that to fall into deep work, you need to fall in love with yourself and your time and how you use it. Only by doing so can you take the steps necessary to remove distractions, be okay with the quiet, and push yourself to be better.

My time at Valinor Streamline was quick. I learned more about what kind of engineer I want to be.

Pulling weeks of 14 hour days and having many days where it felt like if I didn't work during all parts of the day, I wasn't doing enough, is brutal. Some people are cut out for it. I think I value my relationship with the important people around me, and this was reaffirming experience.

Life shouldn't be taken for granted; happiness comes first, whatever that may be. I've come to understand what my happiness is not.

Onto the next part of my life, never forgetting to put a smile on my face because it reminds me to be grateful for who and what I have in my life.

Cheers, CD!

To a friendship that probably wouldn't have happened but did.

To someone who I feel more connected to, and am grateful for, than they probably realize.

To leaving me with lots of memories that I can reminisce on with a smile.

To a person that deserves a lot and then some.

See you soon :) Until then, stay safe and live life to the fullest!

During my time here, I've been able to grow as a software engineer in ways I couldn't have imagined.

MV, CG, and DM, thanks for driving me to be my absolute best. All the lessons I learned are engraved into my mindset on how to be a member of a team, a mentor of the team, and overall how to be a person.

There are many others that I should mention.

Thanks to everyone for making me feel welcome!

I think one skill that I critically lack as a software engineer (at least from being the kind of engineer I'd like to be) is having a systems-level language that I feel comfortable writing and thinking in. I began studying Rust over the past week, and it will be one of my main learning priorities for the time being. The plan is to learn the basics over the next couple of weeks, and then move on to a small-scale project without AI assistance so that I feel the pain. Then, I will tackle on trying to implement an existing project or research paper in Rust to really feel the pain, but I will use AI assistance here.

Resources

• The Rust Programming Language
• Rust Design Patterns

I rewatched Good Will Hunting and previously had thought that it was about the character developments of two lonely individuals, one who continues to push others away and another who has known what it's like to be alone for a long time. After this watch, I can't help but think it was the most likely friendship that could have possibly developed.

Will is a genius but has an ego like no other - a defense mechanism, requiring him to be tough to endure the pains of his childhood. When his ego is hurt, he can't submit nor can he admit that he is lesser. And this is why this relationship works. In the context of the movie, Sean is the first to have an explicitly stated strength that is greater than that of Will's. It was the first moment to crack into Will's ego and begin allowing himself to maybe, just maybe, bring him back down to earth.

As an incoming computer science grad student at the University of Illinois - Urbana Champaign, I'm brushing up on my math knowledge as my core focus will be in machine learning and artificial intelligence. Trying to freshen up on linear algebra, calculus, and probability has brought me back to the nights at Olssen Hall loaded up on Red Bulls.

Resources

• Linear Algebra Overview
• Math Topics Cheatsheets
• AI/ML/Math Quick Reviews

Now that I'm adding a tab for this on my website, I hope that I remember it exists and continue to write my thoughts here about pieces outside of technical learning.

Context

I'm building an AI application and taking on context engineering challenges. There's a lot of domain specific knowledge that an LLM could not possibly know unless the AI has worked for the company for a long time. The LLM is like a new intern that can learn and do everything quicker than a person can but just needs to know how.

Overview

I created a project where we generate embeddings for common questions and definitions along with the context associated to them (which will be provided to the LLM), and we added that to our vector store. When our application is presented with a user query, we create embeddings from it, reach out to the vector store, retrieve n documents, run a reranker, and use topm documents as context for the LLM.

Learnings

• More dimensions do not mean that the retrieval is better. In fact, because the data we were embedding was short and from a next-token-prediction perspective, very similar, the retrieval was poor. Once we used an embedding model with fewer dimensions, the recall was much higher and consistent.
• Reranker saves the day. Even if recall is good, it may not be the top choice from our retrieval. Writing an LLM-based reranker made the passed-in context much more relevant for the user's ask.
• Evaluation frameworks are crucial. We would not have known the previous two if it had not been for the evaluation metrics I wrote to measure recall, precision, and MRR. With a non-deterministic system like an AI application, evaluations for both pre- and post-deployment are critical and should not be ignored for the sake of getting the feature out quicker.

It puts my heart at peace that you are in a better place.

The sacrifices you've had to make to give your grandchildren the best life possible will never be forgotten or unappreciated.

Please watch over me from above.

I think about the 주먹밥 you made me every morning before school.

I wanted to build an MCP server of a platform that I use quite often. I noticed that SeatGeek had a developer API but I didn't see an MCP server that could allow me to use it from an MCP client. So I thought, "why not build one myself?" It gave me the opportunity to learn more about how to build an MCP server from scratch. I used Typescript to implement this project, and I was able to run it in both Claude Desktop and OpenWebUI/Ollama.

Biggest Takeaway

Building tools is not so easy. I used to think that a tool was just a simple interface to call an API, but when an endpoint has many flexible parameters, the LLM opts to use them as much as possible. For example, many public/developer APIs offer a free-search parameter. In the SeatGeek API, it was the "q" parameter. Every search ended up using the "q" parameter, which often brought back poor results. It was even worse for some APIs where "q" could search both performers and events together. So my solution was to expose more structured, yet flexible parameters. I separately evaluated the user's query to determine possible "event_q" and "performers_q" parameters and individually ran them on an event search query and a performer search query, then aggregated the results. Tool calls have to be designed carefully to avoid ambiguity and poor results.

Interesting Fact

Because no one has built an MCP server for SeatGeek, I am the top Google Search result and am even included by responses from ChatGPT, Gemini, and Claude when asked about the SeatGeek MCP server. It's funny, and it's like a UFC belt. Just waiting for someone to take it away from me.

For the first time in my career, I experienced a team shake-up where the most experienced engineers and manager on the team have moved to a new one. Perhaps the first of many.

Gratitude

Giving thanks to my manager for teaching me how to grow as a software engineer as quickly as possible. He taught me how to push hard to achieve my own goals that benefit both me and the team. Always gave me the opportunity to work on the most challenging problems that helped me grow in as many as aspects as possible.

Giving thanks to my mentor for teaching me what it means to be a mentor. Truly the best mentor I could have possibly asked for. I remember him helping me once at midnight because he saw that I was online. Investing time in new team members' growth truly accelerates the team's overall capabilities. I will pay it forward as you did.

This is something that every software engineer should make for the sake of practice and self-expression, and I finally got around to making one. Nothing fancy, but I had a lot of fun developing my technical skills and also found the designing process compelling. I'm more of a coffee-and-a-book-looking-out-into-a-flat-meadow kind of guy, so designing a website where it feels calm and soothing was the goal, and I think I achieved that for the most part.

I hope to add new skills, projects, and career developments to this site as I continue to grow in my search for challenge, peace, and adventure. Basically just saying let's not forget (Peter) that this site you built actually exists.

This was built using Next.js and Typescript.