Status
SteamPeaks
ChartsSalesUpcomingPatchesNewsCalculator
New on SteamEvery app, DLC and depot the minute Steam creates itAppsEvery app on Steam, newest change firstPackagesSubs and bundles, and what each containsDepotsDepots, manifests and install sizesTagsSteam's user tags and the games under themDevelopers & publishersCompanies and their cataloguesTechnologiesEngines, SDKs and anti-cheat found in the filesChange historyEvery PICS changelist as it lands
SignalsNineteen readings of the whole catalogueCompareAny games side by sideRecordsAll-time peaks and the days they were setReportsWeekly and monthly write-upsAlerts & newsroomWatch a game, get told when it movesSteam statusIs Steam up, right nowWeb API explorerTry the endpoints in the browser
NewsSteam's own announcements and the sales calendarCalculatorWhat a Steam account is worth, and its pile of shame
/
Sign in
/
SteamPeaks
The ultimate resource for Steam data.
ExploreChartsSalesSales and festsUpcomingPatchesNewsRecordsTrendingSignals
DatabaseAppsPackagesDepotsTagsDevelopersTechnologiesChange history
ToolsCalculatorCompareSearchAlertsSteam statusAPI
SiteMethodologyFAQDiscordSupportSign in via Steam
Not affiliated with Valve or Steam. Game names and artwork belong to their owners. All times UTC.
PrivacyCookiesFair useStatus
The Things Left BehindNewsDeveloper Diary #5 — Building It From Scratch
Community

Developer Diary #5 — Building It From Scratch

The Things Left Behind · published 1 Oct 2026, 16:55 UTC

All newsPlayers around this dateRead on Steam

Starting a project from scratch is kind of terrifying.

Between You, Me, & the Trees was the first project I worked on as a project leader, so I got to see the whole thing happen from basically nothing. I learned a lot from leading the team, but honestly, I learned just as much from my teammates and from all the weird little problems we had to solve together.

A lot of my time was spent trying to balance two things at once: doing my own development work and making sure everyone else had what they needed to keep going. Sometimes that meant planning, sometimes it meant troubleshooting, and sometimes it meant staring at code and wondering why something that worked yesterday had suddenly decided not to work today.

One of the things I’m most proud of is the inventory system.

Originally, we thought we would just buy or import an existing one. Easy, right? Except the options we found were either too expensive or way more annoying to integrate than expected. So eventually it became: okay, I guess we’re building an inventory system now.

And we did.

There was definitely a learning curve. I had to figure out the toggle functionality, test it with different trinkets, break it, fix it, test it again, and then realize there were three more situations I had not thought about yet. It taught me a lot about building systems that can actually grow with the game instead of only working for the exact thing you need in that moment.

I also became extremely familiar with Git merge conflicts.

Like. Extremely familiar.

When multiple people are working on different parts of the same game, eventually Git decides it is time for everyone to suffer a little. I spent a lot of time merging branches, resolving conflicts, and trying to understand how different pieces of the project connected to each other.

Sometimes things got lost. Sometimes someone had to redo work. Sometimes that someone was me. Sorry again to everyone who had to deal with that 🫶

But weirdly, dealing with all of those conflicts helped me understand the project better. Every time something broke, I had to trace where it came from, who was working on what, and how all the systems fit together. It forced me to stop thinking only about my own code and start seeing the game as one big connected thing.

And I think that was probably one of the biggest lessons for me.

Looking back, Between You, Me, & the Trees was not really one giant breakthrough moment. It was a lot of tiny ones. Fixing something that had been broken for hours. Watching a feature finally work. Seeing someone add a piece of art or writing and suddenly the game felt a little more real. Celebrating small wins with the team and slowly realizing that all these separate pieces were becoming an actual game.

Being a team leader taught me that leadership is not really about standing above the project and telling everyone what to do.

Sometimes it is just being in the mess with everyone else.

Writing code. Fixing problems. Breaking things. Fixing them again. And somehow keeping the team moving toward something you are all excited to make.

More from The Things Left Behind

Other announcements

All news
Community17 Sep 2026Developer Diary #3 — Meetings, but Make Them GayMeetings are not fun. Or at least, they’re not supposed to be. Somehow, team meetings for Between You, Me, & the Trees were a blast. Every meeting felt a little like a holiday. We got new art asset presents, celebrated what we had accomplished that week, and watched the game gradually become something more real. One of my favorite parts of the process was how collaborative it felt. Everyone had…Community3 Sep 2026Developer Diary #2 — When Story and Gameplay ClickI think the biggest breakthrough for me was when the narrative, art, and gameplay finally started to click together. Early on, it felt like I was juggling a bunch of separate pieces. I had a story I cared about and gameplay that worked, but they didn’t quite feel like they belonged to the same game. There were a lot of moments where something technically worked, but just felt… off. Instead of p…Community22 May 2026Developer Diary #1 — Making Queer Chaos Feel PlayableThis is the first in a series of developer and creator diaries for The Things Left Behind . Through these posts, we want to share honest insight into the creative process behind the game, the struggles, breakthroughs, frustrations, and moments of pride that shaped development along the way. Our goal is here is not only to document the journey, but also to give back to the community by sharing w…