.co/mmit

The first two letters are missing.

The commitment isn't.

Why "mmit"?

Because every project begins before the commit.

The code.

The bugs.

The frustration.

The debugging session that somehow fixes itself after a coffee break.

The commit is only the part everyone gets to see.

My Workflow

⎗
✓
Think.

Code.

Break something.

Fix something else.

Test.

Commit.

Push.

Deploy.

Repeat.

Simple.

Not always easy.

Every Commit Tells a Story

Some commits are exciting.

⎗
✓
feat: add new homepage

Some are satisfying.

⎗
✓
fix: navbar no longer explodes on mobile

Some are... honest.

⎗

1	why does this finally work

And some deserve absolutely no explanation.

⎗

1	final-final-v3-please-work

We've all been there.

Why I Like Git

Git remembers.

Every mistake.

Every improvement.

Every tiny step.

It reminds me that progress isn't measured by perfect code.

It's measured by one commit after another.

Deployment Day

There's a small moment before every deployment.

You stare at the terminal.

⎗

git add .

git commit -m "..."

git push

Then...

You wait.

Sometimes for a few seconds.

Sometimes for your heart rate to return to normal.

Philosophy

Life would be easier if it had version control.

⎗

1
2
3

$ git checkout yesterday

error: pathspec 'yesterday' did not match any commit

Unfortunately...

There is no branch called Yesterday.

Even if one existed,
or you started creating it right now...

that commit would eventually become yesterday.

No commit to return to.

No way to rewrite every mistake.

The past is always one step ahead of us.

So the best we can do is keep committing better versions of ourselves.

Current Status

⎗
✓
Repository : Clean
Branch     : main
Changes    : 0
Last Deploy: Successful
Confidence : 50%
Hope        : 100%

Favorite Command

⎗

1	git push origin main

That single line has launched countless ideas into the internet.

"A website isn't finished when it's deployed.

It's finished when the next commit begins."

— aspz3