Dimelo Waterson

There's a reason many universities start with Java- it has strict rules and lays out code in a straightforward (if excessively-boiler-plate-heavy) way. For a beginner, Java is an excellent way to learn the fundamentals of programming before taking off the training wheels and continuing in more flexible, less-syntactically-rigorous direction like Python or JavaScript.

Sticking to a language before moving on is a common goal. However, in reality you are going to transition as you find languages that better suit you or your organization's requirements. Start with Java, not because it is optimal for your end goals, but because it will teach you what you like and dislike about programming and because your instructor is more familiar with it. That will give you a valuable perspective and allow you to make a more informed decision later.

There are many ways to solve problems in different languages, but the "best" language pragmatically is the one that you feel most comfortable using. In that respect, programming is like woodworking- you want to let the tool do the work. If there is another language that is "better" objectively but more difficult or confusing to you, you will counteract the anticipated benefits by having to struggle to write code.

Coming from a Debian-based Linux background, using the Ubuntu base image for my Docker containers was a natural choice. However, the overhead, even on the impressively-slimmed Hub images, was hard to justify. Seeking to create images that were "just right" in size, without unused packages or dependencies, I made the switch to Alpine.

Alpine's modified BusyBox has a surprising amount of functionality, and the package repository contains plenty of muslc-safe versions of commonly-used packages. It's been a valuable exercise in doing more with less, and, as Alpine is keen to point out, an image with fewer packages makes for a more sustainable environment with a smaller attack surface.

My only regret is that Alpine's documentation leaves a lot to be desired.

I need to add a DBMS to my stack, but I don't know which. I'm tempted to learn SQLite since it would be useful to me with its focus on local access without concurrency. However, doing so feels like I would be defeating the purpose of trying to expand my skill set since it seems like most enterprise applications have the opposite requirements.

To be able to apply what I learn to more projects, what should I try to learn? MySQL? PostgreSQL? Something else? Is there a comfortable middle ground between high applicability and ease of use?