Not sure why downvoted. HTMX does seem to be becoming popular. I prefer the simplicity of it.

Okay, I see what you’re saying and I concur. Thanks for the clarifying comment! 🫡

I’m willing to bet a team of untrained, uneducated, software/data engineers receiving big salaries are responsible for this.

It’s my understanding that big brand banks live on top of brittle, low quality, poorly tested code- and that’s if they’re not straight up using excel to run production processes.

Ah yes, the project that nobody asked for, and it has to be worth it because you still have your actual assigned work to hack.

I remember that feeling of not seeing the light at the end of the tunnel while having invested multiple days into a side quest that my boss never asked for (but would ultimately make me, or the team, more productive). I remember being more junior in my career and fighting that devil on my shoulder as it’s saying, “it’s turned into spaghetti! Just abandon it and get back to your deadlines before you go too far!”

Fair!

Python, and its need for virtual environments, is what really drove me to master Docker.

Docker is like, my favorite utility tool, for both deployment AND development (my replacement for Python virtual environments). I wanted to hear more of why I shouldn’t use it also.

Does your ad blocker block ads for YouTube and YouTube Music apps on iOS?

The meme itself isn’t bashing Docker.

Single responsibility principle: is your GetData() function responsible for getting data? Or is it responsible for creating a new database connection and also using that to go get the data?

Start naming your functions by what they really do. When you see the word “and” in your function name, you know your function is responsible for too much.

Dependency injection is the difference between CreateDatabaseConnectionAndGetData() and GetData(connection ConnectionType).

In the first example, that function will always connect to the specific db that you hard coded in it. It probably has to also read in a config file to get the connection details. Maybe you should name it ReadConfigAndCreateDatabaseConnectionAndGetData()?

In the second example, I can pass in a MySQL connection or PostgreSQL connection, or some dummy connection for testing.

Keep all that nasty dirty untestable code in one place and spare your business logic from owning all of that.

My condolences. This is the stuff Robert C. Martin talks about in his book “Clean Architecture”; database vendors locking you into their tech.

Your boss isn’t just a developer, he’s a *db developer *. From his perspective, the database is a god rather than a means to store information.

I should add onto my original post that the queries should strive to be as database agnostic as possible. This alleviates a lot of pain when the company decides to move from one DBMS to another.

Is it safe to assume your stored procedures have lots of DBMS specific functions and syntax sprinkled among the code?

“Did I say ‘we want it to do this OR that?’ I meant we wanted it to do this ‘AND’ that!” 🤦‍♂️

I’m in this boat. I just want to see lemmy succeed as a legit Reddit alternative.

Edit: WefWef has made me feel right at home, coming from the Apollo app. If you haven’t tried it, check it out! (https://wefwef.app)