No it's typical. It's just that your stipend is usually just x amount of Dollars + whatever tuition is so you never have to care what it is and you don't pay it directly per se, it's just included in your stipend. Someone pays for it at the end of the day though.

Depending on the model I could easily see it approaching 7 figures since Mythos security scans have been 6 figures already and don't require nearly as much output.

Given it's like 30 years of my salary I'd probably be willing to be miserable for a number of years.

If you ever actually see the work or something charities on the ground and the people they help you might change your mind very quickly. They certainly do more good than another million in some index fund.

In the menu there is the pricing page? URL is /pricing

Huh, I'd swear earlier today that page didn't have any actual prices on it, but it clearly does now, thanks.

You are allowed to turn up in your own though, no one will check. I even had people turn up in the wrong colour gown at my graduation.

Forgive me if I've mis-understood this thread, but there are unsafe declerations in that crate. Is there really any difference between using unsafe in your own code, versus wrapping it inside some crate?

I guess you are making the point that the user does not have to concern themselves with the unsafe declarations?

> Is there really any difference between using unsafe in your own code, versus wrapping it inside some crate?

Yes, in the same way that there's a difference between using `std::Vec` (which uses `unsafe`), and writing an unsafe Vec class yourself.

Or even the difference between using Python (which wraps an unsafe CPython implementation), and doing everything in unsafe Python code.

The difference is that widely used code like CPython and `std::Vec` are much much better tested and audited than anything I would write myself, because so many people use them. This is a continuum so something like petgraph is going to be not as well tested as std::Vec but still way better tested than anything I've written.

I would say yes, there’s a difference, in general. I would much rather leave the unsafe code to crates used and tested by many other applications, than have them in the application code itself.

I agree that it's a flawed comparison but it does touch on a very real issue in the workplace. The difference between employees who I can send away on a problem and they'll encounter issues and try to solve them, vs those who come back to the senior at any problem, presents a serious ceiling on the level those employees can work at.

As a leader, I can just tell people literally that: if you can't go away and work independently on a problem, it puts a ceiling on how well you're going to do. Then I ask people what they've tried before asking me.

Just being upfront with people can break low performance patterns of behavior.

Perhaps the example should be a homework assignment, not an exam.

Even then I would call it bad teaching, as the usual mode is:

New stuff gets explained in class by the teacher - the details are for self study. This is how it was communicated to me in school, so I would call it part of the "contract".

But giving a homework on a fundamental new subject without explicitely telling that this is what it is about, will rightfully confuse, as the normal mode is different.

And when it happened to me, it always happened because the teacher messed up and got confused themself what they had and have not teached before.

Teaching to self study is a valuable skill in itself that should not be taught by accident, but with a clear pedagogic concept.

Yes I think people forget that cyber-war between West and East is very active, with a significant amount of attacks being committed by nation states or state-sponsored groups.

Moodle?