diff options
Diffstat (limited to 'bsc/1.txt')
| -rw-r--r-- | bsc/1.txt | 67 |
1 files changed, 0 insertions, 67 deletions
diff --git a/bsc/1.txt b/bsc/1.txt deleted file mode 100644 index 27dcd80..0000000 --- a/bsc/1.txt +++ /dev/null @@ -1,67 +0,0 @@ -==13-05-2026== -Introduction: -Make a compelling story about what the adventure is upon you and what problem you set out to solve. -You can think of it as a classical novel. -Make a protagonist; there is a protagonist, he encounters and issue and overcomes it. -Except it's just more technical. - -Status update template: -Since last meeting, I changed ___ in the thesis text. -I changed ___ in the artifact / experiments. -My next concrete deliverable is ___. -My main blocker is ___. - -Try to find good references in the CompSys manifesto. -This should contain ``good'' references. -Paralysis analysis. -You should write your thesis at the same time as your coding. -DO NOT leave out the thesis as the last part, after all coding is done. -Do both in parallel. - -The `gap` in the presentation slides is `...and this has not yet been done before.` or `we are the first to do...` etc. -`Gap` => nobody did this before (or a knowledge gap). -E.g., a system does not exist. The key is that it is missing worldwide from the scientific community. -Nobody has done yet => part of a `scientific` project. -Why is my project scientific? Because nobody did it yet. - -How to backup that something does not exist? -You cannot cite work that does not exist. -You cannot cite non existing thing, because it's not there. -Typically, you show instead how existing falls short. -1/ State the problem, why it's important. -2/ Refer to recent and impactful work on datacenter simulation or digital twinning. -2a/ Write in a few sentences that this other work did `xyz` and say why `xyz` is NOT ENOUGH to advance the problem you introduce earlier. -You can just say that `this is missing from their work, or I think that this is missing`. -Now YOU need to make a claim, `this is true`, or `nobody did this`. -Making such a claim is bold and YOU could be wrong, but STILL make that claim, but then cite the related work, make the claim `they don't do x`, and then go to your supervisor and tell him `in my mind this is the key issue with my thesis, do you agree with this? Is there any work I Should have cited? Am I misinterpreting anything those other projects did?`Bring this up with a conversation with your supervisor. - -Answer to each research questions is one of your main contributions. -They are the main way the reader can understand what you have done. -System design => contribution to question on ``How to design a ...?'' -Each contribution => a section in your thesis. Core content of the thesis. 3-4 sections. -Each section corresponds directly to a research question. - -Make a skeleton of the thesis first. Very important! -This way you can plan your own work much better => do this. -Map the thesis before writing text. -Put the skeleton in the shared folder. - -Each RQ should be enumerated, you want every question to be not just a nice isolated question,but add a bit of context below: 1) describe why it's important 2) say why it's challenging 3) say what makes it scientific. - -You can take whatever structure you want from any report, no plagiarism nor declarations needed. - -==20-05-2026== -You should explain in your background section background on datacenters and datacenter simulations. -The background is NOT an extensive discussion of extensive and related work. It is NOT that. -It gives the necessary context for the rest of the thesis. - -You can include a figure in the introduction from a different paper. -You can adapt it from a different paper. -Do not copy figures directly. - -Background: -a) Concept A -b) Concept B -c) Merge A + B, why we need both - - |