Amey-Thakur
- 1k skills
- 0 followers
- 1 day ago last updated
- ▌ Security Engineer Role · amey-thakurOperate as a security engineer who reduces real risk through threat models, targeted reviews, scalable tooling, and incident duty. Use when a system's security posture is your responsibility and you must prevent and respond, not just audit.
- ▌ Landing Page Strategy · amey-thakurBuild landing pages with a clear message hierarchy, credible proof, and one decisive call to action, tested where it matters. Use when creating or fixing pages that must convert visitors.
- ▌ Conference Talks · amey-thakurGet talks accepted and deliver them well through audience-first proposals, narrative structure, and rehearsed, demo-safe delivery. Use when proposing or preparing a technical talk.
- ▌ Cpu Architecture · amey-thakurUnderstand caches, branches, and pipelines well enough to explain why equivalent code differs in speed by an order of magnitude. Use when optimising hot code or when performance does not match operation counts.
- ▌ Networking Stack · amey-thakurUnderstand the layers between a request and its response, so latency, connection failures, and timeouts can be attributed to the right layer. Use when network behaviour is unexplained or performance varies by geography.
- ▌ Data Pipeline Design · amey-thakurBuild data pipelines that rerun safely, backfill cleanly, and tolerate late data. Use when designing batch or streaming pipelines or fixing ones that need manual babysitting.
- ▌ Gradient Boosting Tuning · amey-thakurTune gradient-boosted trees (XGBoost, LightGBM, CatBoost) effectively: the parameters that matter and the order to tune them. Use when using gradient boosting on tabular data and wanting real gains from tuning.
- ▌ Probability Fundamentals · amey-thakurReason correctly about probability, base rates, conditional probability, and expected value, avoiding the common intuition traps. Use when interpreting likelihoods, test results, risks, or any uncertain quantity.
- ▌ Learning Rate Schedules · amey-thakurSet and vary the learning rate over training, since it is the hyperparameter that most determines whether a run converges. Use when loss diverges, plateaus early, or oscillates.
- ▌ Loss Function Selection · amey-thakurChoose a loss that matches the task and the metric you care about, and understand what each penalises. Use when a model optimises well and performs badly on the thing that matters.
- ▌ Distributed Locks · amey-thakurUse leases with fencing tokens for mutual exclusion across machines, or restructure to need no lock at all. Use when serializing distributed work or reviewing lock code that must not double-execute.
- ▌ Git History Hygiene · amey-thakurKeep git history atomic, bisectable, and readable with curated commits and disciplined force-push. Use when commits are messy, history is hard to navigate, or bisect and blame mislead.
- ▌ Github API Automation · amey-thakurScript repository operations reliably, respecting rate limits, pagination, and permissions. Use when managing repositories at scale or building tooling around the platform.
- ▌ Gpu Sharing Mig · amey-thakurShare one physical GPU across several small workloads using MIG, MPS, or time slicing, and pick the mode whose isolation matches the risk. Use when GPUs sit at low utilization because each job needs far less than a whole A100 or H100.
- ▌ Pseudo Localization · amey-thakurTest localisation readiness with generated pseudo-translations that expand, accent, and bracket text, before any real translation exists. Use when preparing a product for translation and wanting to find breakage early.
- ▌ JS Immutability · amey-thakurWork with immutable data in JavaScript through structural updates, readonly types, and freeze where it earns its cost. Use when managing shared or reactive state, or debugging bugs from unexpected mutation.
- ▌ Coding Agent Workflow · amey-thakurDirect and supervise a coding agent (Claude Code, Cursor, Antigravity) so it ships correct, verified work. Use when delegating engineering tasks to an AI agent and you want reliable results, not plausible-looking ones.
- ▌ Goal Driven Execution · amey-thakurPursue a high-level goal to completion autonomously: lock the done-condition, decompose, execute with verification, adapt, and know when to stop. Use when an agent is handed an outcome to achieve rather than a step to perform.
- ▌ Thumbnail Generation · amey-thakurProduce preview images for files of every type, consistently sized and generated without blocking the user. Use when a file list or gallery needs visual previews.
- ▌ Agent Oncall Triage · amey-thakurRun alert triage as agents that dedup the storm, rate severity by user impact, match a runbook, and draw a hard human-escalation line. Use when you want incoming alerts sorted and enriched by an agent team before they reach the on-call engineer.
- ▌ Agent Release Train · amey-thakurRun release agents that draft the changelog, scan risk, verify the candidate, and gate publish behind a go/no-go check. Use when cutting a release and you want the boring parts automated and the risky parts caught before ship.
- ▌ Agent Risk Register · amey-thakurMaintain a living register of business risks with agents that surface new ones, track mitigations, and force stale entries back to a decision. Use when risks are discussed in meetings and then forgotten until they happen.
- ▌ Agent Startup Squad · amey-thakurRun a lean startup team of agents (builder, marketer, analyst) through one disciplined weekly loop of ship, promote, and measure. Use when you want a small agent team to move a single product metric week over week.
- ▌ Agent Status Rollup · amey-thakurAggregate desk-level state into an honest company view where problems stay visible instead of averaging away. Use when everything is reported green and things are still going wrong.
- ▌ Digest Design · amey-thakurBatch many low-urgency events into one periodic summary that is worth opening, rather than sending each as it happens. Use when individual events are too frequent or too minor to interrupt.
- ▌ Maintainer Sustainability · amey-thakurKeep a project alive without burning out its maintainers, through scope limits, shared load, and honest signals about capacity. Use when maintenance feels like an obligation you cannot decline.
- ▌ Refunds And Disputes · amey-thakurHandle refunds, chargebacks, and disputes with evidence, deadlines, and a policy applied consistently. Use when building refund flows or responding to a chargeback.
- ▌ Subscription Billing · amey-thakurModel recurring plans, cycles, upgrades, and cancellations so what a customer is charged always matches what they agreed to. Use when building or changing recurring billing.
- ▌ Usage Based Metering · amey-thakurMeter consumption accurately enough to bill on it, with reconciliation, limits, and transparency the customer can verify. Use when charging by usage rather than a flat subscription.
- ▌ Serialization Performance · amey-thakurCut the CPU and bytes spent turning objects into wire or disk format by choosing the right format, reusing schemas and buffers, and avoiding copies. Use when serialization shows up in the profile, payloads are large, or encode/decode latency dominates a hot request path.
- ▌ Feature Sunsetting · amey-thakurRemove features with usage evidence, migration paths, and staged communication that preserves trust. Use when retiring product surface or making the case that something should die.
- ▌ User Story Writing · amey-thakurWrite user stories around outcomes with testable acceptance criteria, sliced thin enough to ship in days. Use when turning product intent into buildable work or fixing a backlog of vague tickets.
- ▌ Milestone Planning · amey-thakurBreak a project into milestones that each prove something, so progress is verifiable rather than asserted. Use when a project is long enough that the end is not visible from the start.
- ▌ Disaster Recovery Testing · amey-thakurVerify that backups restore and failover works by practising it, rather than trusting that the procedure would work. Use when recovery has never been rehearsed end to end.
- ▌ Rust Error Handling · amey-thakurDesign Rust error types with the thiserror/anyhow split, context chains, and a deliberate panic policy. Use when structuring errors in Rust libraries and applications.
- ▌ Agent Tool Permissions · amey-thakurConfigure what a coding agent may do without asking, balancing autonomy against the cost of an unwanted action. Use when setting up an agent's permissions for a project.
- ▌ Memory Forgetting Policy · amey-thakurDecide what an AI system forgets and when, through expiry, decay, and explicit deletion, so memory stays current and lawful. Use when memory accumulates indefinitely or a user asks to be forgotten.
- ▌ Integration Monitoring · amey-thakurObserve external dependencies so their degradation is visible before users report it and attributable when it happens. Use when your service depends on APIs you do not control.
- ▌ Integration Resilience · amey-thakurKeep your service healthy when a dependency is slow or failing, through timeouts, retries, circuit breakers, and fallbacks. Use when an external call sits in a request path.
- ▌ Event Driven Architecture · amey-thakurDesign event-driven systems with well-shaped events, schema contracts, and honest handling of choreography's costs. Use when decoupling services through events or debugging an event system nobody can reason about.
- ▌ Deprecation Program · amey-thakurRun a deprecation from usage telemetry through a hard sunset date, with migration tooling and staged comms, so a system retires without stranding its callers. Use when you own an API, endpoint, library, or service that must be turned off while other teams still depend on it.
- ▌ Error Budget Policy · amey-thakurOperate an error budget so reliability decisions follow a written policy instead of an argument: burn-rate alerts, feature freezes, and a clear escalation path. Use when a service has an SLO and you need to decide, without relitigating each incident, when to stop shipping features and fix reliability.
- ▌ Six Pager Narrative · amey-thakurWrite an Amazon six-pager, a narrative memo read in silence at the start of a meeting so a decision rests on reasoning rather than a presenter's charisma. Use when running an operating, strategy, or investment review that must reach a real decision.
- ▌ Developer Advocate Role · amey-thakurOperate as a developer relations (DevRel) engineer who closes the loop between external developers and the product team. Use when asked to run developer advocacy: gather feedback, produce technical content, grow a community, and feed evidence back to product and engineering.
- ▌ Incident Commander Role · amey-thakurOperate as an incident commander who owns the response to a live outage: severity, coordination, and communication, not the fix itself. Use when a production incident is active and someone must run the room instead of everyone debugging in parallel.
- ▌ Knowledge Base Design · amey-thakurBuild self-serve documentation that answers questions before they become tickets, organised by what people search for. Use when the same questions arrive repeatedly.
- ▌ Support Ticket Triage · amey-thakurSort incoming tickets by urgency and type so the ones that matter are answered first and nothing sits unread. Use when volume exceeds what can be handled in arrival order.
- ▌ Privacy Impact Assessment · amey-thakurAssess a high-risk processing activity before it ships, documenting risks, mitigations, and the decision. Use when processing sensitive data, profiling at scale, or introducing a novel use of personal data.
- ▌ Exploratory Data Analysis · amey-thakurExplore a new dataset systematically to understand its shape, quality, and signal before modeling. Use when you first get a dataset and need to know what is in it, what is wrong with it, and what is worth pursuing.
- ▌ Consistency Models · amey-thakurChoose the weakest consistency model each use case tolerates, from linearizable to eventual. Use when designing replicated data paths or explaining anomalies users report as bugs.
- ▌ Procedural Generation · amey-thakurGenerate game content with seeded determinism, layered noise, constraint solving, and validation that guarantees playability. Use when building procedural levels, worlds, or loot, or debugging generation that breaks.
- ▌ Git Hooks Automation · amey-thakurAutomate checks with git hooks that stay fast, with server-side enforcement and documented escape hatches. Use when setting up pre-commit checks or fixing hooks that developers routinely bypass.
- ▌ Monorepo Vs Polyrepo · amey-thakurDecide between one repository and many by tooling readiness, coupling, and team autonomy, and plan the migration. Use when structuring repositories for multiple projects or reconsidering a painful split.
- ▌ Repository Permissions · amey-thakurGrant repository and organisation access through teams and least privilege, and review it before it drifts. Use when managing access for a growing organisation or auditing who can do what.
- ▌ Locale Aware Sorting · amey-thakurSort and compare text using locale collation rather than byte order, so lists read correctly in every language. Use when displaying sorted names, searching case-insensitively, or matching user input.
- ▌ Translation Workflow · amey-thakurRun translation as a pipeline with catalogs, context, review, and continuous updates rather than a one-off handoff. Use when shipping in multiple languages on an ongoing release cadence.
- ▌ Tsconfig Mastery · amey-thakurConfigure tsconfig.json deliberately: the flags that matter, module and target settings, and build vs typecheck configs. Use when setting up TypeScript compilation or debugging confusing module and output errors.
- ▌ Dotnet Dependency Injection · amey-thakurUse .NET's built-in DI with correct lifetimes, the options pattern, and constructor injection free of service-locator drift. Use when wiring .NET services or debugging captive-dependency and disposal bugs.
- ▌ Skill Assessment · amey-thakurJudge someone's ability, including your own, through demonstrated performance rather than confidence or credentials. Use when hiring, mentoring, or deciding what to learn next.
- ▌ Hyperparameter Tuning · amey-thakurSearch hyperparameters with budgets, early stopping, and validation hygiene so gains are real, not overfit to the dev set. Use when tuning models or reviewing tuning claims.
- ▌ Train Test Discipline · amey-thakurSplit data before looking at it, respect time and groups, and quarantine the test set so scores mean something. Use when setting up ML evaluation or auditing why offline metrics did not survive production.
- ▌ Conversion Rate Optimization · amey-thakurImprove the proportion of visitors who take the desired action, through evidence about where they drop rather than opinions about design. Use when traffic is adequate and conversion is not.
- ▌ Media Storage Tiering · amey-thakurMatch storage class to access pattern so rarely read media costs less without becoming unavailable. Use when media storage cost grows faster than usage.
- ▌ Agent Analytics Desk · amey-thakurTurn business data into answered questions with agents that define the metric, pull it consistently, check it against a second source, and state what it does not prove. Use when numbers are quoted in meetings that nobody can reproduce.
- ▌ Agent Brand Guardian · amey-thakurKeep every outgoing artefact consistent in voice, claims, and terminology with agents that check against a written brand definition. Use when output comes from many sources and the product sounds like several different companies.
- ▌ Agent Chief Of Staff · amey-thakurRun the management layer above specialist desks: set the week's priorities, route work, chase what is stuck, and end every cycle with decisions and owners. Use when several agent desks exist but nothing coordinates them into finished work.
- ▌ Agent Meeting Runner · amey-thakurPrepare, run, and close meetings with agents so each one produces decisions and owned actions instead of discussion. Use when meetings consume time and nothing is decided or recorded.
- ▌ Agent Migration Crew · amey-thakurRun a team of migration agents that inventories the work, transforms each slice in isolation, verifies it, and merges under strict discipline. Use when a large mechanical change like a framework bump, an API rename, or a schema move spans many files and one agent would lose the thread or break main.
- ▌ Agent Sales Pipeline · amey-thakurStaff a pipeline with agents that research accounts, qualify leads against explicit criteria, draft outreach for human sending, and keep the CRM honest. Use when lead flow needs consistent handling and the pipeline record keeps rotting.
- ▌ Documentation For Adoption · amey-thakurWrite the docs that decide whether someone adopts a project: a truthful readme, a working quickstart, and answers to the first questions. Use when a project is capable but nobody gets past the first ten minutes.
- ▌ Customer Interviews · amey-thakurRun user interviews that surface past behavior instead of polite predictions, recruited and synthesized honestly. Use when gathering qualitative evidence for product decisions.
- ▌ Shell Portability · amey-thakurWrite shell that runs across POSIX sh, bash versions, and GNU/BSD userlands, or decide deliberately not to. Use when scripts must run on multiple platforms, containers, or CI images.
- ▌ Synonyms And Stemming · amey-thakurMatch words to their variants and equivalents without collapsing distinctions that matter. Use when searches miss obvious results, or when unrelated results appear because two words were merged.
- ▌ Zero Results Handling · amey-thakurTurn an empty result set into a useful next step instead of a dead end, and treat the query as a signal worth acting on. Use when searches return nothing and users leave.
- ▌ Spreadsheet Collaboration · amey-thakurShare workbooks so several people can work without overwriting each other or creating competing versions. Use when more than one person edits the same spreadsheet.
- ▌ Spreadsheet Data Cleaning · amey-thakurTurn messy imported data into a clean flat table, fixing types, whitespace, duplicates, and inconsistent categories. Use before any analysis on data that came from elsewhere.
- ▌ Agent Instruction Files · amey-thakurWrite the repository instruction file that coding agents read, so they follow project conventions without being told each session. Use when setting up a repository for Claude Code, Antigravity, Cursor, or any agent reading AGENTS.md.
- ▌ API Credential Rotation · amey-thakurStore, scope, and rotate integration credentials so a leak is survivable and rotation does not cause an outage. Use when managing keys for external services.
- ▌ Third Party Integration · amey-thakurIntegrate an external service so its failures, changes, and limits do not become your outages. Use when adding a dependency on an API you do not control.
- ▌ Engineering Manager Role · amey-thakurOperate as an engineering manager who grows people, protects delivery health, hires deliberately, and shields the team from noise. Use when you are accountable for a team's output and careers, not for writing the code yourself.
- ▌ Principal Architect Role · amey-thakurOperate as a principal architect who owns the boundaries between systems, curates the technology set, and spends veto power sparingly. Use when you must set architecture direction across teams and keep a platform coherent as it grows.
- ▌ Solutions Architect Role · amey-thakurOperate as a solutions architect who turns a customer's constraints into a defensible reference design and a path to production. Use when asked to scope a technical solution for a specific account, produce an architecture that fits real limits, and de-risk the build.
- ▌ Engineering Resume · amey-thakurWrite engineering resumes with quantified impact bullets, honest tailoring, and machine-readable formatting. Use when writing or reviewing a technical resume.
- ▌ Receiving Feedback · amey-thakurReceive feedback by listening past delivery, extracting the signal, and closing the loop with visible action. Use when getting reviews, criticism, or hard performance conversations.
- ▌ Salary Negotiation · amey-thakurNegotiate offers with market data, competing leverage, whole-package thinking, and a clear stopping point. Use when handling a job offer or a raise conversation.
- ▌ Customer Feedback Loop · amey-thakurTurn support conversations into product change through structured tagging, aggregation, and a route into the roadmap. Use when support hears the same complaints and nothing changes.
- ▌ Support Sla Management · amey-thakurSet, measure, and honour response and resolution commitments that reflect real capacity rather than aspiration. Use when promising response times to customers or in contracts.
- ▌ Incremental Processing · amey-thakurProcess only new and changed data with watermarks, merge strategies, and a full-refresh escape hatch. Use when full-table rebuilds get slow or costly and models must go incremental.
- ▌ Pipeline Orchestration · amey-thakurOrchestrate data DAGs with data-aware scheduling, bounded retries, and SLAs that page the right owner. Use when structuring workflows in an orchestrator or fixing 3am cron archaeology.
- ▌ Regularization Techniques · amey-thakurReduce overfitting with weight decay, dropout, augmentation, and early stopping, choosing by why the model is overfitting. Use when validation performance diverges from training performance.
- ▌ Delivery Guarantees · amey-thakurReason honestly about at-most-once, at-least-once, and effectively-once semantics end to end. Use when specifying messaging behavior or auditing where a pipeline can lose or duplicate data.
- ▌ Partition Tolerance · amey-thakurDecide per operation what happens during a network partition, and design degraded modes that fail safe. Use when planning multi-node or multi-region behavior under network failure.
- ▌ Game Loop Architecture · amey-thakurStructure game loops with fixed-timestep simulation, interpolated rendering, and spiral-of-death protection. Use when building a game loop or fixing physics that behaves differently across frame rates.
- ▌ Gpu Cost Planning · amey-thakurPlan GPU spend by comparing owned hardware, reserved cloud, and on-demand against real utilization and lead time, so you commit at the right break-even. Use when deciding whether to buy GPUs, reserve cloud capacity, or burst on-demand for a workload.
- ▌ Model Parallelism · amey-thakurSplit a model that will not fit on one GPU across devices with tensor, pipeline, and expert parallelism, choosing each split by its communication cost. Use when weights or activations exceed a single card and you must shard without stalling on the interconnect.
- ▌ Currency Localization · amey-thakurDisplay, store, and reason about money across currencies without rounding errors or implied conversions. Use when showing prices in more than one currency or storing monetary amounts.
- ▌ Text Expansion Layout · amey-thakurDesign interfaces that survive translated text growing or shrinking substantially, without truncation or broken layout. Use when building UI that will be translated, or fixing clipped text in another language.
- ▌ JS Async Patterns · amey-thakurCompose async JavaScript with promises and async/await correctly, propagating errors and cancelling with AbortController. Use when writing async code, running work concurrently, or debugging swallowed errors and unhandled rejections.
- ▌ JS Error Handling · amey-thakurHandle errors in JavaScript and TypeScript with proper Error subclasses, cause chains, and a policy for async and unhandled failures. Use when designing error handling or debugging lost stack traces and swallowed errors.
- ▌ Chess Improvement · amey-thakurImprove at chess through tactical pattern training, endgame fundamentals, and engine-assisted analysis of your own losses. Use when your rating has plateaued and playing more games is not helping.