• 0 Posts
  • 154 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle






  • The Rust kernel devs are …

    1. …asking the maintainers to lock down APIs which the C devs purposefully leave malleable, in part, to avoid binary blob drivers being feasible.
    2. …asking maintainers to accept code into their subsystem whilst being told, you don’t need to know Rust to an expert level…trust us. Cross language interfaces always have nuance and make good attack vectors. Understandable that maintainers are cautious.
    3. …creating quite a lot of hassle for no a lot of improvement. Systems are only as resilient as their weakest components. The cross language interface is always going to be weak. Introducing a weakness to get improvements probably only succeeds at making the whole weaker.











  • Getting interview practise is no bad thing. Being interviewed is a skill you learn to be sure.

    I think a lot of people miss that interviews in the technical world are often not smartly dressed exams. Some are, but those are probably jobs where they won’t mentor you and invest in you. They expect you to come fully developed.

    Good interviewers are trying to imagine you as an every-day team member. Will you…

    • …work well with others?
    • …be engaged with the problem space?
    • …ask for clarifications or just make assumptions to avoid appearing “dumb”?
    • …let a lack of knowledge on something become a road block?

    Knowledge is easy to give you. These things are much harder to teach.

    Also, knowledge based questions might be designed to find your limit. So if you don’t know something, that doesn’t mean it’s pointless from that point on. The interviewer may just have pushed you to your limit, and only they know if that was good enough. Keep going, stay engaged.

    I don’t know if any of that helps you design your bot, but maybe it gives you some ideas about being an interviewer.