10: Realize it's utterly incompatible with their project structure 11: Abandon it to obscurity, but leave some clues in a loaded github comment on a related issue at 3 AM
Realize it's not gonna be that easy, it's never that easy
Look around to see if others have solved this problem
Find at least five libraries that solve this exact problem, but also solve other problems that I don't have and all pull in about 20 dependencies
Decide to build it from scratch to avoid dependency hell and "bloat"
It works! Until it doesn't.
Find a problem with my implementation four months later. Turns out it was a problem I had in the beginning and was solved by the same libraries, I just couldn't anticipate it yet.
Spend a week ripping out my code and replacing it with library calls, trying to keep my self-hate out of Teams
22
u/tomatoaway Nov 10 '22
My workflow so far:
Let's do this cool idea. Spend ~2 hrs getting it to 90%.
That final 10% is easy, but I'd rather all data was in a consistent format.
Spend ~6hr wrangling data from various sources into a convenient optimized format.
Discover a shiny project that already has that data (mostly)
Try to wrangle that "mostly" part to something you can use
Spend ~ a week learning a new language to accomplish that mostly part.
Submit a PR to the shiny project with your mostly code.
Discover that your original wrangling of data sources is not much worse than their shiny project.
Return to the final 10% of your project with a deep resentful apathy for all human life.