Im on the fedi doin fedi things.

  • 460 Posts
  • 596 Comments
Joined 1 year ago
cake
Cake day: December 27th, 2024

help-circle



  • It helps! Ive seen it with two jobs completely change the culture around code review.

    • Instead of you/team lead being the bad guy, its now the code/process.
    • Code becomes more stable and releases actually become more frequent.
    • If something goes wrong, your VM/docker/box/etc… can just be re-spun up by the same process.
    • Easier to onboard since the same build process is in the CI. And is constantly being used rather than relying on the README (that may not have been updated in a while).

    Mind you its not perfect of course. You can still “Vibe” test and/or remove tests that dont work. And make the project more brittle. Or go overboard with lint rules (I actually had to break up a fight with that one). But its much better than the old process of merge and pray.




















  • Probably. I have a couple of heltec v3s. I personally got 2 of them so I could test out the LoRa and placement before my solar setup was done. Now they are permanently wall nodes next to a window. Room (client) -> Solar (client_base) -> other nodes. Works well.

    They are decent at most things EXCEPT solar because they take a bit of power and have a nasty habit of bootlooping at certain voltages. It only really occurs if you want them to be solar.