Read this and maybe you'll think of some useful questions to ask related to problems they may be able to directly fix.
I'd use logger that prints the file and line number when logging, to avoid the question of: "where is the log coming from"
It's an algorithm question. If somebody gave me your solution in an interview I would ask them to solve the problem without a dependency. These questions are about demonstrating your ability to code whilst understanding space & time complexity.
Can you list ones you found valuable?
Postfix wasn't in my university degree, nor do I think it should be. It's useful to know about SMTP but it's like saying you need to know the history of brick manufacturing to be a material engineer.
I hate go templating, I really really do. I don't even really know why. I just hate it.
Big hot take to me; especially in an organization with a large size and code high standard
Want to explain your rational?
Goodharts Law applies here - "Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes"
I do these stretches that Day9 talked about very regularly. I used to play some Starcraft 2 but the habit stuck.
is reflog very unfriendly UI? what would make it better?