I missed DevFest last year because I didn't realize it was happening until I saw everyone's recap posts on Monday morning. I missed a YC-adjacent AI demo day because someone mentioned it in a Slack message I skimmed. I missed a local security conference because I assumed it would be announced more broadly.

After the third miss in a month, I decided to actually think about the problem instead of just being annoyed by it.

The issue wasn't that the events weren't announced. They were — just not in places I was looking, or not with enough lead time for me to plan around them. The fix turned out to be pretty simple.

The three-layer system

Layer 1: One aggregator, checked weekly.

I use Droppa for this. Every Sunday, I spend about five minutes looking at what's coming up in my city and in the categories I care about (AI, security, developer tooling). I'm not trying to fill my calendar — I'm just trying to know what's happening so I can decide whether to go.

The key insight here is that you need to check this with enough lead time to actually act. If you're checking on Friday for the same week, you've already lost most of your options. Sunday-for-the-following-two-weeks is the right window.

Layer 2: Two or three sources you follow, not monitored.

There are specific organizers and communities whose events I nearly always want to attend. Instead of trying to remember to check their websites, I've subscribed to their newsletters or followed their Luma pages. When they post an event, it comes to me.

The important constraint here is "two or three." More than that and the signal gets lost. I'm not trying to catch everything — I'm trying to not miss the specific communities that matter most to me.

Layer 3: One recurring calendar block for "check events."

Sunday at 7pm, fifteen minutes. That's it. This is what makes the system work — not the tools, but the habit of looking. Without this, even the best aggregator in the world sits unused.

What to do with events once you find them

This is where most systems break down. You find an interesting event, you think "I should go to that," and then you close the tab and forget about it.

The fix is to be decisive immediately. When you're looking at the aggregator on Sunday:

  • If you're going: put it in your calendar right now, not "later"
  • If you might go: put it in your calendar as tentative and set a reminder three days before to confirm
  • If you're not going: close it and move on. Don't save it for "maybe"

The "maybe" pile is where events go to die. Make the decision at discovery time, not later.

Adjusting for your actual life

Not everyone's calendar has room for multiple events per month. That's fine — the system works just as well if you're only going to one event per quarter.

The minimum viable version: once a month, spend five minutes on Droppa searching for events in your city over the next thirty days. If you find one worth attending, put it in your calendar immediately. That's the whole system.

The reason I'm specific about the tools and the timing is that vague intentions don't work. "I should try to attend more events" is not a system. "Sunday evenings I check Droppa for upcoming events in SF" is a system.

The less obvious benefit

Beyond not missing specific events, there's a second-order benefit to maintaining awareness of what's happening in your local tech scene: you just know more about it.

You notice which companies are hosting events and what it signals about their culture. You see which topics are getting a lot of event activity and what that tells you about the market. You understand the texture of your local ecosystem in a way that people who don't pay attention don't.

That kind of ambient awareness is useful in ways that are hard to quantify but easy to feel when you're in a conversation and you have context that other people don't.

The system takes maybe ten minutes to set up. The maintenance is a Sunday habit. It's probably the lowest-cost high-value thing I do for my career development, which is not something I say about many things.