Maybe two months ago or so, I saw this hilarious video where a developer was having a conversation with a client. The client wanted to change the color of a button, and the developer was explaining just how much work had to go into pulling off such a “simple” request. Of course, it was a skit—a funny one—but there was truth in it too.
A few days ago, @eddiespino made a priority list for @kesolink and me. A way to keep us organized and focused on what we should tackle next for 3Speak. As I went through the list, I already knew the “scheduling posts” task would be harder than it looked. Turns out, I was right.
Not only did I have to make changes to the frontend—which was expected—but I also had to modify the uploading system. The new 3Speak website uses a different upload service, one I genuinely hope users are happy with. Tweaking it has become a near-daily task at this point, but I think I’m finally getting it to a place I can be proud of.
At any rate, it’s almost 7 p.m. where I’m at. I thought I’d be done before breakfast. Then I thought, okay, for sure after lunch. And now? Now I’m thinking I’ll take a short break and revisit this later—if my brain still brains—or just tackle it fresh tomorrow.
Fret not, though. I do have a working branch. It still has issues, yes, and there’s this one styles file that irks me to my core. But progress is progress.
I suppose the only real way to test it properly is to deploy it. That said, I strongly suspect issues will be found before the cows come home to… roost? No, that’s not it. You get my point.
MenO
God I hate when work takes more longer than it should 😂😂😭
Especially when it really shouldn't be that hard!!
I've been tackling with a database for weeks. And I was meant to be through yesterday.
But oh well, surely before lunch today...
But I think it works! It worked for me on my test account. I think we need more testers so we can find edge cases.
see if it needs more mantequilla