andrew/portfolio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tightens some language in values, makes the paragraph headings bigger

Browse Source
This commit is contained in:
Andrew Gioia 2026-05-01 15:05:11 -04:00
parent 08d57fa835
commit f7fd78b0e0
Signed by: andrew
GPG Key ID: FC09694A000800C8
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
assets/css/site.css
View File

@ -967,9 +967,11 @@ body#values {
em:first-child {
color: var(--text);
display: block;
font-size: 1.25rem;
font-style: normal;
font-weight: 700;
padding-bottom: 0.5rem;
line-height: 1.3;
padding-bottom: 0.75rem;
}
&:not(:has(em)) {

6
content/philosophy.md
View File

@ -12,7 +12,7 @@ footnotes:
<em>I care deeply about how something looks, but aesthetics are never the point on their own.</em> Good design should feel thoughtful, trustworthy, and calm; it should reduce cognitive load, never add to it. The goal is to make software more useful and easier to use. If a visual choice, interaction, or animation does not improve the experience, it probably doesn't belong there. **Dark patterns are an abomination.** Delight matters and it should come primarily from responsiveness, clarity, and personality.
<em>I believe good interfaces should respect the user and their system.</em> The browser, HTML and CSS are already an extraordinarily capable platform, and I try to stay as close to the browser's native strengths as possible. If something can be done well with HTML and CSS, I will always do that rather than reach for JavaScript as a crutch.
<em>Good interfaces should respect the user and their system.</em> The browser, HTML and CSS are already an extraordinarily capable platform, and I try to stay as close to the browser's native strengths as possible. If something can be done well with HTML and CSS, I will always do that rather than reach for JavaScript as a crutch.
I am not opposed to frameworks or complex client-side applications when they're justified, I just think they rarely are and too often introduce more usability, accessibility, and performance problems than the ones they solve. **JavaScript should enhance an experience, not become a requirement** by default.&dagger;
@ -20,10 +20,10 @@ I am not opposed to frameworks or complex client-side applications when they're
<em>I don't believe products need to wait for perfect alignment before they improve.</em> Some of the most harmful thinking on product teams comes from the idea that everything has to be redesigned at once in order to be worth doing. Consistency matters, but so does momentum. If something is broken, confusing, or clearly improvable, **it's often better to make it better now than to wait for the ideal future state that may never arrive**. Many interfaces stay bad for years because teams are too concerned with doing every related piece at the same time.
<em>In an org, good design starts from a strong brief.</em> Every good design effort needs a clear understanding of the users, the problems that need solving, and the constraints that shape the solution. On larger teams especially, the brief is what keeps the work focused when opinions multiply or strong personalities have outsized influence. Designers should be part of that conversation early. The quality of the brief often determines the quality of everything that follows.
<em>Good design starts from a strong brief.</em> Every good design effort needs a clear understanding of the users, the problems that need solving, and the constraints that shape the solution. On larger teams especially, the brief is what keeps the work focused when opinions multiply or strong personalities have outsized influence. Designers should be part of that conversation early. The quality of the brief often determines the quality of everything that follows.
<em>I prefer interfaces that are minimal, but not anonymous.</em> White space, alignment, and typography can solve an enormous number of visual problems. At the same time, software should not lose all of its personality in the name of reduction. A product can be clean, efficient, and quiet while still feeling specific to the team, company, or people who made it. Off the shelf systems like shadcn are amazing but **every app doesn't need to look the same.** Minimalism is useful when it sharpens the experience, not when it makes every interface feel interchangeable.
<em>Type is just as much a part of the design as everything else.</em> I often design around or with the words on the screen, and it's ok to add another line of text or force everything to be a single line when it makes the design and usability better.
<em>Finally, I believe design benefits from collaboration, but not from design by committee.</em> Everyone has opinions about interfaces because everyone uses them. That's normal and often useful! **But not every opinion should carry the same weight**, and not every preference should become a product decision. Good design requires judgment: knowing when to listen, when to test, when to defend a choice, and when to change course. My job is not to impose my taste, **my job is to make informed decisions in service of the user and the product, but my taste does matter** and I will rely on it too.
<em>Finally, design benefits from collaboration, but not from design by committee.</em> Everyone has opinions about interfaces because everyone uses them. That's normal and often useful! **But not every opinion should carry the same weight**, and not every preference should become a product decision. Good design requires judgment: knowing when to listen, when to test, when to defend a choice, and when to change course. My job is not to impose my taste, **my job is to make informed decisions in service of the user and the product, but my taste does matter** and I will rely on it too.