I'm primarily a lurker, but after reading this I had to add a comment. I recently had this exact same experience across multiple different languages and IDE's e

I'm primarily a lurker, but after reading this I had to add a comment. I recently had this exact same experience across multiple different languages and IDE's etc. Most recently it was trying to get a laravel PHP app to work on my 2015 MBP, (which apparently was using a system installed version of php, preventing me from connecting to a postgres database on AWS using SSL because it wasn't compiled with SSL support...) Today it was an ios app that started to fail compile because 1 of the devs used an ios 13.0 only feature. Last week it was a .net core windows service, that I had to read several pages of documentation on, in order to upgrade from 2.2 to 3.1, in order to simply add telemetry reporting. I feel the premise of this post is more around the concept than it is specifically about gradle issues. It's simply this feeling of drowning in just getting something back to a working state through the endless cycle of trial/error, StackOverflow, and googling different terms. Too many times what started as a journey of inspiration when I wanted to add a cool feature/idea turns into hours of frustration. I normally end up getting it to work, but all my motivation is gone and I sit there and ponder how is it possible to be doing this for 10+ years, and find myself constantly in these ruts across the board. It's articles like this rant that make me feel that I'm not alone!