Arnim Läuger

To build local changes I just call `make` from bash which typically compiles only the modified source files, creates intermediate libraries, and links the bin files. I tried with the...

> Do you see any way around that? Since make decides for rebuild based on the files' timestamps, you'd have to avoid touching `user_version.h` if its content won't change. E.g....

> Looks like I need to make another attempt at setting those variables through `EXTRA_CCFLAGS` rather than `user_version.h` Hm, maybe the whole escaping can be isolated to a central instance...

And while we're at it - Recompilation of some source files due to volatile dependencies isn't actually a big deal on my machine here. More time is sunken with [pip...

> I need more time to figure out why that is i.e. which manipulations run by build-esp32 cause this. Sounds like a tough job. Maybe `make -d` provides some pointers.

Terry, your separation into these 4 categories adds an interesting dimension with respect to quality: - As far as I understand, code in **modules** and **utils** provides self-contained functionality, "executable...

A matrix is probably ok for an overview. Though I'm not a fan of encoding information exclusively with colours. As a con: You'd have to iterate over the matrix again...

I'm not familiar with the ads1115 architecture, but I see that you moved the I2C reset command into a dedicated function with #2231 - is this issue here still applicable...

> the reset function does not belong to ads1115 module. After reading through the [I2C spec](https://www.nxp.com/docs/en/user-guide/UM10204.pdf) chapters for "General call address" and "Software reset" I also think that the generic...

Issue should be kept.