@@ -7,8 +7,9 @@ import styled from 'styled-components';
7
7
8
8
const AboutMeHeader = styled . div `
9
9
float: left;
10
- margin-right: 3em;
11
- margin-bottom: 0.5em;
10
+ margin-right: 1em;
11
+ margin-bottom: 1em;
12
+ padding: 1em;
12
13
13
14
@media (max-width: 600px) {
14
15
float: none;
@@ -37,6 +38,25 @@ const Picture = styled.img`
37
38
}
38
39
` ;
39
40
41
+ const Blurb = styled . section `
42
+ color: #333;
43
+ font-size: 1.1em;
44
+ letter-spacing: 0.01em;
45
+ text-align: justify;
46
+ text-justify: inter-character;
47
+
48
+ @media (max-width: 600px) {
49
+ letter-spacing: inherit;
50
+ font-size: 1.2em;
51
+ }
52
+
53
+ @media (max-width: 500px) {
54
+ }
55
+
56
+ @media (max-width: 475px) {
57
+ }
58
+ ` ;
59
+
40
60
export default function About ( ) {
41
61
return (
42
62
< Layout >
@@ -87,71 +107,63 @@ export default function About() {
87
107
</ div >
88
108
</ AboutMeHeader >
89
109
90
- < section >
91
- < div
92
- style = { {
93
- fontSize : '1.1em' ,
94
- textJustify : 'inter-character' ,
95
- textAlign : 'justify' ,
96
- } }
97
- >
98
- < p >
99
- Hi there! I'm a software engineer with over 10 years of professional
100
- experience. I started as a self-taught coder, making webpages
101
- (Geocities 😍) and writing small utilities to make my IT help desk
102
- job easier.
103
- </ p >
104
-
105
- < p >
106
- I broke into the industry as a tester at a small startup that
107
- frequently deployed and demoed its product to investors. This
108
- experience taught me how critical software quality is to the
109
- business—especially as I observed how development practices directly
110
- impacted the app's reliability. To help keep up with the rapid pace
111
- of development (one-week sprints), I implemented extensive test
112
- automation, which eventually allowed me to take on development work.
113
- This shift gave me more control over the quality of the product.
114
- </ p >
115
-
116
- < p >
117
- After the startup, I moved into software delivery consulting,
118
- bringing my experience in both development and testing. I spent my
119
- time pairing and mobbing with teams to implement application code
120
- while advocating for better testing practices—asking about potential
121
- test scenarios, encouraging developers to update end-to-end browser
122
- tests, and generally influencing how teams thought about testing as
123
- an integral part of development.
124
- </ p >
125
-
126
- < p >
127
- The more I worked as both a developer and tester, the more I saw a
128
- deep connection between good implementation design and testability.
129
- My "tester spidey sense" would tingle during story refinement or
130
- while pairing on a feature. I had learned through experience—often
131
- painful experience—how certain design decisions could create testing
132
- headaches. Over time, I developed a strong intuition for spotting
133
- trouble before it happened, and my technical background allowed me
134
- to address it effectively. Being able to wear both hats at the same
135
- time turned out to be a major superpower.
136
- </ p >
137
-
138
- < p >
139
- Over my career, I've worked across multiple industries, helping
140
- organizations design and build greenfield applications, modernize
141
- legacy systems, and establish best practices in development,
142
- testing, and delivery. My expertise spans the entire software
143
- lifecycle—from early product discussions to defining robust testing
144
- strategies, building automation frameworks, and mentoring teams on
145
- implementing scalable, testable, maintainable software.
146
- </ p >
147
-
148
- < p >
149
- Outside of work, I love writing test tools, game development,
150
- cooking, and synthesizers. I love to learn new things, so this list
151
- is constantly growing.
152
- </ p >
153
- </ div >
154
- </ section >
110
+ < Blurb >
111
+ < p >
112
+ Hi there! I'm a software engineer with over 10 years of professional
113
+ experience. I started as a self-taught coder, making webpages
114
+ (Geocities 😍) and writing small utilities to make my IT help desk job
115
+ easier.
116
+ </ p >
117
+
118
+ < p >
119
+ I broke into the industry as a tester at a small startup that
120
+ frequently deployed and demoed its product to investors. This
121
+ experience taught me how critical software quality is to the
122
+ business—especially as I observed how development practices directly
123
+ impacted the app's reliability. To help keep up with the rapid pace of
124
+ development (one-week sprints), I implemented extensive test
125
+ automation, which eventually allowed me to take on development work.
126
+ This shift gave me more control over the quality of the product.
127
+ </ p >
128
+
129
+ < p >
130
+ After the startup, I moved into software delivery consulting, bringing
131
+ my experience in both development and testing. I spent my time pairing
132
+ and mobbing with teams to implement application code while advocating
133
+ for better testing practices—asking about potential test scenarios,
134
+ encouraging developers to update end-to-end browser tests, and
135
+ generally influencing how teams thought about testing as an integral
136
+ part of development.
137
+ </ p >
138
+
139
+ < p >
140
+ The more I worked as both a developer and tester, the more I saw a
141
+ deep connection between good implementation design and testability. My
142
+ "tester spidey sense" would tingle during story refinement or while
143
+ pairing on a feature. I had learned through experience—often painful
144
+ experience—how certain design decisions could create testing
145
+ headaches. Over time, I developed a strong intuition for spotting
146
+ trouble before it happened, and my technical background allowed me to
147
+ address it effectively. Being able to wear both hats at the same time
148
+ turned out to be a major superpower.
149
+ </ p >
150
+
151
+ < p >
152
+ Over my career, I've worked across multiple industries, helping
153
+ organizations design and build greenfield applications, modernize
154
+ legacy systems, and establish best practices in development, testing,
155
+ and delivery. My expertise spans the entire software lifecycle—from
156
+ early product discussions to defining robust testing strategies,
157
+ building automation frameworks, and mentoring teams on implementing
158
+ scalable, testable, maintainable software.
159
+ </ p >
160
+
161
+ < p >
162
+ Outside of work, I love writing test tools, game development, cooking,
163
+ and synthesizers. I love to learn new things, so this list is
164
+ constantly growing.
165
+ </ p >
166
+ </ Blurb >
155
167
</ Layout >
156
168
) ;
157
169
}
0 commit comments