# fernandofatech The profile README that documents who I am and what I build — straight to the point. - URL: https://fernando.moretes.com/open-source/fernandofatech - Markdown: https://fernando.moretes.com/open-source/fernandofatech/guide.md?lang=en - GitHub: https://github.com/fernandofatech/fernandofatech - Homepage: https://fernando.moretes.com - Language: n/a - Topics: github-profile, moretes, portfolio, profile, readme, solution-architect, solution-architecture - Stars: 2 - Forks: 0 - Updated: 2026-05-16T01:16:18Z --- fernandofatech/fernandofatech is the special GitHub profile repository that acts as my public technical business card — presenting my stack, highlighted projects, and working style as a Senior Solutions Architect focused on AWS, event-driven systems, and platform engineering. ## What this repository is and why it exists GitHub has a little-known mechanic: when you create a public repository with the same name as your username — in this case `fernandofatech/fernandofatech` — the `README.md` at the root is automatically rendered on your profile page. It is the equivalent of a homepage inside GitHub itself. I use this space deliberately. Rather than leaving the profile empty or with a generic bio, the README functions as a living document that answers three concrete questions: **who I am**, **what I work on**, and **what I have built**. There is no marketing copy. There is an honest list of technologies I use day-to-day, a table of real projects with direct links to their repositories, and a clear invitation for anyone who wants to talk about cloud architecture, FinOps, or event-driven systems. The repository also anchors the portfolio ecosystem I maintain at `fernando.moretes.com`, connecting the GitHub profile to the personal site and LinkedIn in a coherent way. Anyone who lands on my profile — whether a recruiter, a fellow engineer, or a potential client — finds enough context to understand my work without leaving GitHub. ## What the README covers - **Technical identity** — title, focus, and direct links to LinkedIn and GitHub in a clean, centered header. - **Actual stack** — six categories (Cloud & Infra, Backend, Frontend, Data & ML, DevOps, Security) listing tools I actually use in production. - **Highlighted projects** — table with six relevant public repositories, each with a one-line description and direct link. - **GitHub stats** — cards generated via `github-readme-stats` showing overall activity and top languages. - **Contact point** — direct connection section, no forms, pointing to LinkedIn and the repository list. - **Bilingual** — footer in PT-BR and EN documenting the repository as part of the portfolio ecosystem. ## How the profile connects to the portfolio ecosystem The special profile repository is the entry point. From it, visitors reach public projects, the personal site, and LinkedIn. ### 👤 Visitor - Visitor GitHub / Web (user) ### 🐙 GitHub Profile - fernandofatech/ fernandofatech README (frontend) - github-readme-stats Vercel API (external) ### 🌐 Portfolio Ecosystem - fernando.moretes.com Personal Site (frontend) - LinkedIn fernandofatech (external) - Public Repos AWS-Cost-Calculator queue-advisor etc. (compute) ### Flows - visitor -> profile_readme: visits profile - profile_readme -> stats_api: fetches stats - profile_readme -> public_repos: direct links - profile_readme -> portfolio_site: homepage link - profile_readme -> linkedin: badge / link ## How the README is structured — design decisions Writing a good profile README is an exercise in synthesis. Most profiles fail at two extremes: either too empty (just the default GitHub bio) or they become a marketing page with animated GIFs and endless badge lists that say nothing about how the person actually works. My approach was different. The document starts with what matters to someone evaluating an architect: **what I do**, not who I am in personal terms. The title `Senior Solution Architect · AWS · Serverless · Event-Driven Systems` is precise — not generic. The `About me` section uses short bullets that describe concrete behaviors: I design ADRs, I build FinOps-aware systems, I coach teams. These are verifiable claims backed by the public repositories. The projects table is deliberately lean — six entries, one line per project. Each row has a clickable name and a functional description. There are no stars, languages, or dates; that information lives in the repositories themselves. The goal here is to orient the visitor, not impress them with metrics. The GitHub stats cards are generated dynamically via the public `github-readme-stats` API hosted on Vercel. They reflect real activity and update automatically — zero manual maintenance. The `tokyonight` theme with `hide_border=true` keeps the aesthetic clean without distracting from the content. Finally, the bilingual footer (PT-BR / EN) was a conscious choice: my work moves between Brazilian and international contexts, and the README should reflect that. ## How to use this repository as a reference for your own profile 1. **Create the special profile repository** — On GitHub, create a new public repository with exactly the same name as your username (e.g., `yourname/yourname`). GitHub recognizes this pattern and renders the `README.md` on your profile automatically. 2. **Clone and adapt the README** — Clone `https://github.com/fernandofatech/fernandofatech`, edit `README.md` replacing name, links, stack, and projects with your own. The file uses only standard Markdown and inline HTML for the `div align=center` — no build dependencies. 3. **Configure the stats cards** — Replace `fernandofatech` with your username in the `github-readme-stats` card URLs. The `theme`, `hide_border`, and `langs_count` parameters are optional and documented at `anuraghazra/github-readme-stats`. 4. **Update the LinkedIn and GitHub badges** — The badges use `shields.io`. Replace the username parameter in the URLs and the corresponding `href` links. No API key is required for these public badges. 5. **Push and verify** — Commit and push to the main branch. Visit `github.com/yourname` — the README should appear immediately below pinned repositories. If it does not, confirm the repository is public and the file is named exactly `README.md`. _Quick commands to clone and start adapting_ ```bash # Clone the profile repository git clone https://github.com/fernandofatech/fernandofatech.git my-profile cd my-profile # Edit the README with your preferred editor code README.md # or: vim README.md # Replace occurrences of 'fernandofatech' with your GitHub username # macOS / Linux sed -i '' 's/fernandofatech/yourusername/g' README.md # Commit and push to YOUR profile repository git remote set-url origin https://github.com/yourusername/yourusername.git git add README.md git commit -m "chore: initialize profile README" git push origin main ``` > **The special profile repository needs no CI, build pipeline, or dependencies:** Unlike other portfolio projects, this repository is pure Markdown. There is no `package.json`, Dockerfile, or Actions workflow required for it to work. GitHub renders the file directly. If you want to add automations (e.g., auto-updating recent posts or metrics), that is possible via GitHub Actions, but that is not the case here — and deliberately so: fewer moving parts, fewer things to break. ## Frequently asked questions ### Why do the stats cards sometimes fail to load? The cards depend on the public `github-readme-stats` API hosted on Vercel. It occasionally hits GitHub rate limits or experiences instability. There is nothing to fix in the repository itself — it is an external dependency. If this is a recurring issue, the alternative is to self-host your own instance of `anuraghazra/github-readme-stats`. ### Can I use this README as a template for my own profile? Yes. The repository is public. Clone, adapt, and use it. There is no restrictive license — it is a personal profile README, not a product. Just replace the personal data, links, and projects with your own. ### Is the `fernando.moretes.com` site in this repository? No. This repository contains only the GitHub profile `README.md`. The personal site is a separate project. The link appears in the README as part of the portfolio ecosystem, but the site source code lives in a different repository. ### How often is this README updated? I update it when there are relevant changes: a new public project worth highlighting, a shift in technical focus, or when a link goes stale. There is no fixed cycle — it is event-driven maintenance, as it should be. ## Who this repository is useful for This repository serves two audiences. For anyone landing on my GitHub profile — recruiters, engineers, partners — it delivers enough context in under two minutes of reading: what I do, what I work with, and what I have built. For other engineers and architects who want to structure their own GitHub profile professionally, it works as a concrete, adaptable example of how to use the profile README mechanism without falling into badge overload or lack of substance. It is not a framework, has no dependencies, requires no setup. It is well-written Markdown with clear intent — and sometimes that is exactly enough. ## References - [fernandofatech/fernandofatech — GitHub](https://github.com/fernandofatech/fernandofatech) - [fernando.moretes.com — Portfolio Site](https://fernando.moretes.com) - [anuraghazra/github-readme-stats — Stats Cards](https://github.com/anuraghazra/github-readme-stats) - [shields.io — Badge Generator](https://shields.io) - [GitHub Docs — Managing your profile README](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme) ## Links - [GitHub repository](https://github.com/fernandofatech/fernandofatech) - [Homepage](https://fernando.moretes.com)