Simplify "About Me" structure and enhance content readability

packages/app/client/routes/about-me.tsx

@@ -90,9 +90,8 @@ export default function AboutMe(_: Route.ComponentProps): ReactElement {
 	return (
 		<article
 			className={clsx(
-				'prose dark:prose-invert flex w-full max-w-full flex-col justify-start font-comic',
+				'prose dark:prose-invert flex w-full max-w-full flex-col justify-start font-comic prose-blockquote:font-light prose-blockquote:not-italic',
 			)}
-			style={{ fontSynthesisWeight: 'initial' }}
 		>
 			<T.h2 className={clsx('font-comic')}>
 				<div className={clsx('inline-block animate-wiggle hover:animate-none')}>👋</div> Hi, I'm

packages/app/content/copy/about-me-v4.md

@@ -11,15 +11,21 @@ I needed a new career that was **as intellectually satisfying as history**, but
 Realizing I could get **paid** to tinker with complex systems and break things for a living felt like **finding a loophole in the Matrix**. Instead of being a historian documenting **the fall of empires**, I could now **cause server crashes in real-time**. Jackpot 🎰💸.
 Turns out, **breaking things apart to understand them** works just as well in tech as it does in history — except now, instead of uncovering the past, I get to **accidentally deploy bugs into the future**.
 
-And while the universe may be **fundamentally meaningless**, my search for meaning hasn’t been in vain. I’ve found purpose in **craftsmanship**, **curiosity**, and the **joy of learning**. And if I don’t always know the question, at least I can take comfort in knowing the answer—**42** 🚀.
+And while the universe may be **fundamentally meaningless**, my search for meaning hasn’t been in vain. I’ve found purpose in **craftsmanship**, **curiosity**, and the **joy of learning**. And if I don’t always know "_the question_", at least I can take comfort in knowing "_the answer_" — **42** 🚀.
 
 
 
 ## 💻 My Professional Philosophy
 
-After **more than a decade** in the field, I’ve come to see software engineering as more than just a job — it’s a craft. 🛠️ I don’t just aim to write working software; **I aim to write _well-crafted_ software**. This mindset is at the core of **Software Craftsmanship**, an idea championed by **Bob Martin** (Uncle Bob) and later formalized in the [*Software Craftsmanship Manifesto*](https://manifesto.softwarecraftsmanship.org/) by **Sandro Mancuso** and others ✍️. It builds upon Agile principles but pushes them further, focusing on **professionalism, responsibility, and continuous learning** 📚⚡.
+After **more than a decade** in software development, and in my pursuit of refining my craft, I've explored countless methodologies and guidelines on what it means to be a “professional”. Eventually, I discovered the **Software Craftsmanship** movement, whose [manifesto](https://manifesto.softwarecraftsmanship.org/) truly struck a chord. Over time, I've **embraced its principles as the foundation of my work**, finding them both practical and deeply aligned with the kind of developer I aspire to be.
 
-Along the way, I also discovered **Extreme Programming (XP)**, a set of technical practices introduced by **Kent Beck** in the late ’90s. XP emphasizes writing **simple, high-quality code** through **discipline, feedback, and iteration**. 🔄 These ideas deeply resonate with how I approach software development 💡✨.
+> As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:
+> - _Not only working software_, but also **well-crafted software**
+> - _Not only responding to change_, but also **steadily adding value**
+> - _Not only individuals and interactions_, but also **a community of professionals**
+> - _Not only customer collaboration_, but also **productive partnerships**
+>
+> That is, in pursuit of the items on the _left_ we have found the items on the _right_ to be indispensable.
 
 ### 🛠️ Craft Over Code
 

packages/app/content/copy/software-craftmenship.md

@@ -3,7 +3,7 @@ Excerpt From "SOLID: The Software Design and Architecture Handbook" by Khalil St
 # Software Craftsmanship (2006 — today)
 
 There had been some talk about Software Craftsmanship before. The first book to hint that software development might be more of a trade than a science was “The Pragmatic Programmer: From Journeymen to Master.” It drew comparisons between how developers learn and gain seniority to the apprenticeship model in medieval Europe, and was one of the first texts to attempt to distill some sense of professionalism toward software developers.
-In 2006, Peter McBreen published the book Software Craftsmanship, solidifying the name and explaining many of today’s professional practices. Unfortunately for the craftsmanship community around this time, Agile had the limelight. We considered Agile to be the solution to our biggest problems, giving little need for this thing called Software Craftsmanship.
+In 2006, Peter McBreen published the book **Software Craftsmanship**, solidifying the name and explaining many of today’s professional practices. Unfortunately for the craftsmanship community around this time, Agile had the limelight. We considered Agile to be the solution to our biggest problems, giving little need for this thing called **Software Craftsmanship**.
 To nudge craftsmanship back into the spotlight, in 2008, Uncle Bob proposed a fifth value for the Agile Manifesto: “craftmanship over execution”.
 Since things weren’t going the way we wanted them to with Agile, and because we deviated from technical Agile frameworks like XP, in 2009, a group of developers aimed to produce something to be written down that could concisely describe the craftsmanship movement. Eventually, we created the Software Craftsmanship Manifesto. The manifesto, printed below, took the Agile Manifesto’s values and pushed it further, promoting technical excellence and professionalism.
 
@@ -12,21 +12,19 @@ Since things weren’t going the way we wanted them to with Agile, and because w
 The manifesto is as follows:
 “As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value the following:
 
-- Not only working software, but also well-crafted software
-- Not only responding to change, but also steadily adding value
-- Not only individuals and interactions, but also a community of professionals
-- Not only customer collaboration, but also productive partnerships”
+- Not only working software, but also **well-crafted software**
+- Not only responding to change, but also **steadily adding value**
+- Not only individuals and interactions, but also **a community of professionals**
+- Not only customer collaboration, but also **productive partnerships**”
 
 # Back to Basics (XP)
 
-There’s still a lot of work to be done, but today, we’re seeing some positive changes in the
-software industry around Agile and Software Craftsmanship.
+There’s still a lot of work to be done, but today, we’re seeing some positive changes in the software industry around Agile and Software Craftsmanship.
 
 **The software craftsmanship community is growing.**
 Developers worldwide are organizing meetups, signing the original manifesto, and spreading the word of professionalism. This community may very well be the one that comes together to popularize and standardize the approach to solving that 60-year old productivity and quality problem.
 
-Also, in 2019, a frustrated Uncle Bob published a book titled “Clean Agile: Back to Basics”, which is almost entirely
-**a walkthrough of the technical practices of XP**.
+Also, in 2019, a frustrated Uncle Bob published a book titled “Clean Agile: Back to Basics”, which is almost entirely **a walkthrough of the technical practices of XP**.
 
 If you ask me about my future assumptions, I would say that in the next decade or so, we’re going to see the craftsmanship and Agile communities converge. It’s only a matter of time before this happens because they share the same goal:
 **to deliver high-quality software on time**.
@@ -44,9 +42,7 @@ Craftsmanship is professionalism in software development.
 
 Software Craftsmanship is a professionalism **mindset**.
 It’s not about if you have a certification, if you’re a senior developer, or if you practice TDD all the time.
-It’s about taking **responsibility** for our careers, clients, and community. It also means taking *
-*pride** in our solutions, working with **pragmatism
-**, and seeking to constantly improve our reputations with the good work we do.
+It’s about taking **responsibility** for our careers, clients, and community. It also means taking **pride** in our solutions, working with **pragmatism**, and seeking to constantly improve our reputations with the good work we do.
 
 ## Are you a software craftsperson?