Build yourself a weather station
This is a really cool project that I would perhaps like to try myself one day! A home weather station has been on my list for several years.<p>Now I will say something negative. It&#x27;s a nit, but I think it needs to be said.<p>I&#x27;ve seen a lot of these &quot;In which I write a (perhaps series of) essays on building X using all kinds of cool tech you&#x27;d probably like to play with when you could get the same result with less than ten bucks, maybe an hour or two, and just a handful of code, if any&quot;<p>I&#x27;m okay with and completely love &quot;Let&#x27;s do something cool and learn!&quot; I&#x27;m not okay with &quot;I have this problem, so let me by implication teach you how you should architect problems when you run across them&quot; We need to clearly differentiate. You should not, and you should never, start with an important project and begin speculating on what cool tech you could play with.<p>Playing and learning are great. Yay! Adding structure and complexity where none is needed is an antipattern if you&#x27;re doing anything of value for yourself or somebody else. This stack might end up being necessary. Absolutely. Make the problem &quot;prove&quot; that it&#x27;s necessary. You should have a clear and unambiguous process for choosing a stack; do it by necessity. Never even accidentally teach that you do it by &quot;hey, that&#x27;s cool!&quot; People end up doing that, and somebody ends up having to clean it up.<p>tl;dr Love fun projects like this. Keep &#x27;em coming. Just please be sure you&#x27;re clear to the reader that they&#x27;re learning&#x2F;fun projects.<p>* Perfectly fine to add a tech or two to a new project in order to learn-as-you-work, it should just be done with the upmost care and a close eye to how much team bandwidth it&#x27;s using versus the value being provided and how you&#x27;d back it out if you had to.