[sushshshsh]

I've been deep in the interview cycle lately and I just had a dream last night that I was asked, in a non-technical interview with a product manager, "what are the 5 ways to dockerize an application?"

I then said that I could only think of one way, and he responded "how do you not know docker if you are applying for a java developer job?"

Thankfully I woke up

[merb]

well most of the time, my company deals with docker aswell. but my coworkers have nothing to do with it, it just is fully automated. the only problem we had, when introducing long running jobs that can be run while clicking a button inside our ui, which runs a k8s job. that was hairy for my coworker, but with enough shell scripts it started to be easier and easier.

[sushshshsh]

That's cool :) I mean, it's fine to not know the answer to everything. Usually it's not a deal breaker, especially if you provide a general answer of "here's how i tHink it works"

But what's always hilarious to me is 3 seconds after they ask the docker question, they'll then ask "ok so tell me a bit more about how CompleteableFutures, Consumers, and Threadpools work together and why you would want to use them"

or my personal favorite, the predictable trifecta of

"whats the difference between an abstract class and an interface"

"ok tell me how garbage collection works"

"ok and whats the difference between final, finalize, and finally?"

[merb]

well docker should not be your problem the latter are things an java developer should've heard about. well tbf CompletableFutures is relativly new in java, not in other languages of course (i.e. scala, c#, etc...)