|
8 | 8 | org: "Pulsar Informatics", |
9 | 9 | orgLink: "https://www.pulsarinformatics.com/", |
10 | 10 | role: "UX software engineer", |
11 | | - description: ` |
12 | | -- Serve as a core developer on a web-based fatigue management system, delivering real-time actionable insights to customers using GraphQL, TypeScript, and SvelteKit. |
13 | | -- Collaborate cross-functionally with engineering teams, product leadership, and customers to refine the end-user experience and contribute to roadmap planning. |
14 | | -- Contribute to technical planning and system design sessions.`, |
| 11 | + description: |
| 12 | + "I am a key developer on a web-based application offering workforce fatigue management solutions. We use GraphQL, TypeScript, and SvelteKit to deliver actionable insights in real time. I collaborate cross-functionally with other engineering teams, product leadership, and customers to refine the end-user experience and contribute to roadmap planning.", |
15 | 13 | }, |
16 | 14 | { |
17 | 15 | start: 2018, |
|
72 | 70 |
|
73 | 71 | <section aria-labelledby="about-header" class="about container"> |
74 | 72 | <div class="bio stack"> |
75 | | - <h2 id="about-header" class="header header--intro">Hi. I'm Ryan.</h2> |
| 73 | + <h2 id="about-header" class="header header--intro"> |
| 74 | + Hello. My name is Ryan. Nice to meet you. |
| 75 | + </h2> |
76 | 76 | <p> |
77 | | - I am a journalist, designer and developer based in Chicago, and I've spent my |
78 | | - career in the information communications business. Through visualization, writing, |
79 | | - editing and ux design, I find the important messages and express them in the best |
80 | | - ways possible. |
| 77 | + I'm a designer, developer, and problem solver based in the Chicago area. I use |
| 78 | + visualization, development, UX design, writing, and editing to dig past |
| 79 | + surface-level asks and quickly deliver what's actually needed. |
81 | 80 | </p> |
82 | 81 | <p> |
83 | | - Throughout the years, I've made it all: small static charts, large featured |
84 | | - interactives, standalone presentations and dashboard user interfaces. Each format |
85 | | - has its place, and choosing the right one for the job is a delicate, practical |
86 | | - art. |
| 82 | + Each step of my career has been spent working in cross-functional capacities, |
| 83 | + helping disparate teams communicate and collaborate on shared goals. Whether I'm |
| 84 | + designing, developing, or just managing a project, I bring a vigorous |
| 85 | + human-focused approach, keeping everyone's eyes on the final product. This |
| 86 | + requires speaking technology with content creators and content creation with |
| 87 | + technologists, cutting through friction so work moves forward without bottlenecks. |
87 | 88 | </p> |
88 | 89 | <p> |
89 | | - Whether the solution is a few carefully chosen words or something more, the goal |
90 | | - always is to distill mountains of information into meaningful and empowering |
91 | | - experiences. This makes repeat customers out of media consumers. |
| 90 | + Knowing when to collaborate, delegate, and run solo is an important skill. Success |
| 91 | + requires juggling the needs of multiple audiences on multiple platforms on |
| 92 | + deadline, and being a quick study who can ramp up and ship without a lengthy |
| 93 | + runway. |
92 | 94 | </p> |
93 | 95 | <p> |
94 | | - It's important to know when to collaborate, delegate and run solo. Success |
95 | | - requires juggling the needs of multiple audiences on multiple platforms, and being |
96 | | - a quick study doesn't hurt either. (All while on deadline, of course.) |
| 96 | + Throughout the years, I've made it all: featured interactives, standalone |
| 97 | + presentations, and dashboard user interfaces. Each format has its place, and |
| 98 | + choosing the right one for the job is a delicate, practical art. Whether the |
| 99 | + solution is a few carefully chosen words or something more, the goal always is to |
| 100 | + distill mountains of information into meaningful and empowering |
| 101 | + experiences—efficiently, without unnecessary complexity. |
97 | 102 | </p> |
98 | 103 |
|
99 | 104 | <h3 class="header">How I work</h3> |
100 | 105 | <p> |
101 | | - For starters, I work well with others. As a group, we need to discover our true |
102 | | - goals, define them clearly, and consider our resources. A well-scoped project is |
103 | | - important to success and, when it comes to data management, app architecture and |
104 | | - inclusive design, I always try to do things the "right way" within that scope. |
| 106 | + I work well with others. As a group, we need to discover our true goals, define |
| 107 | + them clearly, and consider our resources. A well-scoped project is important to |
| 108 | + success and, when it comes to data management, app architecture and inclusive |
| 109 | + design, I always try to do things the "right way" within that scope—building lean |
| 110 | + solutions that don't sacrifice quality for speed or speed for quality. |
105 | 111 | </p> |
106 | 112 | <p> |
107 | 113 | I speak fluent front-end: <strong>HTML</strong>, <strong>CSS</strong> and |
108 | | - <strong>Javascript</strong>. I know my way around Node and can get things done |
| 114 | + <strong>JavaScript</strong>. I know my way around Node and can get things done |
109 | 115 | with <strong>Python</strong> and <strong>Go</strong>. I'm a big fan of the |
110 | | - Svelte.js framework. I also know others (including <strong>Wordpress</strong>). I |
111 | | - like <strong>Github Actions</strong> and using |
112 | | - <strong>Google Spreadsheets</strong> as an ad-hoc CMS. |
113 | | - </p> |
114 | | - <p> |
115 | | - I appreciate good, useful documentation. From others, for the tools I'm using. |
116 | | - Also to me from my previous self. Future me needs a lot of help. |
| 116 | + <strong>SvelteKit</strong> framework for its ability to move quickly from |
| 117 | + prototype to production. I also know others (including <strong>Vue.js</strong> and |
| 118 | + <strong>WordPress</strong>). I like <strong>GitHub Actions</strong> and using |
| 119 | + <strong>Google Spreadsheets</strong> as an ad-hoc CMS—whatever gets the job done well |
| 120 | + without overengineering. |
117 | 121 | </p> |
| 122 | + <p>Let's talk. I look forward to hearing from you.</p> |
118 | 123 | </div> |
119 | 124 | <div class="work"> |
120 | 125 | <h2 class="header">Experience</h2> |
|
0 commit comments