First, I've got proof no. 3. I can offer a nice 4 argument proof, but you wouldn't let me provide it.
Second, I tried proof no. 2, where I'm offered words like given and algebra I have no use for.
To make a system like this right it needs to be deductive and have a large library of concepts. Getting this right is complex enough to be a PhD project. Properly scoped could be done for MSc.
Turning vaguely defined task into something tangible is usually the most difficult, and most important part of the task, but it requires some experience.
In the beginning you need to learn the internal know-how, and this requires regular prompt answers. Otherwise, you will stay blocked and frustrated most of the time.
Remote work is fine when you already know the domain, but that's not really what intern programs are for.
That said, you can try to write design docs where you put your questions. Note that it's not really about writing a specification, but about writing down what you know and what you don't. You can speculate about answers to your questions, and this way make your manager understand what you're missing.
It so happens that a large part of my PhD was on this very subject. The result I've got N log(N), this is more visible when you get to larger RAM (I had 0,5 TB RAM at the time).
We have an empirical result, a justification and a rigorous predictive model.
The reason has to do with hashing, but a different type: TLB.
It so happens that a large part of my PhD was on this very subject. The result I've got N log(N), this is more visible when you get to larger RAM (I had 0,5 TB RAM at the time).
We have an empirical result, a justification and a rigorous predictive model.
The reason has to do with hashing, but a different type: TLB.