153 karma · joined August 11, 2015
Socials: - linkedin.com/in/juliennigri - nigri.dev
Kudos to the author for being honest about all this. I think it's a real issue and that we should find more solutions to prevent this than candidates signing an NDA. Imho when doing such interview, questions should not rely on a "trick" and even if they do, candidates should be evaluated on everything else: how they explain the code, how they react to feedbacks, how easily they transcribe what they explain to code. It's not perfect but it helps.
Isn't this a bit misleading? Intel is still adding SGXv2 on the Xeon processors. Isn't it most likely that there were just no real use cases for PCs and they just decided to focus on servers?
foo +bar +baz
was equivalent to
foo "bar" "baz"
> I’ve never really subscribed to any of the test-driven-development manifestos or practices that I’ve encountered.
I feel the exact opposite. I've worked in project with a lot of legacy code, both with BDD or with UTs that we added latter on.
Even with the best intentions the latter always failed: we always ended up doing a lot of unreadable tests that had no meaning and that we were afraid to look at. However, when I was working in a team fully committed on BDD, we were looking at the tests before looking at the code, the tests were in the center of the developing process, and we were able to write fast, solid, and simple tests.
Nowadays, I'm more interested on articles that understand that tests can be a pain too. And tbh I don't really trust articles that aim at a high coverage without talking about the different challenges that comes with tests.
Plus, you end up doing stupid stuff like:
DoThat(); // It does that
Sadly, it's often a good strategy to just breaking the law or an agreement, even with the risk of being caught.