-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathworkflow.html
More file actions
355 lines (306 loc) · 15.7 KB
/
workflow.html
File metadata and controls
355 lines (306 loc) · 15.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="HandheldFriendly" content="True" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="robots" content="index, follow" />
<link href="https://fonts.googleapis.com/css2?family=Source+Code+Pro:ital,wght@0,400;0,700;1,400&family=Source+Sans+Pro:ital,wght@0,300;0,400;0,700;1,400&display=swap" rel="stylesheet">
<link rel="stylesheet" type="text/css" href="https://www.evandowning.com/theme/stylesheet/style.min.css">
<link id="dark-theme-style" rel="stylesheet" type="text/css"
disabled="disabled"
href="https://www.evandowning.com/theme/stylesheet/dark-theme.min.css">
<link id="pygments-dark-theme" rel="stylesheet" type="text/css"
disabled="disabled"
href="https://www.evandowning.com/theme/pygments/monokai.min.css">
<link id="pygments-light-theme" rel="stylesheet" type="text/css"
href="https://www.evandowning.com/theme/pygments/monokai.min.css">
<link rel="stylesheet" type="text/css" href="https://www.evandowning.com/theme/font-awesome/css/fontawesome.css">
<link rel="stylesheet" type="text/css" href="https://www.evandowning.com/theme/font-awesome/css/brands.css">
<link rel="stylesheet" type="text/css" href="https://www.evandowning.com/theme/font-awesome/css/solid.css">
<link rel="stylesheet" type="text/css" href="https://www.evandowning.com/static/custom.css">
<link rel="shortcut icon" href="https://www.evandowning.com/images/favicon.ico" type="image/x-icon">
<link rel="icon" href="https://www.evandowning.com/images/favicon.ico" type="image/x-icon">
<!-- Chrome, Firefox OS and Opera -->
<meta name="theme-color" content="#333333">
<!-- Windows Phone -->
<meta name="msapplication-navbutton-color" content="#333333">
<!-- iOS Safari -->
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<!-- Microsoft EDGE -->
<meta name="msapplication-TileColor" content="#333333">
<link href="https://www.evandowning.com/feeds/all.atom.xml" type="application/atom+xml" rel="alternate" title="Evan Downing Atom">
<meta name="author" content="Evan Downing" />
<meta name="description" content="Introduction This post discusses my workflows. I am sharing it in case it is helpful for others to read. Every Day Administrative Read unread emails and unread Slack messages. Respond to everything. Check personal goals and their progress for the year. Gutcheck Projects Review each project's motivation, goals, "secret sauce …" />
<meta name="keywords" content="">
<meta property="og:site_name" content="Evan Downing"/>
<meta property="og:title" content="Workflow"/>
<meta property="og:description" content="Introduction This post discusses my workflows. I am sharing it in case it is helpful for others to read. Every Day Administrative Read unread emails and unread Slack messages. Respond to everything. Check personal goals and their progress for the year. Gutcheck Projects Review each project's motivation, goals, "secret sauce …"/>
<meta property="og:locale" content="en_US"/>
<meta property="og:url" content="https://www.evandowning.com/workflow.html"/>
<meta property="og:type" content="article"/>
<meta property="article:published_time" content="2024-11-11 00:00:00-05:00"/>
<meta property="article:modified_time" content="2025-10-28 00:00:00-04:00"/>
<meta property="article:author" content="https://www.evandowning.com/author/evan-downing.html">
<meta property="article:section" content="misc"/>
<meta property="og:image" content="https://www.evandowning.com/images/profile.png">
<title>Evan Downing – Workflow</title>
</head>
<body class="light-theme">
<aside>
<div>
<a href="https://www.evandowning.com/">
<img src="https://www.evandowning.com/images/profile.png" alt="Evan Downing" title="Evan Downing">
</a>
<h1>
<a href="https://www.evandowning.com/">Evan Downing</a>
</h1>
<p>Cybersecurity Researcher</p>
<nav>
<ul class="list">
<li>
<a target="_self"
href="https://www.evandowning.com/pages/about.html">
About
</a>
</li>
<li>
<a target="_self"
href="https://www.evandowning.com/pages/projects.html">
Projects
</a>
</li>
<li>
<a target="_self" href="https://docs.google.com/document/d/1sKsh88ZiiveotGS-KR4l-vESgfj_U_JifvH6nGat-Wk" >Resume</a>
</li>
<li>
<a target="_self" href="https://docs.google.com/document/d/1UcXkHeRCKpBvlf4KyW92GKjyEeoiPgXGdW7ARPSa2L4" >CV</a>
</li>
</ul>
</nav>
<ul class="social">
<li>
<a class="sc-github"
href="https://github.com/evandowning"
target="_blank">
<i class="fa-brands fa-github"></i>
</a>
</li>
<li>
<a class="sc-google"
href="https://scholar.google.com/citations?user=SnJNwIAAAAAJ&hl=en"
target="_blank">
<i class="fa-brands fa-google"></i>
</a>
</li>
<li>
<a class="sc-linkedin"
href="https://www.linkedin.com/in/evandowning/"
target="_blank">
<i class="fa-brands fa-linkedin"></i>
</a>
</li>
<li>
<a class="sc-soundcloud"
href="https://soundcloud.com/evan_downing"
target="_blank">
<i class="fa-brands fa-soundcloud"></i>
</a>
</li>
</ul>
</div>
</aside>
<main>
<nav>
<a href="https://www.evandowning.com/">Home</a>
<a href="/archives.html">Archives</a>
<a href="/categories.html">Categories</a>
<a href="/tags.html">Tags</a>
<a href="https://www.evandowning.com/feeds/all.atom.xml">Atom</a>
</nav>
<article class="single">
<header>
<h1 id="workflow">Workflow</h1>
<p>
Posted on November 11, 2024 in <a href="https://www.evandowning.com/category/misc.html">misc</a>
• 5 min read
</p>
</header>
<div>
<h2>Introduction</h2>
<p>This post discusses my workflows. I am sharing it in case it is helpful for others to read.</p>
<h2>Every Day</h2>
<h3>Administrative</h3>
<ul>
<li>Read unread emails and unread Slack messages. Respond to everything.</li>
<li>Check personal goals and their progress for the year.</li>
</ul>
<h3>Gutcheck Projects</h3>
<ul>
<li>Review each project's motivation, goals, "secret sauce", current status, and timeline to finish. Do they make sense?</li>
<li><a href="https://www.darpa.mil/work-with-us/heilmeier-catechism">Heilmeier Catechism</a><ul>
<li>What are you trying to do? Articulate your objectives using absolutely no jargon.</li>
<li>How is it done today, and what are the limits of current practice?</li>
<li>What is new in your approach and why do you think it will be successful?</li>
<li>Who cares? If you are successful, what difference will it make?</li>
<li>What are the risks?</li>
<li>How much will it cost?</li>
<li>How long will it take?</li>
<li>What are the midterm and final "exams" to check for success?</li>
</ul>
</li>
<li>Writing papers<ul>
<li>What problem are you solving?</li>
<li>Why is it an important problem?</li>
<li>What are the existing approaches? Why are they not sufficient?</li>
<li>What is your approach? Why is it more effective, efficient, novel, etc?</li>
<li>How do you implement it? Why is that a good and practical way?</li>
<li>How do you evaluate your approach and system? Why is the evaluation fair and realistic? How do the results support the goals and claims of your approach and system?</li>
</ul>
</li>
</ul>
<h3><a href="http://www.evandowning.com/suggested-reads.html">Read</a> academic papers and blog posts</h3>
<ul>
<li>For papers, create a summary:<ul>
<li>Problem</li>
<li>Existing approaches and their limitations</li>
<li>Approach</li>
<li>Evaluation</li>
</ul>
</li>
</ul>
<h3>Coding</h3>
<ul>
<li>Review Pull Requests.</li>
<li>Work on code for each project.</li>
<li>Automate linting and tests via <a href="https://github.com/features/actions">Github actions</a>.</li>
</ul>
<h2>Fridays</h2>
<h3>Start of Day</h3>
<ul>
<li>Administrative</li>
<li>Gutcheck Projects</li>
</ul>
<h3>Write</h3>
<ul>
<li>Brainstorm research ideas<ul>
<li>Focus on defining the problem. If you define the problem well enough, the solution will become clear.</li>
</ul>
</li>
<li>Work on the draft of academic paper or client report<ul>
<li>This is an up-to-date version of the final draft. The weekly meetings serve as snapshots of the final draft, so you can track the evolution of the project.</li>
<li>The story for the project (motivation)</li>
<li>Outline the evaluation (how you will measure success)</li>
<li>Fill in results as you get them each day (if you were successful)</li>
<li>Working on the final draft of the paper or report helps you not leave things until the last minute</li>
<li>Save filling in the rest (introduction, related works, discussion) until the week before you submit</li>
<li>Two days before the deadline, every co-author should have read the final draft and made comments/edits</li>
</ul>
</li>
</ul>
<h2>Starting a New Project</h2>
<ul>
<li>Create a Google Drive of Documents and Slides:<ul>
<li>Related Works (Folder containing PDFs of papers referenced in <code>Background</code>)</li>
<li>Background (Doc which lists and summarizes related works and existing solutions)</li>
<li>Brainstorming (Doc containing ideas I have)</li>
<li>Meetings (Doc of meeting minutes of me presenting the idea to others)</li>
<li>Overview (Doc of Heilmeier Catechism for planning, Ongoing Summary for up-to-date status of project. See <a href="#gutcheck-projects">Gutcheck Projects</a>)</li>
<li>Slides (Presentation during meetings with status updates)</li>
</ul>
</li>
<li>Go Fast!<ul>
<li>To start, search (Google Scholar)[https://scholar.google.com/] and (Scholar Labs)[https://scholar.google.com/scholar_labs/search] for existing works in top-tier conferences. Put these in your <code>Related Works</code> folder -- just download, drag, and drop.</li>
<li>Use <a href="https://notebooklm.google/">NotebookLM</a>. Add your <code>Background</code>, <code>Brainstorming</code>, and <code>Overview</code> Docs as well as all papers in <code>Related Works/</code> Ask it research questions, brainstorm ideas, list experiments to perform (and in what order, such that each tells you the most information about what to do next), etc.</li>
</ul>
</li>
<li>Go Slow!<ul>
<li>Read through claims from LLMs about novel research directions and summaries of prior works. Fact check everything. Carefully craft your research direction and list of experiments to perform.</li>
<li>Create rapid software prototypes and measurements against the state-of-the-art. Ask NotebookLM to craft prompts to give to LLMs to quickly develop these prototypes -- double-check each implementation carefully.</li>
</ul>
</li>
</ul>
<h2>Writing Proposals</h2>
<ol>
<li>Create an overview diagram of what the system will look like. What happens first, second, third, etc. in the pipeline. What is the input? What is the output?</li>
<li>Write & submit an abstract describing the solution. What is the goal? What are the constraints? What is the approach? What are the expected results?</li>
<li>Fill in the front and back matter on the proposal. Now you know how many pages you have to work with to write the technical content.</li>
<li>Create a real-world motivating example (1-2 paragraphs) you will use throughout the proposal.<ul>
<li>This is a framing device to go back and talk about how the solution will handle each challenge in the motivating example.</li>
</ul>
</li>
<li>Split the system into components (which should already be apparent by the diagram) and assign engineers to tackle each part.</li>
<li>Make sure you include the exact metrics the BAA is asking for and say your solution will accomplish them.</li>
</ol>
<h2>Leadership</h2>
<ul>
<li>Break each project down into 2 or 3 parts, and assign each person one part to own.</li>
<li>For each project, have an end-goal in mind and an end-date. I.e., what specifically do you want to accomplish by when?</li>
<li>Everyone self-updates their progress for you to present at status updates, as well as allows you to ask and answer questions there (an internal Google Doc).</li>
<li>For each status update, create slides and meeting meetings (shared with the client). Have action items they agree to (ranked by importance) for the next meeting.</li>
<li>For each status update presentation, create ~6 slides to share with the client. That way, it is easy for them to track your progress over time.<ul>
<li>Agenda</li>
<li>Running list of Insights and Contributions</li>
<li>2-3 updates (visual/graph/numbers of results)</li>
<li>Insights for each update -- What did I learn? What is novel/interesting?</li>
<li>Next steps -- From what I learned last week, what will I do this week?</li>
</ul>
</li>
<li>If you are away on leave, assign someone to lead in your place, and notify the client who the lead contact will be until you get back. No major changes to the project should be made until you return, unless absolutely necessary.</li>
<li>Overspend on the front end of a project, so you can get far enough along that you can divert your attention if needed (e.g., a proposal needs your attention or you have meetings/trainings/other responsibilities to take care of later).</li>
<li>Every time there is a problem or something does not go according to plan, ask the Five Whys (from The Lean Startup book). Ask "why" 5 times, and you will usually identify the root cause of an issue. Fix the fifth (final) "why" first, then fix the other "whys" if they pop up again. Blame the problem, not the person. If someone makes a mistake, it is our fault it was easy for them to make that mistake.</li>
</ul>
<h2>Retrospective</h2>
<ul>
<li>After each project is finished, do a retrospective for lessons learned.<ul>
<li>What went right? Why did it go right?</li>
<li>What went wrong? Why did it go wrong? What will we do to prevent this in the future?</li>
</ul>
</li>
</ul>
</div>
<div class="tag-cloud">
<p>
</p>
</div>
</article>
<footer>
<p>
© 2026 - This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/deed.en_US" target="_blank">Creative Commons Attribution-ShareAlike 4.0 International License</a>
</p>
<p>
Built with <a href="http://getpelican.com" target="_blank">Pelican</a> using <a href="http://bit.ly/flex-pelican" target="_blank">Flex</a> theme
<span class="footer-separator">|</span>
Switch to the <a href="javascript:void(0)" onclick="theme.switch(`dark`)">dark</a> | <a href="javascript:void(0)" onclick="theme.switch(`light`)">light</a> | <a href="javascript:void(0)" onclick="theme.switch(`browser`)">browser</a> theme
<script id="dark-theme-script"
src="https://www.evandowning.com/theme/dark-theme/dark-theme.min.js"
data-enable-auto-detect-theme="False"
data-default-theme="light"
type="text/javascript">
</script>
</p><p>
<a rel="license"
href="http://creativecommons.org/licenses/by-sa/4.0/"
target="_blank">
<img alt="Creative Commons License"
title="Creative Commons License"
style="border-width:0"
src="https://i.creativecommons.org/l/by-sa/4.0/80x15.png"
width="80"
height="15"/>
</a>
</p></footer> </main>
<script type="application/ld+json">
{
"@context" : "http://schema.org",
"@type" : "Blog",
"name": " Evan Downing ",
"url" : "https://www.evandowning.com",
"image": "https://www.evandowning.com/images/profile.png",
"description": "Evan's personal website."
}
</script>
</body>
</html>