If you're interested in atproto development but don't have a project in mind you can start by hosting your data (PDS). Then hosting a feed or a moderation service (labeler).
You probably won't need to host your own event log (relay), indexer, app API, or client app but you're free to do so.

atproto is already a way richer ecosystem than ActivityPub which is basically a gazillion microblogging platforms, all of them unmaintainable monoliths that refuse to follow the protocol's spec just so they can stay compatible with Mastodon.

Not everything has to be on atproto. A cloud drive, for example, is not great if all your files have to be public. But having login with atproto and everything else off-protocol could be an attractive proposition. Way better than "Log in with Facebook" or whatever.

The public has better things to do than learning about decentralized protocols just to use an app. Nobody's demanding you learn about battery chemistry and kinetic energy before selling you a car.
It's OK to use language all your users will understand.
#atproto

I’m glad people with a lot more patience than me are gently correcting that person who is very confidently wrong on the ATProto feed.

Don't feel bad for not having your main account on a self-hosted PDS. For almost everyone it's pointless other than it being a learning exercise.
You're better off setting up rotation keys/backups in case you ever need to migrate (you probably won't).

I'm just glad Liam Neeson was able to get her back.

There are too many people who can write code but haven't learned to think like an engineer and the overconfidence it creates is detrimental to them and everyone around them.

How I made my new Linux laptop (almost) as convenient as my MacBook. Best of both worlds!