Related Work Section

You’ll find yourself writing when you say you know we prove this that in the other section for like you’re referring to a section you have written yet so it’s kind of like the specification for a program so in this case for the contributions I do think it’s a good idea to write you’ll iterate like but it’s like otherwise it’s like writing an implementation of a program and only then going back and writing the specification right of course it’s not a waterfall model like you write one version of contributions you start to write the paper you go back to the contributions and change them there’s an iterative but stop yeah then something stuff about the initial setting up you might leave until near the end. Read more on references and researches at Edusson.

But I would have a go at the introduction first yeah anybody else yeah no I wouldn’t I don’t have any sense of how many paragraphs I want to write it depends on the paper I do try to fit the the this this sequence of the problem and my I’ll count the contributions of the paper on page one that’s all however many paragraphs that takes sometimes I have two contributions sometimes six never twelve but but page one I wouldn’t worry about the paragraphs okay what’s next in any papers they set it up related work what a disaster right here is your idea this is the payload you’re trying to get to this is the virus you’re trying to convey into Dennis’s mind and here’s Dennis right and you put in the way a huge mound a sort of sandbar of related work you’re going to force him to march through lives or death march to get to the idea right and moreover the related work at this stage your reader remember is not an expert or may not be a complete expert in this subject so and yet you’re faced with this tension of do in this related work section do you say enough to make it comprehensible in which case it becomes long or do you make it compress than a bit cryptic because your reader lacks the intellectual and terminological scaffolding necessary to understand it right.

So here’s a you know classic bit of stuff from a related work section with lots of references and special and you know we haven’t talked about where vocation protocols and transaction none of this vocabulary is going to be familiar to your readers or even if it is familiar they’ll wonder whether they mean the same thing as you mean see the problem and this is terrible tension between making it long enough to be understandable but short enough to fit in a section that’s between your reader and your idea so the solution actually very simple which is don’t put the related work section here right it just makes your readers feel tired and worse it makes them feel stupid right because you’ve compressed it to make it short enough and then they read it nothing I don’t understand this I must be a very stupid worm and this author you know he’s incredible genius I just move on like I’m never going to understand this paper that’s not the message you want to they do your readers you want to make them feel good about themselves right.