I work with relative paths:
/
../
../../
/folder/
../folder/

I got used to working with templates having strict code, so then if I need to change something, its two files (or a bunch) and a text replace does the work with an text editor.

I'm managing only two pages now (template) and use my own CMS to work the rest out, so no changed needed. If so, I do it via preferences (CMS).

Relative paths are extremely useful as explorador says.

I'd also recommend taking your workspace online but keep it in sandbox state where nobody but you can find/access it.

I develop a site on my own domain (no followed) using relative URLs so the owner can view and approve the pages. Once it's ready to go online I change all urls to full and remove no follow, add base hrefs, fix htacess, etc and load it. It usually takes 3 hours to get a small site ready for going online till it's finished (not including a shopping cart).

I used to use relative paths, but switched to absolute complete URLs for a few reasons.

I include a $domain global variable in the configuration file for each site.

Whenever a site is moved, all that has to be changed is the value for $domain and I'm good to go.

you could also include some if-else statements. like if the server path is x, then some parameter is a. if server path is y than that same parameter is b. this works for image upload locations, database connection details and lots of over things