Amey-Thakur
- 1k skills
- 0 followers
- 1 day ago last updated
- ▌ Devops Engineer Role · amey-thakurOperate as a DevOps engineer who owns the delivery pipeline, keeps environments identical, and makes every deploy reversible. Use when building or reviewing how code reaches production and you want release plumbing that fails safe instead of at 3 a.m.
- ▌ Growth Engineer Role · amey-thakurOperate as a growth engineer who moves a funnel metric through instrumented, fast experiments and refuses to win with dark patterns. Use when your job is to raise activation, retention, or conversion with measured changes, not guesses.
- ▌ Mobile Engineer Role · amey-thakurOperate as a mobile engineer who plans around release trains, a real device matrix, and app-store rules that a web engineer never faces. Use when building or reviewing an iOS or Android feature and you need mobile-specific release and compatibility discipline.
- ▌ Product Manager Role · amey-thakurOperate as a product manager who picks the right problem, writes the spec, makes the tradeoff calls, and owns the launch outcome. Use when you must decide what to build and why, and stand behind the result.
- ▌ Release Manager Role · amey-thakurOperate as a release manager who runs release trains, enforces cut criteria, and holds rollback authority. Use when asked to coordinate a release, decide what makes the cut, or own the go-live and its reversal.
- ▌ Market Sizing · amey-thakurEstimate how large an opportunity actually is, from the bottom up, and state the assumptions that drive the number. Use when evaluating a market, writing a plan, or challenging a large number in a deck.
- ▌ Developer Marketing · amey-thakurReach developers through docs, honest content, and community trust instead of ads they ignore. Use when marketing developer tools or building a devrel content engine.
- ▌ Status Updates · amey-thakurWrite status updates with progress, risk, and asks calibrated to the audience, honoring the no-surprises rule. Use when reporting project status upward or fixing updates nobody reads.
- ▌ API Surface Minimalism · amey-thakurKeep the public API small by defaulting to private visibility and retiring symbols through deprecation before deletion. Use when designing a module's exports or reviewing what a package exposes to callers.
- ▌ Virtual Memory · amey-thakurUnderstand address translation, paging, and the memory hierarchy well enough to explain swap thrashing, page faults, and why memory usage numbers disagree. Use when memory behaviour is confusing or a process is slower than its CPU usage suggests.
- ▌ Support Escalation · amey-thakurMove a ticket to engineering or management with the context needed to act, and set expectations with the customer while it moves. Use when a ticket cannot be resolved at the current level.
- ▌ Batch Vs Streaming · amey-thakurChoose batch or streaming from honest latency requirements and operate the complexity you actually need. Use when designing a data flow or reviewing whether a streaming system earns its cost.
- ▌ Warehouse Modeling · amey-thakurModel warehouse tables with explicit grain, conformed dimensions, and deliberate SCD handling. Use when designing analytics schemas or fixing double-counted metrics and unjoinable tables.
- ▌ Cross Border Transfers · amey-thakurKnow where personal data physically goes and keep transfers lawful when it crosses a border. Use when choosing a region, adding a vendor, or designing replication and backups.
- ▌ Vendor Data Processing · amey-thakurAssess and control what third-party services do with personal data you send them, before and after integration. Use when adding a vendor, SDK, or API that will receive user data.
- ▌ Overfitting Diagnosis · amey-thakurDistinguish overfitting from underfitting, data leakage, and distribution shift, since all four present as poor validation performance. Use when validation performance is worse than expected.
- ▌ Weight Initialization · amey-thakurInitialise parameters so signal and gradients propagate at usable scale from the first step. Use when a deep network fails to train from the start or diverges immediately.
- ▌ Leader Election · amey-thakurRun one active node with lease-based election, split-brain prevention, and clean handoff. Use when exactly one instance must do a job (scheduler, migrator, singleton consumer) across a fleet.
- ▌ Pull Request Size · amey-thakurKeep pull requests small through vertical slicing and stacking, because review quality and latency both collapse with size. Use when PRs are too big to review well or sit for days.
- ▌ Locale Formatting · amey-thakurFormat numbers, dates, currency, and units by locale using the platform formatter rather than string templates. Use when displaying any value whose written form differs between regions.
- ▌ JS Event Loop · amey-thakurReason about the JavaScript event loop, microtasks vs macrotasks, and why blocking it freezes everything. Use when debugging ordering surprises, UI jank, or code that runs in an unexpected sequence.
- ▌ Context Engineering · amey-thakurAssemble what goes into an LLM's context on each call: selecting, ordering, and formatting the right information. Use when deciding what to put in a prompt or debugging why a model ignores or misuses provided information.
- ▌ Conversation Design · amey-thakurDesign multi-turn conversational systems with state tracking, memory injection, topic handling, and repair. Use when building chat assistants or fixing bots that forget, drift, or trap users.
- ▌ Retrieval Reranking · amey-thakurImprove RAG answer quality by reranking retrieved candidates so the most relevant chunks reach the model. Use when a retrieval system returns roughly-right documents but the best ones are not on top, or answers miss available evidence.
- ▌ Ml Problem Framing · amey-thakurFrame ML problems around a decision, a measurable target, and honest error costs before touching models. Use when scoping an ML project or reviewing whether one should exist.
- ▌ Positioning And Messaging · amey-thakurDecide what you are, who for, and against what alternative, then say it in words customers use. Use when nobody can explain the product in one sentence or the same product is described differently everywhere.
- ▌ Metadata Stripping · amey-thakurRemove embedded metadata such as location, device, and author from user files before they are stored or shared. Use when users upload photographs or documents that others will see.
- ▌ Agent Growth Team · amey-thakurRun a team of growth agents that designs an experiment, builds the variant, analyzes the result, and passes an ethics gate before anything ships. Use when you want product changes tested rigorously instead of shipped on a hunch, with a guardrail against manipulative tactics.
- ▌ Agent Ops Command · amey-thakurRun the daily operating rhythm with agents that sweep every system each morning, surface what needs a decision, and keep nothing waiting silently. Use when running a business day to day and things fall through the cracks between desks.
- ▌ Agent Pm Eng Loop · amey-thakurPair a product-manager agent with engineer agents through spec, pushback, scope negotiation, and acceptance so the build matches intent. Use when an agent team must turn a fuzzy request into a shipped, accepted increment.
- ▌ Batching And Debouncing · amey-thakurCoalesce a flood of small operations into fewer larger ones with batch windows, debounce, or throttle, chosen by whether you need the last event or a steady rate. Use when high-frequency triggers each do expensive work: per-keystroke queries, per-event writes, per-scroll handlers.
- ▌ Policy As Code · amey-thakurExpress organisational rules as automated checks in the pipeline rather than as documents people are meant to follow. Use when standards exist on paper and are inconsistently applied.
- ▌ System Prompt Design · amey-thakurWrite the durable instructions that shape every turn, covering role, boundaries, and defaults without micromanaging each response. Use when configuring an assistant or agent that will handle many different requests.
- ▌ Offline Sync · amey-thakurLet clients work disconnected and reconcile changes on reconnect without losing edits or resurrecting deletions. Use when building an application that must work on an unreliable network.
- ▌ Scheduled Jobs · amey-thakurRun cron and timer jobs with overlap locks, jitter, missed-run policies, and monitoring for silent absence. Use when scheduling recurring automation or debugging jobs that overlap, pile up, or quietly stop.
- ▌ Security Incident Response · amey-thakurRun a security breach through containment, evidence preservation, and notification duties in the right order, under time pressure, without destroying the record you will need. Use when you suspect or confirm a compromise: leaked credentials, unauthorized access, malware, or exfiltrated data.
- ▌ Conditional Formatting · amey-thakurUse formatting rules to surface exceptions and patterns automatically, without turning the sheet into a colour chart. Use when readers need to spot outliers or status at a glance.
- ▌ Spreadsheet Automation · amey-thakurAutomate repetitive spreadsheet work with scripts, knowing when the task has outgrown a spreadsheet entirely. Use when the same manual steps are repeated on a schedule.
- ▌ Go Project Layout · amey-thakurOrganize Go packages by domain with internal boundaries, consumer-side interfaces, and structure that grows on demand. Use when starting a Go project or refactoring one into clearer packages.
- ▌ Systems Profiling · amey-thakurProfile native code with perf and flamegraphs, then read cache, syscall, and allocation behavior to find the real bottleneck. Use when optimizing systems software or explaining why fast code is slow.
- ▌ Knowledge Graph Memory · amey-thakurStore facts as entities and relationships when questions depend on connections rather than similarity. Use when retrieval must answer who relates to what rather than find similar text.
- ▌ Vendor Evaluation · amey-thakurEvaluate vendors against weighted criteria, a proof of concept that tests your real workload, and a clear-eyed accounting of exit costs before you sign. Use when choosing a paid tool or service you will depend on and a wrong pick is expensive to undo.
- ▌ War Room Protocol · amey-thakurRun a war room for a live incident with defined roles, a steady cadence, a decision log, and explicit stand-down criteria. Use when a high-severity outage or crisis needs coordinated response across teams and the improvised version is descending into chaos.
- ▌ Backend Engineer Role · amey-thakurOperate as a backend engineer who designs stable API contracts, guards data integrity, and ships services that are operable on day one. Use when building or reviewing a service, API, or data path and you want production-grade engineering discipline.
- ▌ Product Designer Role · amey-thakurOperate as a product designer who designs the whole flow, specs every state, defends the work in critique, and hands off at build fidelity. Use when designing a feature, running or joining a critique, or preparing a handoff to engineering.
- ▌ Support Engineer Role · amey-thakurOperate as a support engineer who triages by impact, reproduces before escalating, and turns recurring tickets into product fixes. Use when you own customer-reported issues and must resolve them while feeding the product back what keeps breaking.
- ▌ Technical Writer Role · amey-thakurOperate as a technical writer who owns the information architecture, runs docs through a two-gate review, and ships documentation with the feature it describes. Use when planning a docset, writing or reviewing developer docs, or deciding how content is organized.
- ▌ Unit Economics · amey-thakurWork out whether one customer or one transaction makes money, before scaling anything. Use when deciding to grow, raise prices, or cut costs, and when growth is not producing profit.
- ▌ Giving Feedback · amey-thakurDeliver feedback with situation-behavior-impact structure, timeliness, and care calibrated to stakes. Use when correcting course, recognizing work, or preparing a hard conversation.
- ▌ Change Data Capture · amey-thakurReplicate database changes via log-based CDC with correct snapshot handling, ordering, and schema-change survival. Use when streaming OLTP changes to warehouses, caches, or search without touching app code.
- ▌ Data Quality Checks · amey-thakurLayer freshness, volume, schema, and distribution checks with quarantine and alert discipline. Use when adding quality gates to pipelines or when consumers keep finding bad data first.
- ▌ Subject Access Requests · amey-thakurAnswer a request for a copy of someone's data completely, on time, and without exposing anyone else. Use when building an export path or responding to an access request.
- ▌ Consensus Basics · amey-thakurUnderstand what Raft and Paxos actually provide, quorum arithmetic, and when you need consensus at all. Use when deploying replicated coordination systems or deciding whether a problem truly requires consensus.
- ▌ Game Asset Pipeline · amey-thakurAutomate asset import, atlasing, compression, and hot reload so content flows from tools to game without hand steps. Use when building content pipelines or fixing bloated builds and stale assets.
- ▌ Game Input Handling · amey-thakurBuild input systems with action mapping, buffering, dead zones, and rebinding that feel responsive and fair. Use when wiring game controls or fixing input that feels laggy or eats presses.
- ▌ Multiplayer Netcode · amey-thakurBuild multiplayer with an authoritative server, client prediction, reconciliation, and lag compensation. Use when adding networking to a game or fixing rubber-banding and desync.
- ▌ Repository Structure · amey-thakurOrganise a repository so a newcomer finds what they need and automation has predictable paths. Use when starting a repository or when nobody can find anything in an existing one.
- ▌ Character Encoding · amey-thakurHandle Unicode end to end so text survives storage, transport, and display without mojibake or truncation mid-character. Use when text arrives corrupted, lengths behave oddly, or emoji break a field.
- ▌ NPM Publishing · amey-thakurPublish an npm package that installs and imports cleanly: correct exports map, dual formats, types, and semver. Use when releasing a library to npm or fixing a package consumers cannot import.
- ▌ Embeddings Selection · amey-thakurChoose embedding models and chunking by evaluating retrieval on your own corpus, not by leaderboard rank. Use when building semantic search or RAG and deciding how to embed and chunk.
- ▌ Experiment Tracking · amey-thakurRecord every training run's code, data, config, and results so any model is reproducible and comparisons are honest. Use when setting up ML experiment infrastructure or untangling which run produced the prod model.
- ▌ Feature Engineering · amey-thakurBuild features that are leakage-free, temporally correct, and reproducible between training and serving. Use when creating model inputs or auditing a suspiciously good offline score.
- ▌ Content Marketing Strategy · amey-thakurPlan content that reaches buyers at the moment they are looking, with a cadence you can sustain and a way to tell whether it worked. Use when publishing sporadically without knowing whether it helps.
- ▌ Agent Crisis Comms · amey-thakurPrepare public communication during an incident with agents that assemble facts, draft holding statements, and check for claims that cannot be supported, while a human speaks. Use when something has gone wrong publicly and the response must be fast and accurate.
- ▌ Agent Decision Log · amey-thakurRecord what was decided, by whom, on what basis, and when to revisit, so decisions are not relitigated or silently forgotten. Use when the same discussion recurs and nobody remembers why the current approach was chosen.
- ▌ Agent Finance Desk · amey-thakurRun a standing finance function with agents that reconcile transactions, track runway, flag anomalies, and prepare reporting for a human to approve. Use when the money side of a business needs steady attention rather than a quarterly scramble.
- ▌ Agent Goal Cascade · amey-thakurTranslate company objectives into desk-level goals and weekly work, keeping the line from a task to the objective visible. Use when teams are busy but nobody can say how the work serves the goal.
- ▌ Agent Hiring Panel · amey-thakurSimulate an interview panel as agents that design questions, score independently on anchored rubrics, and reconcile in a debrief. Use when you want to pressure-test a hiring loop, calibrate rubrics, or dry-run questions, not to score a real candidate.
- ▌ Agent Research Lab · amey-thakurRun a lab of researcher agents that search in parallel, verify sources independently, and synthesize a cited answer. Use when a question needs breadth of sources and every load-bearing claim must trace to evidence.
- ▌ Agent Support Desk · amey-thakurRun a team of support agents that triages each ticket, reproduces the problem, drafts a reply, and hands clean escalations to a human. Use when inbound support volume needs consistent handling and a person must approve every customer-facing reply before it goes out.
- ▌ Vulnerability Disclosure · amey-thakurReceive, triage, fix, and announce security reports on a coordinated timeline that protects users. Use when running a project that could have security issues, or when you receive a report.
- ▌ Payment Idempotency · amey-thakurMake payment operations safe to retry so a network timeout never charges a customer twice. Use when calling a payment API, processing webhooks, or building any money-moving endpoint.
- ▌ Payment Integration · amey-thakurIntegrate a payment provider so charges are authorised, confirmed, and recorded correctly even when the customer closes the tab. Use when adding checkout or moving to a new payment provider.
- ▌ Pci Scope Reduction · amey-thakurKeep card data out of your systems so compliance obligations stay minimal, and know what remains in scope when it cannot. Use when handling card payments or preparing for a compliance assessment.
- ▌ Algorithmic Optimization · amey-thakurReplace a hot algorithm with one of better complexity, a fitter data structure, or memoized results instead of micro-tuning the slow one. Use when a profiler points at a function whose cost is inherent to its approach, not to constant-factor waste.
- ▌ Performance Optimization · amey-thakurMake code measurably faster by profiling first and fixing the actual bottleneck. Use when something is slow, uses too much memory, or needs to handle more load.
- ▌ Service Catalog · amey-thakurMaintain an inventory of services with owners, dependencies, and operational metadata so questions about who owns what are answerable. Use when nobody can say who owns a service or what depends on it.
- ▌ Product Discovery · amey-thakurValidate problems before building solutions using evidence standards and opportunity mapping. Use when deciding what to build next or challenging a solution that arrived before its problem.
- ▌ Resource Planning · amey-thakurMatch people and capacity to project needs over time, accounting for partial allocation, ramp-up, and the cost of splitting attention. Use when planning who works on what across projects.
- ▌ Negative Instructions · amey-thakurTell a model what not to do in a way that works, by converting prohibitions into positive alternatives wherever possible. Use when a prompt lists things to avoid and the model keeps doing them.
- ▌ Output Format Control · amey-thakurGet output in exactly the structure downstream code expects, using schemas, examples, and validation rather than hope. Use when a model's output is parsed by a program rather than read by a person.
- ▌ Incident Severity Levels · amey-thakurClassify incidents consistently so the response, communication, and escalation match the impact. Use when incident response is either overwhelming or too slow.
- ▌ Service Level Objectives · amey-thakurDefine measurable reliability targets from the user's perspective and use the error budget to decide between shipping and stabilising. Use when reliability is debated without numbers.
- ▌ Bash Robustness · amey-thakurWrite bash that fails loudly, quotes correctly, cleans up after itself, and passes shellcheck. Use when writing shell scripts that automation or other people will depend on.
- ▌ Makefile Design · amey-thakurWrite Makefiles with honest dependencies, phony discipline, and self-documenting help, and know when make is the wrong tool. Use when standardizing project task-running or fixing rebuild bugs.
- ▌ Text Processing · amey-thakurChoose grep, sed, awk, or jq by job, prefer structured formats, and know when a one-liner should become a script. Use when slicing logs, transforming files, or wrangling command output.
- ▌ Autocomplete Design · amey-thakurSuggest queries as the user types, fast enough to feel instant and relevant enough to be worth reading. Use when adding a search box that should guide rather than merely accept input.
- ▌ Query Understanding · amey-thakurInterpret what a user meant before matching, through normalisation, intent detection, and entity extraction. Use when queries are short, ambiguous, or full of product-specific language.
- ▌ Spreadsheet Performance · amey-thakurDiagnose and fix slow spreadsheets by reducing volatile formulas, whole-column references, and unnecessary recalculation. Use when a workbook takes seconds to respond to an edit.
- ▌ Unsafe Code Review · amey-thakurAudit unsafe blocks by verifying documented invariants, minimizing surface, and testing under sanitizers and Miri. Use when reviewing unsafe Rust, C/C++ interop shims, or any code that bypasses language safety.
- ▌ Agent Test Generation · amey-thakurUse an agent to write tests that check behaviour rather than restate the implementation, and verify they can actually fail. Use when adding coverage to existing code.
- ▌ Multi Model Workflows · amey-thakurUse more than one model or tool deliberately, playing to their differences rather than switching at random. Use when one model is consistently weak on part of your workflow.
- ▌ Vector Store Operations · amey-thakurRun a vector index in production, covering dimensions, filtering, updates, and reindexing when the embedding model changes. Use when semantic search is live and must stay correct as data and models change.
- ▌ Integration Migration · amey-thakurMove between API versions or providers without downtime, using parallel running and staged cutover. Use when a provider deprecates a version or you are replacing a service.
- ▌ Microservices Boundaries · amey-thakurSplit services along business capabilities with clear data ownership, avoiding the distributed monolith. Use when decomposing a system into services or diagnosing services that must always deploy together.
- ▌ Dogfooding Program · amey-thakurRun an internal dogfooding program with staged cohorts, one feedback intake, and numeric exit criteria to general availability. Use when a pre-release product needs real internal use to surface bugs and adoption risk before it ships to customers.
- ▌ Hiring Loop Design · amey-thakurDesign a hiring loop where each interview gathers distinct signal against an anchored rubric and the debrief resists groupthink. Use when standing up or fixing an interview panel and you want a decision based on evidence, not overlapping impressions.
- ▌ Quarterly Planning · amey-thakurRun quarterly planning with honest capacity, negotiated cross-team dependencies, and an explicit cut line that names what will not get done. Use when a team commits to a quarter of work and needs the plan to survive contact with reality.
- ▌ Frontend Engineer Role · amey-thakurOperate as a frontend engineer who defends UX quality, enforces performance budgets, and partners with design instead of just closing tickets. Use when building or reviewing a user-facing web feature and you want an engineer's operating discipline, not raw code.
- ▌ Platform Engineer Role · amey-thakurOperate as a platform engineer who builds golden paths for internal developers and earns adoption on merit. Use when asked to design an internal developer platform, pave a common workflow, or prove a platform is being adopted.