3 ms·
Having dealt with that crap… that should be an interesting read scroll scroll scroll nod nod nod scroll scroll scroll > Recurring events Whelp, shit just got
by masklinn 8y ago
Having dealt with that crap… that should be an interesting read
scroll scroll scroll nod nod nod scroll scroll scroll
> Recurring events
Whelp, shit just got very very real, and I actually disagree with Zach here:
> If someone held a gun to your head and demanded in the next week you either 1) programmed a comprehensive system that included full support for recurring events, or 2) invent full-scale ready-to-go-to-market cold fusion, then you should abolutely start brushing up on atomic physics.
You should just beat yourself with the gun (or whatever the nearest heavy implement is) immediately, no cause to prolong the pain, you're not Harold.
- scruple 8y agoYeah. I've lived through this scenario (implement recurring events based on a calendar system in very little time). And even though I definitely had a longer runway than a week (a whole month! on top of the work that I already had on my plate), I would still agree to take the beating immediately if I was presented with that situation again. Yeah, sure, I "got it done" but it was very challenging to maintain for a while. And, of course, I learned well after the fact that what I had designed and implemented had basically, rather poorly, implemented some existing solution / FOSS library (I had essentially written some pieces of the Ruby gem ice_cube without realizing it) that I hadn't been able to find via Google at the time.