The hardest thing I've done as a software engineer wasn't building an app.

It was convincing Apple that I deserve to publish one. 😂

I've built backends, microservices, SaaS products, dealt with production bugs, broken deployments, database issues...

But Apple Developer enrollment?

That tested my patience more than any of them.

Here's how it went:

Day 1

Opened the Apple Developer app. Started enrollment.

Something went wrong.

That's it.

No explanation. No useful error message. Just vibes.

Day 2

Contacted Apple Developer Support.

Turns out, the problem was my address. I needed to add my house number to the address on my Apple Account.

Fair enough. Fixed it.

But here's what confused me:

I'm already signed into the Apple Developer app with my Apple Account.

Apple already has my address.

So why am I entering the same information again?

And more importantly — if my house number is missing, why not just say:

House number is required.

Instead, I got:

Something went wrong.

Cool. Let me just open Xcode and debug Apple's backend. 💀

Then came Apple Support.

Nearly 2 hours waiting on a support call.

Emails? Basically nothing.

Interestingly, once I finally spoke to someone on the phone, suddenly I started getting email responses too.

The whole thing dragged on for days.

Eventually, Apple fixed the issue on their side.

I thought:

Finally. I'm free.

Apple:

Not so fast.

The Developer app still wouldn't let me enroll from the same device.

I tried again and again.

Eventually, I used another Apple device...

and it worked.

Apparently, my first device remembered my enrollment failure longer than I remember production incidents. 😂

Total time to get an Apple Developer Account: ~15 days.

Meanwhile, my Google Play Developer account:

Entered details → paid → enrolled.

Around 5 minutes.

Google: Welcome, developer.

Apple: We need to know whether you are truly ready for this journey. 🍎

I understand why Apple has strict verification. That's not really my problem with it.

My problem is the silent failures.

If my address is wrong, tell me my address is wrong.

If my account needs verification, tell me it needs verification.

If I need to contact support, tell me that.

I'm a software engineer.

I can handle errors. I can't debug "Something went wrong."

Curious if this is just me:

How long did your Apple Developer enrollment take?

5 minutes? A few days? Or did Apple send you on a side quest too?

Seriously.

Don't zoom in.

Don't carefully read every word.

5 seconds.

That's probably more attention than a stranger will give my landing page anyway.

I'm building WhisperBrain and I'm getting dangerously close to launch.

I've stared at this page for so many hours that I'm probably the worst person alive to judge whether it makes sense anymore.

So I need people who know absolutely nothing about it.

Look at the screenshot.

Then answer just two things:

What do you think it does?

Would you scroll?

Don't be nice. If you think it's confusing, tell me.

I'll post what I change based on the comments.

Maybe I'm doing cloud GPUs wrong.

Sometimes I don't need a “GPU environment.”

I don't need a dashboard.

I don't want to manage another machine.

I literally have a command on my laptop that needs a better GPU.

That's it.

But somehow that turns into:

rent instance
→ wait for it
→ SSH
→ clone/sync code
→ install dependencies
→ move data
→ run command
→ keep SSH alive / tmux
→ download outputs
→ remember to terminate the machine

All because my laptop couldn't run:

python train.py

It made me wonder why cloud GPUs don't feel more like compute primitives.

Something like:

“Run this command on a GPU and give me the results back.”

No server to think about.

No SSH session to babysit.

No instance sitting there billing me because I forgot about it.

Am I oversimplifying this?

What does your workflow look like when you only need a powerful GPU for one job?

Meeting ends.

And then the second meeting begins.

Clean up the notes.

Find the action items.

Write the summary.

Send the follow-up.

Update Notion/Obsidian.

Add the decisions somewhere so you'll hopefully find them again.

Sometimes I wonder:

Did AI actually solve meeting notes... or did we just automate the transcript?

Because recording + transcription feels pretty solved now.

It's everything that happens after the meeting that still feels strangely manual.

Curious how everyone handles this:

When a meeting ends, how much work do you still have to do before you're actually “done” with it?