jkubrynski

From my experience, especially in big companies (but not only) most of the feedback is negative. People are not sharing positive feedback, and when they contact your manager it's usually an escalation process. That's why it's so important to reach to people who support you or simply create a content you like (blog posts, webinars, etc) and say: "thanks, I found a lot of value here".

I always care about explaining to the candidate how the interview will look like, and what are the most important elements I care about. When you skip this part, the candidate has no idea if for example during live coding, you care about the results, the code quality, IDE shortcuts fluency, etc. The feedback after the interviews proves it is a game-changer.

It's also good to check the https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect - a cognitive bias in which people with low ability at a task overestimate their ability. Very useful during job interviews

There is also an interesting presentation about how Azul implemented their JIT called Falcon, that is fully based on LLVM. https://www.youtube.com/watch?v=Uqch1rjPls8 Generally LLVM is a nice idea that allows vendors to reuse major components.

My company uses mostly Java and TypeScript. However, it’s a good starting point to proof the technology on JVM languages and see how it’s adopted by the team, how many false-positives is generates, etc. With all automated tools the biggest issues usually are false-positives.

1800 commits since the last release - that's not the "continuous delivery" ;)