A Java Geek weekly 91

Java is the first language I learned in my career. Its structure is foundational in my early years of understanding programming concepts. After going through several other languages with very different approaches, I’ve widened my point of view. Today, I want to reflect on the idea of inheritance.

The Standard Commits format is a structured approach to writing commit messages that enhance clarity and consistency in version control systems. This format is particularly beneficial for projects with multiple contributors, as it provides a common language for describing changes. Without getting lost in too many frills:

Why use Standard Commits?

• Create a history that is easily greppable and log-like
• Make commits context-rich so that they are easily interpretable even in the future
• Bring consistency even among commits of different people
• Let projects relying on the repo determine compatibility with new changes just by looking at the commits headers

I don’t remember any work getting committed this release cycle on parallellizing INSERT, let alone parallelizing COPY or MERGE, and I can’t find this supposed new feature in any of the changelogs that track PG18, nor is it mentioned in the COPY docs for PG18.

• Java CAN be fast - With the right approach
• Hardware sympathy - Know your CPU and memory
• Question conventions - Standard library isn’t sacred
• Batch operations - Amortize costs
• Measure everything - Benchmarks guide optimization