{SITE_DESCRIPTION}
## Writings @@ -15,18 +15,16 @@ import { SITE_DESCRIPTION, YEARS_OF_EXPERIENCE } from '@src/consts.ts'; ## About -I have over {YEARS_OF_EXPERIENCE} years of [experience](/resume) in: +I have over [{YEARS_OF_EXPERIENCE} years of experience](/resume) in: -- web software -- accessibility -- [reactive programming](/reactive-programming) +- [web apps](/web-apps) - [design systems](/design-systems) - [mentoring](/mentoring) - [public speaking](/talks) Outside of work, I play [board games](/board-games), listen to [audiobooks](/books) and [podcasts](/podcasts), and run trails in sandals. -Learn more [about this website](/colophon). +Learn more about my [purpose statement](/purpose) and [this website](/colophon). ## Contact diff --git a/src/pages/mentoring.mdx b/src/pages/mentoring.mdx index 9bc31d6..2d3b74b 100644 --- a/src/pages/mentoring.mdx +++ b/src/pages/mentoring.mdx @@ -3,10 +3,20 @@ layout: "@layouts/Layout.astro" title: "Mentoring" --- -Since working at Indiana University in 2012, I have mentored interns and graduate assistants in user experience design, and I have taught backend developers to program in front-end development. Each of these types of relationships are treated differently. +I have mentored developers, interns, graduate assistants, designers, and developers. Each relationship is approached differently. -For programmers, teaching is handled mostly through paired programming. We solve problems as they emerge from team projects. Staff developers already have a technical foundation, so they need to learn how to translate syntax to another language and how to work with different toolsets. +## Interns + +Interns need ongoing support, as they may not have much prior experience in the field. At the start of the internship, you should establish some goals. Impact maps are useful for framing goals, documenting accomplishments, and prioritizing work. Collaborate with the intern about establishing a pace for their learning and practice. + +## Graduate assistants Graduate assistants tend to have an academic foundation in their field. Work projects put into practice what they've learned in the classroom. Critique and exposure to other full-time staff in their field help them refine their craft. -Interns need more ongoing support, as they may not have much prior experience in the field. Establish goals for both the intern and the organization at the beginning of an internship. [Impact maps](https://github.com/basham/swit-workshop-impact) can define successful outcomes, who can contribute toward those outcomes (the intern, the mentor, other staff, stakeholders), and what those people can do to lead to those outcomes. As the internship progresses, the impact map can be updated to reflect what has been done and what still needs to be done. This approach allows the internship to be a guided, evolving, and well-documented collaboration. It results in skills that can be learned and put into practice, at a pace that is agreeable to everyone involved. +## Designers + +Weekly meetings with a group of designers can provide diverse feedback for members. One-on-one meetings with another designer can produce a safe space for richer feedback. + +## Developers + +Backend developers must learn new syntaxes, tools, and methods for the front-end. Paired programming is a great way to teach while solving practical problems. diff --git a/src/pages/purpose.mdx b/src/pages/purpose.mdx new file mode 100644 index 0000000..643e673 --- /dev/null +++ b/src/pages/purpose.mdx @@ -0,0 +1,33 @@ +--- +layout: "@layouts/Layout.astro" +title: "Purpose" +--- + +import { SITE_DESCRIPTION } from '@src/consts.ts'; + +My purpose statement introduces this site, saying: + +>{SITE_DESCRIPTION}
+ +I break down this statement, explaining what it means to me: + +