Resume, OCWW
This commit is contained in:
Madison Scott-Clary
88
content/resume.md
Normal file
88
content/resume.md
Normal file
@ -0,0 +1,88 @@
|
||||
# Madison Scott-Clary (she/her)
|
||||
|
||||
*Sultan, WA — <madison@makyo.io> — 303-818-5943*
|
||||
|
||||
-----
|
||||
|
||||
I am an author, technical writer, and software developer living up in the Cascades Northeast of Seattle. I've been keenly focused on open-source and freely available software since I first began programming two decades ago, and in free access to information for nearly as long, focused on liberal licences such as MIT and CreativeCommons. With twenty years programming experience and ten years writing and community education and organization experience, I hope to bring all that I can to my new role.
|
||||
|
||||
## Experience
|
||||
|
||||
### Employment
|
||||
|
||||
DigitalOcean — Technical Writer (IC3) — Jan 2022–*present*
|
||||
:
|
||||
* Created new educational content in the form of tutorials and conceptual articles for DO's community site on topics ranging from software development to product deployment and maintenance.
|
||||
* Maintained existing articles, ensuring that they were technically correct, up to editorial standards, and, where necessary, updated to the current version of software.
|
||||
* Helped with the editorial team on the Write4DO campaign, soliciting and selecting technical article pitches from the community through a democratic process
|
||||
|
||||
Nvidia — Senior Software Engineer, GeForce NOW — July 2020–Dec 2021
|
||||
:
|
||||
* Expanded and maintained the GeForce NOW publisher dashboard, aggregating playtime data to aid in stakeholder marketing decisions.
|
||||
* Created and scheduled Spark big-data map-reduce jobs to build aggregate data sets from raw metrics.
|
||||
* Participated in on-call rotation for a suite of microservices that, taken together, made up the publisher and product toolset.
|
||||
|
||||
Internet Archive — Senior Software Engineer, ArchiveIt — Sept 2018–Oct 2019
|
||||
:
|
||||
* Shifted the ArchiveIt infrastructure from the old Java Wayback Machine to the newer Python version.
|
||||
* Implemented fast key-value stores for capture-index (CDX) records using OutbackDB, a purpose-built layer atop RocksDB, moving from a 2-layer flat-file plus sharded sqlite3 system.
|
||||
|
||||
Canonical — Software Engineer, Juju — Sept 2012–Sept 2018
|
||||
:
|
||||
* Helped build the Juju GUI, a responsive web application, from the ground up, implementing much of the data visualization software using d3, YUI, and React.
|
||||
* Implemented SVG icon, service, and bundle displays in Juju Core using Go.
|
||||
* Supported the Extended Release Repository, an `apt` repository for customers who had paid for extended support on older versions of Ubuntu.
|
||||
* Helped run a data visualization workshop for interns visiting from Cisco.
|
||||
* Provided community support on the Canonical/Ubuntu IRC, Slack, and Discord servers, continuing beyond formal employment.
|
||||
|
||||
### Extracurricular
|
||||
|
||||
Software and Data
|
||||
:
|
||||
* Ran a large-scale community census and survey to collect data from members of a fandom in order to explore what made it tick. Created accessible and interactive data visualizations based on survey and art repository data.
|
||||
* Wrote regular posts on both demographic data and social topics for the blog \[adjective\]\[species\].
|
||||
* Wrote, maintain, and support the site <https://polycul.es> for mapping complex relationship structure using force-directed graphs.
|
||||
|
||||
Writing, Editing, and Production
|
||||
:
|
||||
* Wrote and published nine books (four novels, three short story collections, a poetry collection, and a memoir).
|
||||
* Ran educational panels on writing, covering the topics of writing and mental health, book layout and design, and braided plot structure. In addition, planned and hosted short writers workshops focused on writing critique and critical reading.
|
||||
* Solicited, edited, produced, and published/helped publish three short fiction anthologies: *Arcana — A Tarot Anthology*, *When The World Was Young — A Prehistoric Anthology*, and the upcoming *Clade*.
|
||||
* Provided typesetting, layout, design, and production services for both print and ebook to individuals and small publishing houses.
|
||||
|
||||
## Examples
|
||||
|
||||
Technical Tutorials
|
||||
:
|
||||
* [How to Install Gitea on Ubuntu Using Docker](https://www.digitalocean.com/community/tutorials/how-to-install-gitea-on-ubuntu-using-docker)
|
||||
* [How to Store Gitea Repositories on a Separate Volume](https://www.digitalocean.com/community/tutorials/how-to-store-gitea-repositories-on-a-separate-volume)
|
||||
* Additional tutorials in-flight available on request: How to Use Templates in Go, How to Use CI/CD With Gitea and Drone, How to Create a REST API with Flask-RESTX
|
||||
|
||||
Blog Posts and Articles
|
||||
:
|
||||
* [Accessing the Juju CLI from within the Juju GUI](https://ubuntu.com/blog/accessing-the-juju-cli-from-within-the-gui)
|
||||
* [Coming Out in Tech](https://thenewstack.io/coming-out-in-tech/)
|
||||
* [Gender: Furry](https://makyo.ink/gender-furry/)
|
||||
* [Tracking an anthology: the steps from start to finish](https://makyo.ink/anthology)
|
||||
* [Book layout and design: reducing barriers between story and reader](https://makyo.ink/layout-and-design/)
|
||||
* Linux Shell Tips and Tricks (in-flight, available on request)
|
||||
* Data science and sociology articles from the now-defunct \[adjective\]\[species\] (available on request)
|
||||
|
||||
Presentations, Workshops, and Talks
|
||||
:
|
||||
* Oxfurred Comma Writing Workshop [Session One](https://www.youtube.com/watch?v=-05SW1qeNEk) and [Session Two](https://www.youtube.com/watch?v=-05SW1qeNEk)
|
||||
* [Braided Plot Threads](https://www.youtube.com/watch?v=r1SEKD2IAhQ)
|
||||
* [Writing and Mental Health](https://www.youtube.com/watch?v=i9btAkkoGzA)
|
||||
* Book Layout and Design [2020](https://www.youtube.com/watch?v=Bzmx_tCkI1E) and [2021](https://archive.org/details/layout-and-design-fc2021) — [Slides](https://writing.drab-makyo.com/layout-and-design/)
|
||||
|
||||
Software
|
||||
:
|
||||
* [Stimmtausch](https://github.com/makyo/stimmtausch) — a terminal MUCK/MUD/MUSH/MOO client written in Go (and [usable in Vim](https://github.com/makyo/stimmtausch.vim)!).
|
||||
* [polycul.es](https://github.com/makyo/polycul.es) — a web application for mapping complex relationships written in Python and Javascript.
|
||||
* [snuffler](https://snuffler.projects.makyo.io/) — cascading configuration for Go programs.
|
||||
* [ansigo](https://ansigo.projects.makyo.io/) — ANSI color and formatting support for Go CLI programs.
|
||||
|
||||
## Eductaion
|
||||
|
||||
* **Colorado State University** — Bachelor's in Music Composition
|
||||
* **Cornell College** — MFA in creative writing and writing pedagogy *(current student)*
|
||||
@ -134,8 +134,12 @@ Unfortunately, due to the fact that time zones started clashing with schedules (
|
||||
|
||||
## Sessions
|
||||
|
||||
During the time leading up to the convention, the Friday panel was canceled due to a misunderstanding about schedules. With one participant joining from Australia and the convention not actually beginning until Saturday, the participants weren't able to meet. However, the two sessions on Saturday and Sunday went off as planned.
|
||||
|
||||
### Video in Lieu of Friday Session
|
||||
|
||||
Due to the canceled Friday session, I recorded a short video with the introduction to critique that I had planned. The participants found this quite useful, though a few got stressed due to missed expectations as to what critique actually was.
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/v_HKqGY1fiM" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
|
||||
#### Writing assignment
|
||||
@ -188,20 +192,30 @@ Unfortunately, due to the fact that time zones started clashing with schedules (
|
||||
|
||||
### Other Sessions
|
||||
|
||||
During the convention, I ran two additional panels (a third was offered in case there were not enough panels from others, but there was a sudden surge of submissions a few days before the con began).
|
||||
|
||||
#### Writing and Mental Health
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/i9btAkkoGzA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
|
||||
[Panel notes](https://writing.drab-makyo.com/writing-and-mental-health/)
|
||||
|
||||
#### Plot Threads
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/r1SEKD2IAhQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
|
||||
[Panel document](https://makyo.wiki/assets/romance-caduceus.pdf)
|
||||
|
||||
## Feedback
|
||||
|
||||
### Feedback During
|
||||
|
||||
I ran into an issue with expectations around critique. A few of the members were confused as to what that meant and just how much work needed to be done. For instance, Kayodé wound up running through the stories several times as he learned more about what was expected of him, starting first with line editing, then with points that he wanted the authors to focus on that he felt were too specific and would have taken up too much time. As I posted the video for session 0, that wound up giving a much better idea of what the critique sessions would look like. This is probably something that I'll keep in mind moving forward, and may hunt down some good resources to provide participants with for future workshops.
|
||||
|
||||
### Feedback Survey
|
||||
|
||||
After the workshop, I provided the participants with a short survey to see if they had any particular feedback, positive or negative, about the whole experience as well as particular days.
|
||||
|
||||
#### How do you feel the workshop went overall?
|
||||
|
||||
* I thought it went well. Coyote Woman was a good story to analyze. The mix of people, yourself included, was excellent. We all had different things to share and came from different directions. Sometimes a group has too many people that see things the same way. That did not happen here. The shorter, compressed format worked pretty well for me as an introduction to workshops. I wouldn't have had the time or energy for something more. Now that I know what to expect, I feel that I could tackle a longer, more involved workshop in the future. It's had a very positive affect on how I think of myself as a writer and author. As I've said elsewhere, I feel like this was my introduction to writing as a craft, rather than just a hobby. Seeing how other people analyzed things and seeing my own analysis compared to theirs was incredibly validating. I've had people say I'm good at writing and while I kind of believed it, it was hard to know what parts of my writing style worked. I was surprised that my dialog was highlighted. It's never something I considered. I'd focused on knowing my characters and knowing their voices. Accents and dictation were very deliberate, informed by their backstories. But I never explicitly thought about the dialog as a tool for conveying information the way I do with description. Knowing this, I now have some direction on where to grow.
|
||||
@ -227,3 +241,5 @@ Unfortunately, due to the fact that time zones started clashing with schedules (
|
||||
* I know you mentioned there was originally 3 sections, so having the third section going over the writing excercise after it was edited from the first day's feedback would have been cool to see how people use that changes and get info on how best to do that.
|
||||
|
||||
## Takeaways
|
||||
|
||||
This was an incredibly fun project from start to finish, and I had a really fun time working with some great (and very respectful!) authors. With their insights, I think they were all able to take something away for each of their stories that they could use moving forward. There are some things that I would change, such as adding some clarity before the workshop starts and also spending a bit more time on introducing the concepts of critique during the first session. While this had been on the schedule for the first session that wound up getting canceled, the participants did mention meeting over video chat beforehand, and we never wound up doing so. I'll be hosting an in-person workshop in January using a similar structure, and I'll be using a lot of the lessons that I learned from this in order to make that one all the better.
|
||||
|
||||
Reference in New Issue
Block a user