Skip to content

Commit 1d6f880

Browse files
committed
[ tyde-24 ] Add blog post (and PDF!) about paper
Type-level Property Based Testing
1 parent 6581946 commit 1d6f880

File tree

2 files changed

+98
-0
lines changed

2 files changed

+98
-0
lines changed
Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
---
2+
# Documentation: https://docs.hugoblox.com/managing-content/
3+
4+
title: "I submitted a Tyde '24 Paper"
5+
subtitle: "Type-level Property Based Testing"
6+
summary: ""
7+
authors: [thomas-e-hansen]
8+
tags: [academia, phd, publications]
9+
categories: [sprout]
10+
date: 2024-05-28
11+
lastmod:
12+
featured: false
13+
draft: false
14+
15+
# Featured image
16+
# To use, add an image named `featured.jpg/png` to your page's folder.
17+
# Focal points: Smart, Center, TopLeft, Top, TopRight, Left, Right, BottomLeft, Bottom, BottomRight.
18+
image:
19+
caption: ""
20+
focal_point: ""
21+
preview_only: false
22+
23+
# Projects (optional).
24+
# Associate this post with one or more of your projects.
25+
# Simply enter your project's folder or file name without extension.
26+
# E.g. `projects = ["internal-project"]` references `content/project/deep-learning/index.md`.
27+
# Otherwise, set `projects = []`.
28+
projects: []
29+
---
30+
31+
Well, there we go. Just shy of four years after I started my PhD, I've finally
32+
submitted a research paper to a workshop. In this case: "The Workshop on
33+
Type-Driven Development" -- abbreviated TyDe -- 2024. Papers aren't a
34+
requirement for passing your PhD here (and I know several successful people
35+
who never did as part of their PhD), but it still feels good to at least have
36+
submitted something (I'm _so_ not counting my chickens yet!). The title of it is
37+
"Type-level Property Based Testing".
38+
39+
It's always interesting to go through the motions yourself, having heard from
40+
others what it is like. I was convinced I could have it all ready one month
41+
before the submission deadline. In reality, it ended up being closer to 5 days
42+
before (which apparently is really good, I'm told the day before is horrifyingly
43+
normal). I would love to write more about it, if my brain doesn't immediately
44+
repress it due to the past week of stress, but I'm currently slightly tired of
45+
writing... ^^;;
46+
47+
Also, past me turned out to be a turned out to be a huge help! I keep a series
48+
of PhD notebooks of technical considerations, paper summaries, miscellaneous
49+
ramblings, etc. As part of that, about a year ago, I took care to keep a log of
50+
all the tricks and challenges involved with implementing what I ended up writing
51+
about. All the challenges and considerations were there (albeit in note form)
52+
and I "just" needed to transfer them into formal writing. Thanks past me!!
53+
54+
Of course, my supervisor was also a great help. The initial version was 1½ pages
55+
over the 12 page limit; 3 columns too many. But like many things, experience is
56+
helpful, and so Edwin managed to regain those columns by "simply" rewording
57+
things (and cutting some excessive details I didn't know were excessive). This
58+
was a massive help, and I would not have been able to submit without it.
59+
60+
After a tiny amount of confusion, I have now received confirmation that the
61+
paper is not meant to be anonymous or double-blind or anything like that, hence
62+
this blog post, where you'll also find the paper itself (the PDF should be
63+
linked at the top of this page). We're not entirely happy with the title, but it
64+
was the best we could come up with (and naming is infamously one of the 2
65+
hardest Computer Science problems, so I'm glad we have a title at all ^^). I
66+
will update the paper once the review process has happened. Oh also, although
67+
it's slightly distracting, I think I have to put this somewhere: **the PDF is a
68+
personal copy for personal use only, not redistribution**, it is pre-everything,
69+
including peer review.
70+
71+
Regardless of whether you read or understand any of it, I hope you at least
72+
enjoyed this tiny random blurb : )
73+
74+
I would like to do a more comprehensive discussion/walkthrough/tutorial about
75+
how and what I did in the paper, but apparently that's called a "Thesis Chapter"
76+
and "something I really should be working on right now". (Oh yeah, this is also
77+
why
78+
[the graph](../writing-up-a-phd)
79+
has been flat for the past while. I'm really looking forward to the jump once I
80+
add this in!).
81+
82+
Anyway, I'm off to
83+
[EMF](https://emfcamp.org)
84+
tomorrow -- the timing worked out _so well_ -- which I'm looking forward to
85+
tremendously (5 years I've wanted to go to that! _\*shakes fist at COVID\*_).
86+
It'll also be the only tiny amount of summer holiday I get this year, but such
87+
is writing up it seems. Thanks again for reading, bye for now : )
88+
89+
-----
90+
91+
## Acknowledgements
92+
93+
* [Edwin Brady](https://www.type-driven.org.uk/edwinb/), without whom none of
94+
this would have been possible.
95+
* Micah J. Smith, whose
96+
[blog post](https://www.micahsmith.com/blog/2021/02/sharing-a-preprint-using-acmart/)
97+
on various `acmart` settings got the document into its postable format.
98+
Binary file not shown.

0 commit comments

Comments
 (0)