Some questions about the "questions" about back-end-developer-interview-questions

[monklof]

(continue)

• As a software engineer you want both to innovate and to be predictable. How those 2 goals can coexist in the same strategy?

what do you mean by "be predictable"?

[arialdomartini]

What does your computer do when you wait?
what do you mean by "wait"?

The question is about what an Operating System does when it idles. It can involve discussions about interrupts, daemons, background services, polling, event handling and so on.

Could you implement Objects in terms of Higher Order Functions, and vice-versa?
Forgive me... I really don't know what this mean?

Don't remember what I meant. I'll suspend this one.

What is the tests influence on design?
Also, I don't know what's 'tests' here, unit test? or experiments before design?

Yes, I refer to Test Driven Development and emergent design. I should mention TDD more explicitly. I'll send a pull request for this.

Write a loop, then transform it into a recursive function, avoiding mutability. Discuss.
what does "mutability" mean here?

Probably I should write "using only immutable objects".

How would you introduce Continue Delivery in a multi million waterfall shop?
What does "a multi million waterfall shop" mean?

I mean a huge company, in a very profitable business. A company for which the change from Waterfall to Continuous Integration would be not trivial, because of all the interactions. Would you help me to describe it with more proper words.

I'm the CEO of your Company. Explain me Kanban and convince me to invest on it.
I don't know very well about this, do you mean this?

Yes, exactly. I mean this Kanban

"Individuals and interactions over processes and tools" and "Customer collaboration over contract negotiation" comprise half of the values of the Agile Manifesto. Discuss
discuss about what?

This is a principle listed in the Agile Manifesto and I think it can be a starting point for interesting discussions. With this question I would like to invite candidates to discuss their opinion about the deep meaning behind this principle. Could you suggest me another way to start a discussion around this principle?

How would you design a "defragger" utility?
what is "defragger" ?

I should have writen "File system fragmentation" instead. Thank you.

How to deal with failover and user sessions?
what does "user sessions" mean here? do you mean "user session in distributed system"? if so, why put "user sessions" and "failover" in one question?

With this question I would like to talk about Session Affinity, Session Stickiness and session management after a server crash, for example like in Bind_session_after_crash_to_failover_node.
I'd love if you can suggest a clearer form.

In which part of the lifecycle performance should be taken in consideration, and how?

"lifecycle performance" or "performance lifecycle"?

"taken in consideration", taken into consideration for what kind of problem?
“and how”, how for what?

I try to reformulate: "In which part of the lifecycle of a program (during the design phase? after the deployment?) developers should care about performance? What should they do and when?"

Again, I'd love to hear a suggestion on how to make it clearer.

thanks.

Thank you! You are helping me a lot. I'm opening an issue for each of your questions.

[arialdomartini]

Ciao @monklof

I moved all the single questions above to specific issues (see #10, #11, #12, #13, #14, #15, #16, #17, #18, #19, #20), so it will be more convenient to track them and apply the fixes we will agree on to both this and your repository.

I think this issue can be closed now.
Thank you!