Oğuzhan Kurum
@oguzhan
Software engineer. Sharing the tools and resources that actually make me ship faster.
Nolan Pierce
@nolan
I test AI tools like a skeptical operator, not a hype account.
cengizfoan
@cengizfoan
Entrepreneur & Investor
oguzhankurumdev
@oguzhankurumdev
fatehkudsi
@fatehkudsi
Tap a card or Start Watch — swipe like Reels
17 BridgesOğuzhan Kurum
@oguzhan · 45 days ago
A concise, approachable introduction to the HTTP protocol on MDN Web Docs — a useful starting point for developers and learners seeking an accessible overview of core HTTP concepts.
Oğuzhan Kurum
@oguzhan · 62 days ago
Railway’s public networking guide is a practical reference for custom domains, TLS, and production service exposure.
Oğuzhan Kurum
@oguzhan · 64 days ago
The official introduction shows how protocol buffers, generated clients, streaming, deadlines, and language interoperability fit together. It is a clear starting point for deciding when typed RPC is a better boundary than ad hoc JSON endpoints.
Oğuzhan Kurum
@oguzhan · 64 days ago
Start with the official overview when observability tools feel like unrelated dashboards. OpenTelemetry explains the vendor-neutral model for signals, context propagation, collectors, instrumentation, and exporting telemetry across services.
Oğuzhan Kurum
@oguzhan · 64 days ago
The official concepts guide connects workloads, services, storage, configuration, security, policies, scheduling, and cluster administration. It is the right starting point before copying manifests whose runtime behavior you cannot predict.
Oğuzhan Kurum
@oguzhan · 64 days ago
The official DevTools documentation is worth browsing beyond Elements and Console. Network traces, performance recordings, memory tools, accessibility inspection, coverage, sensors, and protocol tooling can replace a surprising amount of guesswork.
developer.chrome.comOğuzhan Kurum
@oguzhan · 64 days ago
Use this official guide to understand build context, layers, cache behavior, multi-stage builds, BuildKit, secrets, and reproducibility. It helps turn a Dockerfile from a copied recipe into an artifact you can reason about.
Oğuzhan Kurum
@oguzhan · 64 days ago
The overview explains why fetching, caching, synchronization, invalidation, retries, and background refresh belong together. Read it before building another collection of custom loading flags and duplicated request effects.
tanstack.comOğuzhan Kurum
@oguzhan · 64 days ago
Zod is useful wherever static types meet untrusted runtime data. Its docs make schemas, parsing, refinements, transformations, error handling, JSON Schema, and ecosystem integrations easy to discover without hiding the underlying contract.
zod.devOğuzhan Kurum
@oguzhan · 64 days ago
This is the security reference to consult while designing authentication, sessions, passwords, uploads, APIs, SSRF defenses, logging, and secrets handling. Each guide is focused enough to apply during implementation and review.
cheatsheetseries.owasp.orgOğuzhan Kurum
@oguzhan · 64 days ago
Use the official Actions documentation for workflows, events, expressions, permissions, environments, reusable jobs, caching, and security. It is especially valuable when a copied workflow almost works but its trust boundaries are unclear.
docs.github.comOğuzhan Kurum
@oguzhan · 64 days ago
The Playwright introduction gets you from installation to resilient browser tests quickly, then opens into fixtures, traces, screenshots, multiple browsers, mobile emulation, and CI. It is the reference to keep beside any serious web QA loop.
Oğuzhan Kurum
@oguzhan · 64 days ago
pnpm is worth learning beyond the install command. Its official docs cover workspaces, catalogs, overrides, patches, deployment, and strict dependency resolution without treating monorepos as an afterthought.
Oğuzhan Kurum
@oguzhan · 64 days ago
Use the Turborepo docs to get task dependencies, caching, filtering, environment variables, and CI behavior right. The payoff is not just faster builds; it is a monorepo whose execution model the whole team can reason about.
turborepo.comOğuzhan Kurum
@oguzhan · 64 days ago
Drizzle is a strong fit when you want TypeScript inference without giving up the shape of SQL. Its overview explains the design, schema model, query APIs, migrations, and why the library stays close to the database.
Oğuzhan Kurum
@oguzhan · 64 days ago
NestJS is easiest to understand through its official docs: modules, providers, controllers, guards, pipes, testing, and deployment are presented as one architecture rather than disconnected recipes.
docs.nestjs.comOğuzhan Kurum
@oguzhan · 64 days ago
Use the official Next.js documentation before relying on a blog post that may describe an older router. The guides connect routing, rendering, caching, data fetching, deployment, and upgrades to the current framework behavior.