Being a Developer and Creator: Two Worlds That Shouldn't Mix (But Do)

From 9am to 6pm I'm a software engineer. From 9pm to 12am I'm a gaming streamer. And somewhere in between, I'm just me trying to make it all work.

The "Not Enough in Either" Syndrome

At work: "I should be studying more, other devs know more than me."

In streaming: "I should be more consistent, other creators post daily."

It's impostor syndrome, but doubled. You don't just feel like you're not enough in one thing, but in two.

The reality that took me years to accept: it's okay not to be the best at either. I can be a good developer AND a decent creator. I don't have to choose.

The Skills That Transfer

What's surprising is how much both worlds connect.

From Development to Content

Debugging = OBS Troubleshooting

When the stream goes down, I have to diagnose: Is it the encoder? The network? A software conflict? It's the same mental process as debugging code.

// Debugging code
1. Reproduce the error
2. Isolate the cause
3. Test hypotheses
4. Implement solution
5. Verify it works

// Troubleshooting stream
1. Identify when it fails
2. Check OBS logs
3. Test configurations
4. Change settings
5. Test stream before going live

Automation

As a developer, I automate everything I can. In streaming:

• Scripts to change scenes automatically
• Discord/Twitch bots I made myself
• Pipelines to upload clips to multiple platforms

Systematic Thinking

A content channel is a system. It has inputs (ideas, time, energy), processes (recording, editing, publishing), and outputs (videos, engagement, growth). Optimizing that system uses the same skills as optimizing code.

From Content to Development

Communication

After years of explaining character builds to viewers, explaining software architecture in meetings is easier. I learned to simplify complex concepts.

Feedback Loops

In content, feedback is immediate: viewers leave if it's boring, comments tell you what works. That made me better at receiving code reviews and feedback at work.

Resilience

I've had streams with 0 viewers. I've uploaded videos nobody watched. That builds thick skin. When a PR gets rejected or a project fails, it hurts less.

The Logistics of Time

The scarcest resource isn't money, it's time. Here's how I divide it:

Typical Day

6:30am  - Wake up
7:00am  - Exercise/shower
8:00am  - Breakfast + check notifications
9:00am  - WORK
6:00pm  - End of work
6:30pm  - Dinner + rest
8:00pm  - Prep for stream/video editing
9:00pm  - STREAM (3 days/week) or editing
12:00am - Sleep

What I Sacrificed

• TV series (I barely watch any)
• Socializing on weekdays
• Playing games "just for fun" (everything is potential content)
• Sleep (sometimes)

What I Don't Sacrifice

• Weekends with my partner
• Exercise (non-negotiable for mental health)
• 7 hours of sleep minimum (most days)

Why This Portfolio Unites Both Worlds

Many developers have code portfolios. Many creators have link pages. Few have both in the same place.

This portfolio exists because I got tired of fragmenting my identity:

• LinkedIn: only the developer
• Twitter: only the creator
• Resume: formal code

Here I can be both. The projects section has my code. The creator section has my content. The blog has both. It's honest about who I am.

The Risk

A recruiter might see the gaming content and think "not serious." A viewer might see the code and think "boring nerd."

But people who value authenticity will appreciate the combination. Those are the people I want to work with/create for.

The Uncertain Future

I don't know which one will "win" in the long run.

Scenario A: Development remains my main career, content is a serious hobby. Scenario B: Content grows enough to be significant secondary income. Scenario C: Something completely different that I can't predict.

And it's okay not to know. Life doesn't require a 10-year plan.

Advice for Other Developer-Creators

If you're at this intersection, here's what I learned:

1. Don't Hide Either Identity

Authenticity is your competitive advantage. There are millions of developers and millions of creators. There are few developer-creators.

2. Use Your Development Skills

You can do things other creators can't:

• Custom websites
• Bots and automations
• Data analysis of your audience
• Your own tools

3. Set Clear Boundaries

Work doesn't invade content time. Content doesn't invade sleep. Health is non-negotiable.

4. Accept the Tradeoffs

You won't grow as fast as someone full-time in content. You won't have as many side projects as someone who doesn't create content. And that's okay.

5. Document the Journey

This post exists because documenting helps process. And maybe it will help someone else in the same situation.

Conclusion

Being a developer and creator is hard. It's time that doesn't stretch far enough, energy that gets divided, and the constant feeling that you should be doing "the other thing."

But it's also unique. The skills complement each other. The communities cross over. And at the end of the day, I'm doing two things I genuinely enjoy.

Is it sustainable forever? I don't know. Is it what I want now? Yes.

And now is the only thing I have guaranteed.