Reposted by Florida Man, PhD
My biggest piece of writing advice is figure out when you can actually write. It's really uncommon to have a brain that can write just whenever. What are your core hours? Figure those out and don't torture yourself by trying to be productive outside of them.
9 replies
32 reposts
149 likes
This! It took a shameful # of years of my PhD to figure this out. It also becomes a question of "can I reorganize my life in order to ensure a max % of these hours are available for writing instead of, say, sitting in meetings?"
0 replies
0 reposts
2 likes
But also: I think we're using slightly different terminology here; I'm treating access and preservation as inextricably linked in an online/digital context; digital preservation absent any of the infrastructure for digital access is a very different (and cheaper) beast.
1 replies
0 reposts
1 likes
Security is what links them; preservation, under conditions of digital access, is more precarious due to access opening up first- and second-order risks re: dataset loss.
1 replies
0 reposts
0 likes
...and also ruined by the cinematic equivalent of "this meeting should've been an email"
0 replies
0 reposts
1 likes
Additionally, as web dev gets more complex w/ more tooling, the sheer qty of code used in the average website (and the # of smaller projects it depends on) balloons. With NPM I have to worry about the security status of 100s of discrete chunks of code on a daily basis.
1 replies
0 reposts
1 likes
But the backups of our archives maintained by one of the college sysadmins require much less time and energy from the devs--if I had the option of containerizing our archive and cutting it off from the internet (but maintaining internal access) my maintenance workload would drop by like 80%.
1 replies
0 reposts
2 likes