

You better be ready to pick up some drum sticks while I hop on the bass guitar, otherwise we can watch music videos on yt.
You better be ready to pick up some drum sticks while I hop on the bass guitar, otherwise we can watch music videos on yt.
Just out of curiosity, did the take-home assignment direct candidates to include tests, or was there an implicit expectation of them using TDD? I’d probably be one of those to sound a little dismissive of TDD, though I do support testing for nontrivial functionality. I always wondered if anyone really used that workflow or if it was too idealistic for the real world.
I made some automation in python for common git tasks and use the cli otherwise. I tried a couple like sourcetree and the built in automation for VS but they’re either slow or lack features i’d like.
Yeah, that too! When you have some non technical manager breathing down your neck, you might have a hard time not fumbling around even if you normally could resolve the issue in no time.
I can see how this could be unfair, but working as a dev sometimes does require you to be on top of things in a high stress atmosphere. For example, what if you’re proposing an excellent technical solution in a meeting but some jaded older engineer is hard to convince? If you can’t outline your thinking in that scenario, your solution could be discarded just because someone was louder than you. As someone who used to have performance anxiety, I believe it’s generally something you can and should practice for. On the other hand, if there really isn’t a need for this type of skill, it totally makes sense to avoid creating interview environments where you are filtering candidates based on it.
But it’s better when it’s deep cold. People just need to get sturdier utensils.