3 ms·
The pain points sound pretty trivial though. You notice a deprecation warning in the logs, or an email from GitHub and you make a 1 line commit to bump the nod
by dkdbejwi383 2y ago
The pain points sound pretty trivial though.
You notice a deprecation warning in the logs, or an email from GitHub and you make a 1 line commit to bump the node version. Easy.
Sure you can make typos that you don’t spot until you’ve pushed and the action doesn’t run, but I quickly learned to stop being lazy and actually think about what I’m writing, and get someone else to do an actual review (not just scroll down and up and give it a LGTM).
My experience is same as the commenter above, it’s relatively set and forget. A few minutes setup work for hours and hours of benefit over years of builds.
- ironmagma 2y agoThe non-solution solution, to simply downplay the issues instead of fixing them. You can solve almost anything this way, but also isn't it nice when things around you aren't universally slightly broken?
- dkdbejwi383 2y agoI guess I'd disagree that this is "slightly broken". That's just how it works. I don't think there's some universally perfect solution that magically just works all the time and never needs intervention or updating.
- IshKebab 2y ago> That's just how it works. It's how it works now. It doesn't have to forever. We can imagine a future in which it works in a better way. One that isn't so annoying. > I don't think there's some universally perfect solution that magically just works all the time and never needs intervention or updating. Again you seem to be confused as to what the issue is. Maintenance is not painful. Initial development is.