Progress is a series of setbacks. "The error message is different this time. Hooray!"
-
I got my SVG code parsing and more or less accurately rendering exactly one document. Found out my float point peephole parsing was off in some cases, and that my understanding of SVG path syntax was lacking. Correcting for what I learned and finding that bug dramatically improved my results, but... I introduced errors in the vector graphics engine's antialiasing somehow. Not sure what I did, or what changed. Yikes! No other document other than the one renders at all, but I'm not as concerned about that at the moment. What a mess. It just reminds me of any significant project though. I have one at work where, with demo coming up, we had to do a last minute swap of the hardware. Issue is we already had that swap in the pipeline, but somebody else nixed it due to it using a different cell protocol and them having to rewrite their code. (Not someone I work with directly usually - I'm actually working with a client, and another team - this coder is on that other team - and I'm not trying to dish on him - this was all a misunderstanding). We get the module swapped, and run into power supply problems. Fix that, run into some additional bugs. Finally, late night EST we had a deliverable. And honestly, some of that could have been avoided if I could have foreseen one of the issues we ended up with back when the project was spec'd. Progress lurches. They say 80% of goth is lint rolling.* Well 80% of software development is having the patience to roll with the punches and eat your mistakes. * The other 20% I think involves being hopelessly depressed, but that may apply to software as well.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I got my SVG code parsing and more or less accurately rendering exactly one document. Found out my float point peephole parsing was off in some cases, and that my understanding of SVG path syntax was lacking. Correcting for what I learned and finding that bug dramatically improved my results, but... I introduced errors in the vector graphics engine's antialiasing somehow. Not sure what I did, or what changed. Yikes! No other document other than the one renders at all, but I'm not as concerned about that at the moment. What a mess. It just reminds me of any significant project though. I have one at work where, with demo coming up, we had to do a last minute swap of the hardware. Issue is we already had that swap in the pipeline, but somebody else nixed it due to it using a different cell protocol and them having to rewrite their code. (Not someone I work with directly usually - I'm actually working with a client, and another team - this coder is on that other team - and I'm not trying to dish on him - this was all a misunderstanding). We get the module swapped, and run into power supply problems. Fix that, run into some additional bugs. Finally, late night EST we had a deliverable. And honestly, some of that could have been avoided if I could have foreseen one of the issues we ended up with back when the project was spec'd. Progress lurches. They say 80% of goth is lint rolling.* Well 80% of software development is having the patience to roll with the punches and eat your mistakes. * The other 20% I think involves being hopelessly depressed, but that may apply to software as well.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix