Stress testing
-
My Tiny True Type engine for LVGL uncovered a long standing but previously hidden bug in LVGL's POSIX filesystem caching subsystem. Because of that the LVGL devs are banging on my library something fierce to tease the errors out so they can fix it. And it's making me nervous, even though my code is holding up fine. I should have included in the license: NOT FOR USE FOR ANY PURPOSE WHICH MAY MAKE THE AUTHOR ANXIOUS :~ It's being stress tested, and I'm the one who is stressed.
To err is human. Fortune favors the monsters.
-
My Tiny True Type engine for LVGL uncovered a long standing but previously hidden bug in LVGL's POSIX filesystem caching subsystem. Because of that the LVGL devs are banging on my library something fierce to tease the errors out so they can fix it. And it's making me nervous, even though my code is holding up fine. I should have included in the license: NOT FOR USE FOR ANY PURPOSE WHICH MAY MAKE THE AUTHOR ANXIOUS :~ It's being stress tested, and I'm the one who is stressed.
To err is human. Fortune favors the monsters.
-
This is a similar feeling to a parent moving their barely grown child out of the house. Nothing much you can do. Just hope the library doesn’t ask to move back home in 3 months!
As an aside, I've been hunting for rasterization code to handle complex anti-aliasing for basic vector shapes. Couldn't find it, but I did find an SVG interpreter in C i ported over to my library. Anti-aliased everything. It's not full SVG, but it's a significant subset. Not the fastest thing in the world, but good for simple designs, and is a pretty novel way to "skin" a user interface. :) Pretty excited. I *just* got it working. And all because I couldn't antialias a filled ellipse. ha!
To err is human. Fortune favors the monsters.
-
My Tiny True Type engine for LVGL uncovered a long standing but previously hidden bug in LVGL's POSIX filesystem caching subsystem. Because of that the LVGL devs are banging on my library something fierce to tease the errors out so they can fix it. And it's making me nervous, even though my code is holding up fine. I should have included in the license: NOT FOR USE FOR ANY PURPOSE WHICH MAY MAKE THE AUTHOR ANXIOUS :~ It's being stress tested, and I'm the one who is stressed.
To err is human. Fortune favors the monsters.
honey the codewitch wrote:
It's being stress tested, and I'm the one who is stressed.
I've never thought of it that way, but you're absolutely right. "Are you stress-testing the code, or the coder?" :-) I suppose one can lead to the other. But look at it this way (if I understood it correctly), your library is exposing flaws at lower layers and people are interested in your library to root them out and fix them, as nothing else has ever tried to push things that far. I'd take that as praise.