>>4108901>where the fuck do i get wedding photography experience without dragging my name through the mud if I fuck up the first time?Start small and work up. I started with senior portraits of friends while in school, then started doing some events / concerts (largest being Tyga), and later lots of family portraits & headshots. Did an engagement shoot with some old friends, worked out so well I offered to do their wedding at very reasonable rate. Booked two more weddings from that one, and just snowballed from there.
More standard approach is to yes, bug other established photogs about second shooting for them. Do that for a while, build experience and a portfolio, then go solo. Tons of resources online walking through a typical wedding and what to expect. One of my first jobs was kitchen staff at an event place that often hosted weddings. Got to see ~100, and get a real good idea of the general flow of things which gave me a lot more confidence going into the first one.
Weddings are honestly not that difficult to shoot. Everything else that goes into wedding photography (client communication, $, marketing, website, social media, etc) causes me way more stress than actually shooting a wedding. You should have a solid grasp of your gear though, good understanding of working with different lighting environments, and have a backup plan for anything that could go wrong. Going full-time with photo work has way more to do with your business skills than photography, and I know plenty of people that take terrible pictures but are relatively successful.
FF is definitely more versatile, but it may not be necessary depending on what your doing. A lot of my early weddings were mostly on aps-c, and I've even done paid work with 1" ILC cameras too.
>>4108915my doggo
>>4107405 
