Ramons talk

This commit is contained in:
Johan Thelin 2019-04-07 16:57:33 +02:00
parent 7e99e31af4
commit 88de560812
3 changed files with 4 additions and 4 deletions

View file

@ -272,7 +272,7 @@
<a href="speakers-and-talks.html#rsotomathiesen" class="speakerfront">
<img class="speakergrid" src="images/speaker-rsotomathiesen.png" alt="Ramón Soto Mathiesen"><br />
<b>Ramón Soto Mathiesen</b><br />
T.B.D.
Limiting side-effects of applications at compile-time
</a>
</div><div class="col-md-4">
<a href="speakers-and-talks.html#dstenberg" class="speakerfront">

View file

@ -281,7 +281,7 @@ All sessions include time for Q&amp;A and to move between rooms.</p>
<a href="speakers-and-talks.html#rsotomathiesen">
<div class="talktitle">T.B.D.</div>
<div class="talktitle">Limiting side-effects of applications at compile-time</div>
<div class="talkspeaker">Ramón Soto Mathiesen</div>
</a>

View file

@ -548,9 +548,9 @@
</div>
<div class="col-md-9">
<div class="name">Ramón Soto Mathiesen</div>
<div class="title">T.B.D.</div>
<div class="title">Limiting side-effects of applications at compile-time</div>
<div class="links"><a href="schedule.html#mon17">Talk Slot</a></div><div class="abstract">
T.B.D.
By using tools where you have a clear separation between code branches that makes effects and the ones that doesn't, as for example Haskell, it's very easy to argue that this can be done in a fairly easy manner. But it's not always the case that if a specific code branch is allowed to have side-effects, these should be all possible side-effects. In this short talk, we will be showcasing how you will be able to further restrict effects, granularly and even recursively, in order to limit these side-effects. An example could be an application that only needs to access data from a specific website, limited to a relative URL, and then print it to the console. These effects restrictions will be designed into the application, which will allow you to outsource development to anyone with the right skill-set, even if they have bad intentions, knowing that they will live up to 100% the design or the application will not build.
</div><div class="bio">
Ramón Soto Mathiesen, is a passionate computer scientist, with talent for business, who advocates for: correctness, code quality and high standards, but always with the customer in focus.
</div><div class="bio">