Shell script time-savers are handy. Why? They give you time to focus on important things rather than tedious yak shaving. The time it takes to write a little script is hardly anything compared to the time it saves.
No programming language is perfect. There is not even a single best language; there are only languages well suited or perhaps poorly suited for particular purposes.
Last time I provided some quick shell script time-savers. The goal of automation is saving time and providing focus on important things rather than tedious yak shaving. The time it takes to write a little script is hardly anything compared to the time it saves.
So here are some more useful tips including how to list folders by size, read and verify user input, and find files by date, loop over them and apply a command (like mv or rm) . . .
That’s weird! Suddenly, you try to inject a dependency in your Spring Boot application, but it’s like
@Autowired stopped working.
You will see this in several ways. IntelliJ will provide a warning from the Spring plugin, which says “Could not autowire. No beans of ‘YourBeanName’ type found.”
At runtime, Spring itself will fail with a message like:
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.scottshipp.www.YourBeanName' available: expected at least 1 bean which qualifies as autowire candidate.
If you have a multi-environment dev team with some of your staff using MacOS and some using one flavor of Linux and some using another flavor of Linux like Fedora then you might be tempted to try out virtualizing the development environment so there’s no weird configuration bugs (“works on my machine”). This might lead you to trying out Vagrant which nicely manages all the boxes and their configuration for you.