@GreenSky I'm sorry, but the only reason George Orwell would be shocked at all about anything happening in 2024 would be because he would learn that Aldous Huxley was right.
It's fun when you edit code that's been written by someone with the job title "Software Architect" and there are so many mistakes in it that it takes you two days to clean it up. 😅
Hmmm, I keep getting deeper and deeper into this rabbit hole and I keep running into more problems. I may have to write all this code from scratch, it at least the part of it I need.
This is the danger of copying code verbatim from other projects. Errors are cumulative.
I managed to get the code to compile, but it doesn't run, and I suspect it's incompatible with the architecture it was supposed to run under in the first place.
I think cutting my losses at this point and starting over is the best plan.
I'll get an older version that I wrote myself to work. I really wanted to avoid that since the whole idea is to replace my old boilerplate code, but at this point time is more important than correctness. I need to get this working to get the project done soon.
Good news — the EPA updated the air quality index on May 6th.
Good news: AQI now includes a wider range of conditions that make people sick.
Complicated news: since AQI is based on health impacts rather than an absolute measure of pollutants, anyone basing research or analysis on AQI should expect the definition of a one unit difference in AQI to change.
Time to update my own monitoring/early warning system
In case you're wondering, the part I'm complaining about is the useless comment above the line of code that is a literal restatement of what the code does without contributing to clarity or understanding for anyone reading said code.