My workflow in last 2 jobs, if I already printed something in last 3 months:
print the document
After a change of laptop / floor / other size instead of the usual A4 / fiddling with booklets / …:
go to the printer
follow instructions on the printer (usually just filling the IP address on a Mac, but I once tried testing a web app I was developing how it prints from virtual Windows when testing.. permissions were fun)
print it
realize some Unicode characters in some heading fonts in a PDF from Firefox preview didn’t work (or something)
download the stupid PDF and print it again
fill the paper from the cabinet next to the printer
remove chewed-down page, confirm everything is fixed, let the printer finish and re-print whatever is a mess
or set higher DPI if needed for images and re-print
or sign the document, scan to email, and shred the paper (because they didn’t like my electronic signature and asked me to do it for expense report or something where I have to sign-in anyway)
(not very often) debug our web app for a couple of days to convert position:absolute gantt chart into actual html table that can be paginated with repeated headers and footers
and find the least worst CSS for page orientation and margins and default zoom and logo resolutions for most common DPI that looks reasonable in at least some browsers
figure out which backgrounds make sense to force-preserve (icons) and which to remove by default (whole-page background)
preserve order of text when printing to PDF and completely remove hidden text so that search still works in various PDF readers (reasonably-ish)
Almost forgot—being in a hurry almost certainly triggers the second path through the workflow.. no idea what’s the mechanism for that tho, probably availability bias.
My workflow in last 2 jobs, if I already printed something in last 3 months:
print the document
After a change of laptop / floor / other size instead of the usual A4 / fiddling with booklets / …:
go to the printer
follow instructions on the printer (usually just filling the IP address on a Mac, but I once tried testing a web app I was developing how it prints from virtual Windows when testing.. permissions were fun)
print it
realize some Unicode characters in some heading fonts in a PDF from Firefox preview didn’t work
(or something)
download the stupid PDF and print it again
fill the paper from the cabinet next to the printer
remove chewed-down page, confirm everything is fixed, let the printer finish and re-print whatever is a mess
or set higher DPI if needed for images and re-print
or sign the document, scan to email, and shred the paper (because they didn’t like my electronic signature and asked me to do it for expense report or something where I have to sign-in anyway)
(not very often) debug our web app for a couple of days to convert position:absolute gantt chart into actual html table that can be paginated with repeated headers and footers
and find the least worst CSS for page orientation and margins and default zoom and logo resolutions for most common DPI that looks reasonable in at least some browsers
figure out which backgrounds make sense to force-preserve (icons) and which to remove by default (whole-page background)
preserve order of text when printing to PDF and completely remove hidden text so that search still works in various PDF readers (reasonably-ish)
Almost forgot—being in a hurry almost certainly triggers the second path through the workflow.. no idea what’s the mechanism for that tho, probably availability bias.