hipjim

I built a small command-line tool that lets you query a PostgreSQL database using natural language instead of SQL.

It's nothing revolutionary - just a simple CLI wrapper around the OpenAI API with PostgreSQL integration, but it's been incredibly useful for my own work. The code analyzes your database schema to provide context to the LLM, which helps generate more accurate queries.

There are so many more alternatives for the JVM these days - languages like Scala, Kotlin and Clojure - I wonder why these companies do not invest in the future and still push the old Java around.

What a bull* article. There is a lot of Scala traction even in the big enterprises. What is sure is that Java lost a lot of ground with Oracle at the driving wheel.

stacktrace from hell - a consequence of stacking frameworks over frameworks. This is the state of our craft as of today :(. This has nothing to do with Java as a prog language. Java stack traces are quite nice :-)

Point 1 is silly - this depends greatly on what your application needs to do. If you need to store the image together with the metadata or other information related to the image that is transactional data - then storing the image in the database is the way to go. This also helps a lot with database backups, migrations etc..