If nothing else, just make sure they come off as achievements rather than just stuff you did. We’ve all seen projects that made us go “but why? That seems like

If nothing else, just make sure they come off as achievements rather than just stuff you did. We’ve all seen projects that made us go “but why? That seems like a bad use of time.” “Migrated from MySQL to Postgres” could be a massive waste of time, or it could have made something much better. The difference between a waste and an accomplishment is what is you want the resume to reflect. A quantified outcome is one way to do that, and reflect well on some roles/projects, but not others.