+
+
++ {title} + {badge && {badge}} +
+ {meta &&{meta}
} +{desc}
+ { + tags.length > 0 && ( +
+ {tags.map((tag: string) => (
+ {tag}
+ ))}
+
+ )
+ }
+ {name}
- -- {heroLine} -
- - {stats && stats.length > 0 && ( -{status.label}
} -{meta}
} +{desc}
+ { + tags.length > 0 && ( +{subtitle}
+- {project.tagline} -
- -{project.description}
- - {project.packages && ( -{pkg.name}
- - {project.tech.join(' · ')} -
- )} -{lead}
-Individual contributor
++ I am a senior IC for teams that need someone to own the hard platform surface directly: cloud + architecture, cost, Terraform, secrets, CI/CD, reliability, security operations, and the internal + tools that keep those pieces from becoming a permanent tax. +
+ +{signal.body}
+Contribution modes
+{mode.context}
++ {mode.proof} +
+Operating style
+{principle.body}
+Curriculum vitae
+{resume.about.label}
++ {resume.about.tagline} +
+{text}
)} +{job.summary}
} + {job.tech && ( ++ {job.tech.join(' · ')} +
+ )} +{resume.earlierCareer.summary}
++ {category.keywords.join(', ')} +
++ {edu.institution} · {edu.startDate}-{edu.endDate} +
+{edu.honors.join(' · ')}
++ Staff Platform & DevOps Engineer +
++ I make messy infrastructure operable: clearer ownership, safer delivery, better defaults, and + automation that holds up after I leave the room. +
++ {resume.about.heroLine} +
+ +{point.value}
+{point.detail}
+Individual contributor
++ Cloud architecture, Terraform, secrets, reliability, security operations, and cost pressure + treated as one system. +
++ Terraform generation, secrets propagation, CI/CD standards, and release plumbing built to + remove repeated manual work. +
++ Better defaults, clearer workflows, and standards other engineers can use without waiting on + a gatekeeper. +
+Outcome stories
++ {story.eyebrow} +
+{story.summary}
+ + )) + } +Selected work
+Writing
++ {post.data.description} +
+ + ))} +Proof beyond the resume
++ The CV gives the chronology. Projects show public artifacts. These outcome stories connect the + two: what changed, what systems were built, and why the work is senior platform work rather than + a list of tools. +
+{story.eyebrow}
+{story.summary}
++ {item} +
+ ))} +Operating model
+{principle.body}
+Open-source portfolio
++ These are the public artifacts that make the resume less abstract: shipped tools, package + surfaces, release systems, and implementation details you can inspect. +
+{pkg.name}
+ {text}
)} -{resume.earlierCareer.summary}
{resume.earlierCareer.positions.map((pos) => ( diff --git a/src/pages/rss.xml.ts b/src/pages/rss.xml.ts new file mode 100644 index 00000000..44ba7dca --- /dev/null +++ b/src/pages/rss.xml.ts @@ -0,0 +1,22 @@ +import { getCollection } from 'astro:content' +import rss from '@astrojs/rss' +import type { APIContext } from 'astro' +import resume from '@/content/resume' +import type { WritingEntry } from '@/content.config' + +export async function GET(context: APIContext) { + const posts = (await getCollection('writing', ({ data }: WritingEntry) => !data.draft)).sort( + (a: WritingEntry, b: WritingEntry) => b.data.pubDate.valueOf() - a.data.pubDate.valueOf() + ) + return rss({ + title: `${resume.about.name} — Writing`, + description: resume.about.tagline, + site: context.site ?? resume.about.url, + items: posts.map((post: WritingEntry) => ({ + title: post.data.title, + description: post.data.description, + pubDate: post.data.pubDate, + link: `/writing/${post.id}/`, + })), + }) +} diff --git a/src/pages/services.astro b/src/pages/services.astro new file mode 100644 index 00000000..51033cd2 --- /dev/null +++ b/src/pages/services.astro @@ -0,0 +1,101 @@ +--- +import BaseLayout from '@/layouts/BaseLayout.astro' +import resume from '@/content/resume' +import { operatingPrinciples, outcomeStories } from '@/content/site' + +const services = [ + { + title: 'Platform and DevOps audit', + body: 'Map the real state of cloud accounts, CI/CD, Terraform, secrets, observability, incident response, and ownership boundaries.', + }, + { + title: 'Cloud cost reduction', + body: 'Find the high-leverage waste: serverless migration candidates, idle capacity, right-sizing, storage churn, and missing guardrails.', + }, + { + title: 'Terraform and automation systems', + body: 'Build maintainable infrastructure workflows, provider abstractions, CI gates, and internal tooling that teams can keep using.', + }, + { + title: 'SRE and reliability foundations', + body: 'Establish monitoring, alerting, runbooks, release safety, and incident practices without turning a small team into a process shop.', + }, +] +--- + +Independent consulting
++ I am useful where infrastructure, delivery, security operations, and cost control are tangled + together. The work is making ownership visible, removing repeated coordination, and leaving teams + with a platform they can operate without turning one person into the bottleneck. +
+ +{service.body}
+Related outcomes
++ {story.eyebrow} +
+Working model
+{principle.body}
++ {formatDate(post.data.pubDate)} + {post.data.updatedDate && ` · updated ${formatDate(post.data.updatedDate)}`} +
+Notes and case studies
++ No public posts are published yet. The CV and projects pages are the canonical proof + surfaces while longer case studies are being pulled into the site. +
+ ) : ( ++ {formatDate(post.data.pubDate)} +
++ {post.data.description} +
+ +