Code never lies; comments sometimes do.

WASM is simply further down the rabbit hole for someone who is new to programming (but not someone who’s already a programmer and just doesn’t focus on web dev today). You are likely far less beginner than you think if you’re making decisions like “I’m going to compile my software written in Rust targeting WASM so I can demo it.”

Python, and dynamically typed languages in general, are known as being great for beginners. However, I feel that while they’re fun for beginners, they should only be used if you really know what you’re doing, as the code can get messy real fast without some guard rails in place (static typing being a big one).

I’ve found Docker helpful when I want to use it to build binaries or use CLI tools that may not be available directly on the CICD platform. Also, Docker makes it easier to run the same code on MacOS that I ended up running on a Linux CICD server.

What would you consider to be overuse of containers?

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.

Damn, this meme slaps so hard. I didn't chase any friends down there, but I thought it sounded like a secret nerd club that I wanted to be a part of. Using Linux is a part of my daily life now, professionally and personally, 10 years later.

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!”

Docker builds are not reproducible

What makes you say that?

My team relies on Docker because it is reproducible…

The meme itself isn’t bashing Docker.

Here’s a few from me:

• How many separate projects are developers working on at any given time? (Because I want to know if they expect developers to be context switching all the time.)

• Is anyone sitting there with a stop watching checking what time I get into work in the morning? (Because I’m not hourly and don’t expect to be treated as such.)

• Describe the work-life balance.

• Are you agile? Not agile? Scrum teams?

• What might an average day look like for me? Walk me through from when I sign in and log off for the day.

• How do you perform automated testing here? (if they don’t, I’m concerned)

• Do you enforce code formatting?

• How do you deploy your code? (if it’s not a CICD pipeline, I’m concerned)

• How involved in DevOps are developers? (Will o be expected to work on CICD code? Infrastructure as Code?)

• What version control system do you use? (Of the answer is nothing, the interview is over. I will not work there. If it’s something other than Git, I’m not excited about it.)

• Is Docker used here? (Docker makes me very productive, I’m concerned if Docker is a tool I’m not allowed to use.)

• Are there any other programming languages I’ll be using other than <advertised language for the position here>?

• Are SOLID principles common practice here? Or rejected as unnecessary? (I love SOLID and think it’s useful much more than not. If SOLID is frowned upon, I probably won’t be happy there.)

• Can I choose what sort of machine I get to work on? (If I can’t work on MacOS, it could be a deal breaker… I love MacOS for development, sue me! 🤷‍♂️)

Go programmer here: What does Go’s simplicity have to do with dependency injection? What does a language itself have to do with dependency injection?

Reading your post and not being personally familiar with your work, I do wonder, perhaps your “extremely complex projects” wouldn’t be so extremely complex if you practiced dependency injection?

How do you unit test your extremely complex projects if your business logic carries the additional responsibility of creating objects?

In my experience, 9/10 times a stored procedure is code that should just be SQL executed from your application (as in, your application sends the query text to the db, rather than that text being stored in the database and executed via calling a stored procedure).

If it’s necessary for performance, sure, go for it. Satisfy your requirements. If it’s not necessary for performance, ask yourself why it needs to be a stored procedure deployed to the database.