Timeline for I am spending more time installing software than coding. Why?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2021 at 18:59 | comment | added | Adam Dobrawy | If the project is front-end, it can be verified whether building with an updated package changes the delivered result code too. It is possible that the change concerns unused code removed during tree-shaking etc. This, in turn, allows you to automatically reduce the scope of future updates, because having a smaller version diff and being "up to date" makes it easier to adapt to future changes. | |
| Aug 26, 2021 at 18:59 | comment | added | Adam Dobrawy | I agree with everything. As a person who developed a small startup, instead of abandoning the update, it is worth considering simplifying and accelerating the process of preparing and verifying updated packages. If the project has a high automatic test coverage and is configured, it is quite effective to use bots that automatically create pull-requests, eg Renovate / pyup. Then you are aware and have immediate information which changes are safe to install and which will require work that requires additional planning. | |
| Jan 18, 2021 at 12:41 | audit | First posts | |||
| Jan 18, 2021 at 12:41 | |||||
| Jan 16, 2021 at 16:19 | comment | added | Max H. Balsmeier | yep, that's why I am always doing updates early | |
| Jan 16, 2021 at 6:47 | comment | added | Hagen von Eitzen | Also: Be ahead with compliance. If you use function or feature foobar and it already brings you a "deprecated" warning, be sure to replace it early and not only after some update gets rid of foobar altogether | |
| Jan 15, 2021 at 17:09 | comment | added | Jerry101 | Good answer. Another tip is to seek ways to reduce en.wikipedia.org/wiki/Dependency_hell e.g. don't use pips that are particularly fragile. Add looser binding e.g. environment variables or symlinks that point to apt libs that move. Use a virtualenv per Python project so each one has a minimal set of pips and you can build a new virtualenv (from a requirements.txt file) before deleting the previous one. Try pipenv and conda. | |
| Jan 15, 2021 at 16:22 | comment | added | Useless | There may be some element of the role expanding to fill the space available, but dev environments are genuinely more complicated than during, say, the thirteen-year interregnum between C++ standards when you might stick with GCC 2.95.x for years at a time, and Perl 5 was used for > 20 years. | |
| Jan 15, 2021 at 16:13 | comment | added | Steve | "Those are paid full-time jobs" - by all accounts, that's precisely the problem! | |
| Jan 15, 2021 at 15:27 | vote | accept | Max H. Balsmeier | ||
| Jan 15, 2021 at 15:24 | history | answered | Useless | CC BY-SA 4.0 |