feat: update export statistics with new user data and extended date range for graphs

- Bump active users from 351 to 355 and total contributions from 8477 to 8726 in dataset export
- Update per-user contribution counts and percentages for IHateForALiving, BordedDev, CoreFusionX, and D-4got10-01
- Add Burns11Mor to mentions list and adjust mention counts for multiple users
- Replace graph PNGs with extended date range from 2024-11-07 to 2025-01-14, replacing previous 2024-12-28 cutoff
- Append new post content for users 12bitfloat and AceDev in their respective export files

export/rants-Nmeri17.txt

@@ -28,4 +28,14 @@ I know I'm just whining atp instead of moving on something else. For lack of any
 
 Unbelievable,Disclaimer: This joke will be lost in translation but I can't help but make it
 
-In my country, you can use the phrase "it's not beans" to describe something difficult eg "that ielts exam no be beans". Given my recent woes with spring boot, I can also say "spring webflux no be beans". But it's funny to me because the framework calls objects bound to the container "beans" so it's a nerdy, don't leave me joke```
+In my country, you can use the phrase "it's not beans" to describe something difficult eg "that ielts exam no be beans". Given my recent woes with spring boot, I can also say "spring webflux no be beans". But it's funny to me because the framework calls objects bound to the container "beans" so it's a nerdy, don't leave me joke,That time you would have used to test that code in postman, bravely muster the werewithal to write automated tests instead. It's a onetime investment that keeps malfunction in check until code is altered
+
+I acknowledge the fact that it's not always possible. You may have gotten thrown in headfirst into unfamiliar territory ie tech stack, or inherit a monolith where no tests were pioneered. Or you may be strongly constrained for time. But in events that you can, it's worthwhile
+
+Whether automated or manual, Testing your work the least professional thing to do before handover. Might as well swallow the bitter pill of avoiding the gui shortcut, and write those certifications once and get it over with
+
+My preference is to write a boilerplate that gets generated each time I create a new module/resource management classes. Another strategy is to write them immediately after completing implementation of each endpoint/user story/feature, even if they're not run immediately. That way, they don't pile up in the end
+
+Or you could try the tdd that everyone else cherishes. Whatever works for you, the end justifies the means,I would batter this nigga if I could
+
+My database migrations are failing after setting a 3 character max length on an integer field with default value 200. I attempt to investigate why and after numerous back and forth, this dude reveals 200 is in fact greater than 998```