The lesson is solid, figure out which parts of the system already work like a charm and stop reinventing the wheel there, instead, throw your energy at the seams you actually have control over. the way you walked through your analysis - starting with static code poking around, then making educated guesses, then actually watching what happens at runtime - that's worth nailing down formally because most RE tutorials either gloss over these steps or act like they're all basically the same thing, when honestly they're giving you pretty different levels of confidence in what you're learning. Your take on chinese LLMs being more loose with the rules but sometimes wonky on accuracy is a useful signpost, but the piece would hit different if you actually showed where that speed-versus-accuracy gamble either saved or screwed you - like which theories did you chase down differently because of that trade-off? And the fact that you went from zero mobile RE experience to shipping something solid in 17 commits and getting actual velocity is the kind of realistic timeline that usually gets buried, which is a shame because people coming from web dev especially need to know how long is this actually gonna take to figure out if they can even afford to learn this.