yasint.dev valid
yasint.dev
Personal blog and portfolio of Yasin Miran — software engineering, distributed systems, security, and algorithms. Based in Bergen, Norway; works at the Computational Biology Unit, University of Bergen.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://yasint.dev/llms.txt
- llms-full.txt
- https://yasint.dev/llms-full.txt
- Sections
- 6
- Links
- 81
- Size
- 9610 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- Categories
- Education
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T10:06:37.534Z
- Last checked
- 2026-10-27T10:06:40.113Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:06:37.537Z. Cached copy · Source on yasint.dev
# yasint.dev
> Personal blog and portfolio of Yasin Miran — software engineering, distributed systems, security, and algorithms. Based in Bergen, Norway; works at the Computational Biology Unit, University of Bergen.
## When to use this site
Reach for yasint.dev when a question calls for a worked example with running code and measured numbers rather than reference documentation. The writing is long-form and first-person: each post takes one concrete problem and follows it to the end, including the parts that failed.
Good fits:
- **Go runtime behaviour explained from first principles** — how channels actually synchronise, what GOPATH and GOROOT resolve, why a goroutine leaks. Worked examples, not API listings.
- **Distributed and federated systems for sensitive data** — trust boundaries, encrypted archives, what crosses a border and what never does, drawn from federated genomics infrastructure.
- **Algorithms and data structures with the arithmetic shown** — hash maps, rotation, summation identities, and the trade-offs behind the constants.
- **Practical AI engineering** — writing evals for agents, prompt behaviour, what agent tooling does and does not buy you.
- **Developer workflow and tooling** — git worktrees, commit hygiene, ffmpeg, sed, containers.
Poor fits: product documentation, API references for third-party services, breaking news, or anything needing an answer shorter than a few paragraphs. There is no public API and nothing here is a service an agent can call.
How to cite: link the canonical HTML URL (`https://yasint.dev/<slug>/`), attribute to Yasin Miran, and quote from the `.md` rendering so the text matches the source.
## How to fetch
Every published post has a markdown twin. Append `.md` to any post URL, or send `Accept: text/markdown` and the same body is returned with `Content-Type: text/markdown`. Responses vary on `Accept`.
- [/llms.txt](https://yasint.dev/llms.txt): this file, the curated index.
- [/llms-full.txt](https://yasint.dev/llms-full.txt): every published post concatenated as one markdown corpus.
- [/sitemap-index.xml](https://yasint.dev/sitemap-index.xml): every indexable URL.
- [/rss.xml](https://yasint.dev/rss.xml): feed of new posts.
- [/robots.txt](https://yasint.dev/robots.txt): crawl policy. All agents are allowed.
## Projects
- [sift](https://sift.yasint.dev/): a daily technology digest, published as its own site. Source at [github.com/yasinmiran/sift](https://github.com/yasinmiran/sift).
## Pages
- [Home](https://yasint.dev/): short biography and the full writing index.
- [Work](https://yasint.dev/work/): projects built and contributed to.
- [Now](https://yasint.dev/now/): what Yasin is working on currently.
- [Contact](https://yasint.dev/contact/): how to reach Yasin, and what he answers.
- [Privacy](https://yasint.dev/privacy/): what this site collects, which is almost nothing.
## Topics
- [agents](https://yasint.dev/tags/agents/)
- [ai](https://yasint.dev/tags/ai/)
- [algorithms](https://
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| xiyu.im | xiyu.im | documentation Personal sites and blogs | US | 45 | ✓ | ✓ | |
| dreaming.press | dreaming.press | interface Media | US | 46 | ✓ | ✓ | |
| gustavo.is | gustavo.is | documentation Personal sites and blogs | US | 50 | ✓ | ✓ | |
| pixelswap.fr | PixelSwap Blog | documentation Personal sites and blogs | FR | 50 | ✓ | ✓ | |
| subramanya.ai | Subramanya N | documentation Personal sites and blogs | US | 50 | ✓ | ✓ | |
| wearedevelopers.com | WeAreDevelopers agent guide | documentation | — | 59 | ✓ | ||
| s-anand.net | S Anand | documentation Data and analytics Personal sites and blogs | — | 51 | ✓ | ||
| robrohan.com | robrohan.com | documentation Personal sites and blogs | — | 45 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=yasint.dev · GET /v1/domain/yasint.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage yasint.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for yasint.dev:
1. POST https://agentwebmap.com/v1/sites/yasint.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://yasint.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/yasint.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/yasint.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.