//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
Profile
Loading...
Research software engineer #RSE @Harvard #rstats | #python | climate science | public health Research Software Engineering for Reproducible Science
Data go brrrr








Loading...
In today’s hypercapitalist Internet landscape every single thing that you experience — voluntarily or not — is to turn you into a customer… That’s why I’m happy to be working with today’s sponsor, outside! I’m not selling anything, I just wanna remind you to go outside
At this point I think I wanna become an expert in software engineering in academia and HPC just to prove it can be done… it’s so bloody irritating how data scientists in industry are like, “just develop in a container” and “just get an AWS account” and all their problems go away
I’m more and more convinced every day that I work in technology, especially with code, that you should be using instant messaging (like slack) to do debugging and troubleshooting sessions.. it just doesn’t make sense to zoom code and not have any of your commands recorded
Istg this kinda thing is beyond frustrating not because it’s not a burden to create reproducible science — it is, but what’s more irritating to me is that this burden actually gets lighter the earlier you implement your reproducibility strategy…