3 ms·
I just lost 3 hours of my life debugging JavaScript utc vs local time issues in a top rated React datepicker component. Where I used to relish the learning from
by bayonetz 10y ago
I just lost 3 hours of my life debugging JavaScript utc vs local time issues in a top rated React datepicker component. Where I used to relish the learning from such experiences, now I feel vaguely resentful and just want that time back for more leisurely pursuits. What I've realized is there is an exponential drop off on how much time "learning experiences" like these will save me in the future. For example, for this category of debugging, it might taken me several days early on, then 1 day, then 4 hours, then 3.5, now 3, maybe 2.8 next time, etc. I think unconsciously when I was starting out I thought all this hard work I was putting in would pay off such that I'd eventually get to a level where I could basically blink and new 1000+ line projects would just appear effortlessly, bug free, and ready to go. The reality is much farther from the truth. While my investment has paid off immensely, there is still a ton of uninteresting ditch digging that still has to get done in the service of making stuff. For me all the way up to the most brilliant engineers out there, there are still plenty of 3 hour slogs left where we will never get that time back and the result won't feel like it was worth it.
- noir_lord 10y agoEverything you said and the fact that the 'surface' to learn anything well is now huge so we have lots of abstractions all of which leak and require you know a fair bit about all the layers underneath if you want to consider yourself 'good' at what you do.