Amey-Thakur
- 1k skills
- 0 followers
- 1 day ago last updated
- ▌ Schema Evolution · amey-thakurEvolve data schemas with compatibility rules, producer contracts, and registries so downstream never breaks silently. Use when changing event or table schemas that other teams consume.
- ▌ Leaderboard Strategy · amey-thakurTrust your cross-validation over the public leaderboard, avoid overfitting it, and select final submissions wisely. Use in the endgame of a Kaggle competition, where rank is won or lost by validation discipline.
- ▌ Time Series Analysis · amey-thakurAnalyze and forecast time-ordered data respecting trend, seasonality, autocorrelation, and the arrow of time. Use when working with data indexed by time: metrics, sales, sensor readings, or any forecast.
- ▌ Binary Search Debugging · amey-thakurHalve the search space repeatedly across code, data, time, and configuration until a single change isolates the failure. Use when the fault could live anywhere across a large surface and reading it all in order is too slow.
- ▌ Metrics Instrumentation · amey-thakurInstrument code with counters, gauges, and histograms picked to answer a specific operational question. Use when you need to watch a system's behavior over time and want the right instrument instead of a wall of unreadable numbers.
- ▌ Attention Mechanism · amey-thakurUnderstand what attention computes and why its cost grows quadratically with sequence length, to reason about context limits and efficiency work. Use when working with transformer models or evaluating long-context claims.
- ▌ Optimizer Selection · amey-thakurChoose an optimiser and its hyperparameters based on the problem rather than habit, and know what each actually does. Use when training is unstable, slow to converge, or generalising poorly.
- ▌ Spreadsheet Modeling · amey-thakurBuild spreadsheet models that are auditable and hard to break, separating inputs, calculations, and outputs. Use when modelling finances, forecasts, or scenarios.
- ▌ Firmware Ota Updates · amey-thakurShip over-the-air firmware with A/B slots, signed images, power-loss resilience, and staged fleet rollout. Use when building device update systems or reviewing one before it bricks a fleet.
- ▌ Sensor Data Handling · amey-thakurTurn raw sensor readings into trustworthy data with correct sampling, filtering, calibration, and timestamped batching. Use when building sensor pipelines or debugging noisy, aliased, or drifting measurements.
- ▌ Game Performance · amey-thakurHold frame budgets through per-frame profiling, object pooling, draw-call batching, and allocation discipline. Use when a game stutters, drops frames, or needs optimization triage.
- ▌ Branch Strategy · amey-thakurChoose a branching model, default to trunk-based with short-lived branches, and set protection rules. Use when establishing team git workflow or fixing long-lived-branch merge pain.
- ▌ Commit Messages · amey-thakurWrite commit messages that explain change and intent so history stays useful. Use when committing work or asked to draft a commit message for a diff.
- ▌ Merge Vs Rebase · amey-thakurChoose merge or rebase by the history you want, use interactive rebase safely, and set a team policy. Use when deciding integration mechanics or resolving debates about git history style.
- ▌ Release Tagging · amey-thakurTag releases with semantic versions and signed tags, generate changelogs, and trigger builds from tags. Use when setting up a release process or fixing ambiguous, unsigned, or manual releases.
- ▌ Branch Protection · amey-thakurConfigure rules that stop unreviewed or broken code reaching the default branch, without making routine work impossible. Use when setting up a shared repository or after an incident traced to a direct push.
- ▌ Locale Fallback · amey-thakurDefine what a user sees when a string, a locale, or a region is not available, so gaps degrade predictably instead of showing keys or blanks. Use when supporting partial translations or regional variants.
- ▌ Spring Boot Discipline · amey-thakurKeep Spring Boot apps explicit with constructor injection, typed configuration, test slices, and restrained magic. Use when building or reviewing Spring Boot services that must stay debuggable.
- ▌ LLM Observability · amey-thakurInstrument LLM applications with request tracing, token accounting, quality signals, and feedback loops. Use when running LLM features in production or debugging why quality or cost moved.
- ▌ Structured Output · amey-thakurGet valid structured data from LLMs with schema-constrained generation, boundary validation, and repair loops. Use when LLM output feeds code, databases, or downstream systems.
- ▌ Cross Validation · amey-thakurPick CV schemes that respect time and grouping, nest them for tuning, and read the variance, not just the mean. Use when data is too small for a single split or when validating tuning claims.
- ▌ Drift Monitoring · amey-thakurDetect input, prediction, and performance drift with reference windows and act through retrain or rollback triggers. Use when operating models in production or diagnosing gradual quality decay.
- ▌ Model Deployment · amey-thakurShip models through batch, online, or edge patterns with shadow testing, gated rollouts, and rollback. Use when moving a model to production or designing the serving architecture.
- ▌ Model Evaluation · amey-thakurEvaluate models with cost-aligned metrics, slice analysis, calibration, and uncertainty, not a single accuracy number. Use when choosing evaluation metrics or judging whether a model is fit to ship.
- ▌ Audio Processing · amey-thakurNormalise, compress, and prepare audio for reliable playback and transcription, handling levels and formats consistently. Use when accepting recorded audio or producing spoken content.
- ▌ Document Parsing · amey-thakurExtract text and structure from PDFs, office documents, and scans reliably enough to search, index, or summarise. Use when users upload documents whose contents the product must understand.
- ▌ Format Selection · amey-thakurChoose media formats and codecs by compatibility, quality, and licensing, with fallbacks for what the client cannot play. Use when deciding what to store and deliver.
- ▌ Agent Data Team · amey-thakurRun a data team as agents that build the pipeline, gate on quality checks, run the analysis, and independently audit every headline metric. Use when you want a number produced by a coordinated agent team rather than one agent's unverified query.
- ▌ Forking And Vendoring · amey-thakurDecide between patching upstream, forking, and vendoring a dependency, and carry the ongoing cost knowingly. Use when a dependency needs a change you cannot get merged, or is unmaintained.
- ▌ Open Source Licensing · amey-thakurChoose a licence, comply with the licences you depend on, and keep attribution correct as a project grows. Use when publishing a project, adding a dependency, or answering whether a licence permits your use.
- ▌ Supply Chain Security · amey-thakurProtect a project and its users from compromised dependencies, publishing credentials, and build pipelines. Use when publishing packages or auditing what your build actually trusts.
- ▌ Compression Tradeoffs · amey-thakurChoose a compression codec and level by weighing size reduction against CPU cost, and place compression where the bytes are actually scarce. Use when deciding whether and how to compress payloads, logs, or stored data, or when compression is burning CPU for little gain.
- ▌ Ab Test Design · amey-thakurDesign product experiments with real hypotheses, honest sample-size math, guardrails, and peeking discipline. Use when validating a change by experiment or reviewing a test before believing its result.
- ▌ Product Launch · amey-thakurLaunch features through tiered rollouts, a readiness checklist, coordinated comms, and a post-launch review. Use when shipping something users will notice or coordinating a cross-team release moment.
- ▌ Prompt Constraints · amey-thakurExpress limits on length, scope, style, and behaviour so they are followed rather than politely ignored. Use when a model consistently exceeds bounds or drifts outside the task.
- ▌ Failure Mode Analysis · amey-thakurEnumerate how a system can fail and what each failure does, before building the mitigations. Use when designing a critical system or reviewing one that has surprised you.
- ▌ Reliability Tradeoffs · amey-thakurDecide how much reliability to buy, given that each additional nine costs disproportionately more than the last. Use when reliability investment is being decided without reference to its cost.
- ▌ Experiment Design Basics · amey-thakurDesign experiments with controls, randomization, confound awareness, and pre-registered analysis. Use when testing a hypothesis empirically and needing the result to actually mean something.
- ▌ Relevance Tuning · amey-thakurImprove ranking with a judged evaluation set and measured changes rather than intuition. Use when search feels wrong and every proposed fix is someone's opinion.
- ▌ Search Analytics · amey-thakurInstrument search so queries, clicks, and abandonment tell you what to fix. Use when improving relevance without evidence, or when nobody can say whether search works.
- ▌ C Memory Safety · amey-thakurWrite C with explicit ownership conventions, bounds discipline, and sanitizers wired into every test run. Use when writing or reviewing C code, or hunting memory corruption.
- ▌ Visual Regression Testing · amey-thakurCatch unintended UI changes by diffing rendered screenshots against approved baselines with tuned thresholds and flake control. Use when protecting a component or page from visual drift across code changes.
- ▌ Accessibility Review · amey-thakurAudit a UI for real accessibility, keyboard-first, with concrete failures and fixes rather than checkbox compliance. Use when reviewing or building any user interface.
- ▌ Agent Cost Control · amey-thakurKeep agent usage within budget through context discipline, model selection, and caching, without degrading results. Use when agent costs are rising or long sessions are expensive.
- ▌ Memory Consolidation · amey-thakurPeriodically merge, deduplicate, and abstract accumulated memories so recall stays fast and coherent as volume grows. Use when a memory store has grown large and retrieval returns redundant or conflicting entries.
- ▌ Architecture Diagrams · amey-thakurDraw architecture diagrams at consistent C4-style levels, as code, kept honest and fit to the audience. Use when documenting a system's structure or when existing diagrams mislead more than they help.
- ▌ Canary Analysis · amey-thakurJudge a canary release against a concurrent baseline using pre-set metric gates, automatic rollback, and statistically honest windows. Use when a deploy is rolling out to a slice of production traffic and you must decide pass, hold, or revert.
- ▌ Design Critique · amey-thakurRun a design critique with a clear presenter contract, feedback rules that attack the work not the person, and captured decisions. Use when a designer brings work in progress to a group for structured feedback rather than approval.
- ▌ Data Scientist Role · amey-thakurOperate as a product data scientist who frames falsifiable hypotheses, analyzes experiments, and reports results without flattering the launch. Use when asked to design an A/B test, read out an experiment, or turn a metric question into a decision.
- ▌ Community Building · amey-thakurGrow product and open-source communities through seeded value, working moderation, and contributor ladders. Use when starting a community or reviving one that went quiet.
- ▌ Circular Dependencies · amey-thakurFind dependency cycles between modules and break them with layering, interface extraction, or dependency inversion. Use when imports form a loop that blocks compilation, isolated testing, or clear reasoning about load order.
- ▌ Cyclomatic Complexity · amey-thakurMeasure a function's branching complexity and reduce it so the logic stays testable. Use when a function has many paths, deep nesting, or a long if or switch chain.
- ▌ Defensive Programming · amey-thakurValidate untrusted data once at the boundary, then trust invariants inside and fail loudly if they ever break. Use when writing entry points, constructors, or any code that must not proceed on bad state.
- ▌ Feature Flags Hygiene · amey-thakurShip code behind flags without accumulating flag rot, through disciplined naming, expiry, and cleanup sweeps. Use when adding a feature flag or auditing the flags already live in a codebase.
- ▌ Immutability Defaults · amey-thakurMake immutability the default so aliasing bugs turn into compile errors or no-ops instead of action at a distance. Use when designing data structures, state updates, or any value shared across threads or call sites.
- ▌ Premature Abstraction · amey-thakurResist extracting shared code until a third real use reveals the true axis of variation. Use when tempted to add a helper, base class, config object, or generic layer on one or two examples.
- ▌ Community Support · amey-thakurRun a public forum where users help each other, with seeding, moderation, and staff presence that keeps answers accurate. Use when support volume exceeds staffing and questions are broadly shareable.
- ▌ Proactive Support · amey-thakurReach customers before they contact you, when telemetry or a known issue means they are about to have a problem. Use when failures are detectable before the customer notices or writes in.
- ▌ Support Analytics · amey-thakurMeasure support with metrics that reflect customer outcomes rather than agent activity, and use them to reduce ticket volume. Use when support is measured by throughput and quality is drifting.
- ▌ Data Partitioning · amey-thakurPartition datasets by pruning-friendly keys with healthy file sizes and scheduled compaction. Use when laying out lake or warehouse tables, or fixing slow scans and small-file explosions.
- ▌ Correlation Causation · amey-thakurTell correlation from causation and avoid the confounding, selection, and reverse-causation traps. Use when data shows a relationship and someone is about to claim one thing causes another.
- ▌ Statistical Inference · amey-thakurDraw honest conclusions from samples using hypothesis tests, confidence intervals, and significance read correctly. Use when deciding whether an effect is real, comparing groups, or reporting uncertainty.
- ▌ Training Loop Design · amey-thakurStructure a training loop with correct ordering, evaluation, checkpointing, and logging so runs are debuggable and resumable. Use when writing or reviewing training code.
- ▌ Newsletter Production · amey-thakurProduce a recurring newsletter with a sustainable format, a clear reason to open, and rendering that survives email clients. Use when publishing regularly to a subscribed audience.
- ▌ Event Sourcing · amey-thakurPersist state as an append-only event log with projections and snapshots, and know when the pattern is overkill. Use when audit history is a first-class requirement or evaluating event sourcing against CRUD.
- ▌ Game Save Systems · amey-thakurBuild save systems with versioned formats, corruption resistance, and autosave that never loses real progress. Use when designing game persistence or debugging broken saves after updates.
- ▌ Release Automation · amey-thakurAutomate tagging, building, and publishing releases so shipping is repeatable and the artefacts match the tag. Use when releases are manual, inconsistent, or occasionally wrong.
- ▌ Repository Hygiene · amey-thakurKeep a repository free of stale branches, dead files, oversized objects, and abandoned configuration. Use when a repository has grown cluttered or slow to clone.
- ▌ Vllm Serving · amey-thakurDeploy an LLM on vLLM with continuous batching, deliberate VRAM planning, and multi-model hosting that never overcommits the card. Use when serving on vLLM and deciding memory fraction, context length, tensor parallel size, and how many models share a GPU.
- ▌ TS API Types · amey-thakurType the boundaries of a TypeScript codebase: public API surfaces, branded types, and runtime validation of untyped input. Use when designing types others consume, or when external data enters your program.
- ▌ Prompt Engineering · amey-thakurBuild prompts that get accurate, reliably-shaped output from any LLM, choosing the right technique for the task. Use when writing, improving, or debugging a prompt.
- ▌ Ml Error Analysis · amey-thakurReview model errors by hand, discover failing slices, and decide whether data or model fixes pay more. Use when a model underperforms and you need to know why before spending compute.
- ▌ MCP Multi Server Orchestration · amey-thakurRun an agent across several MCP servers without name collisions, tool overload, or ambiguity about which server owns an action. Use when one agent connects to more than a few servers.
- ▌ Resumable Uploads · amey-thakurLet large uploads survive network interruption by chunking and resuming from the last confirmed part. Use when files are large enough that a failed upload is a real cost to the user.
- ▌ Video Transcoding · amey-thakurConvert uploaded video into the renditions needed for reliable playback across devices and bandwidths. Use when accepting user video or delivering video that must play everywhere.
- ▌ Agent Arch Board · amey-thakurRun an architecture board of agents where one proposes a design, several review it independently and blind, and a chair synthesizes a binding decision. Use when a design choice matters enough that one agent's opinion will not do and you want independent scrutiny before committing.
- ▌ Agent Docs Guild · amey-thakurRun a team of documentation agents that finds the gaps, drafts the pages, gets them reviewed against the code, and sweeps for staleness on a schedule. Use when a codebase has outrun its docs and you need both new coverage and a way to stop pages from rotting.
- ▌ Agent Legal Desk · amey-thakurUse agents to triage contracts and policies, extract obligations, flag unusual terms, and prepare a lawyer's review rather than replace it. Use when routine agreements pile up and nothing is tracked after signature.
- ▌ Agent Map Reduce · amey-thakurSplit a large task across parallel agents that each handle one slice, then merge their outputs deliberately. Use when the work exceeds one context window or would take too long serially.
- ▌ Contributor Onboarding · amey-thakurLower the cost of a first contribution with a working setup, a clear scope, and a fast review so people come back. Use when a project wants contributors and gets drive-by patches or none.
- ▌ Pagination Performance · amey-thakurPaginate large result sets so page cost stays constant by using keyset (cursor) pagination instead of OFFSET, with a stable, encoded cursor. Use when deep pages get slow, an infinite scroll drifts or duplicates rows, or OFFSET grows with page depth.
- ▌ Product Metrics · amey-thakurChoose a north star with input metrics you can move, guardrails you must not break, and defenses against vanity. Use when defining product measurement or auditing a dashboard full of numbers nobody acts on.
- ▌ Project Closure · amey-thakurEnd a project deliberately, with handover, documentation, and a decision about what happens to what was built. Use when a project reaches its goal or is being stopped.
- ▌ Project Kickoff · amey-thakurStart a project with shared understanding of goal, roles, and working agreements, so early ambiguity does not become late rework. Use at the start of any multi-person project.
- ▌ Project Scoping · amey-thakurDefine what a project includes, excludes, and depends on before work starts, so scope disagreements surface early. Use when starting a project or when a project keeps growing.
- ▌ First Principles Thinking · amey-thakurReason from fundamental truths by excavating assumptions and rebuilding from constraints, knowing when analogy is faster. Use when stuck in a solution space defined by convention or challenging an inherited assumption.
- ▌ CLI UX Design · amey-thakurDesign command-line interfaces with predictable flags, honest exit codes, machine-readable modes, and helpful failure text. Use when building CLI tools people other than the author will run.
- ▌ Command Injection Defense · amey-thakurRun external programs without ever building a shell string from untrusted input, using argument arrays that bypass the shell entirely. Use when a program shells out to another binary, especially with any value that came from a user, a file, or the network.
- ▌ Data Validation Rules · amey-thakurConstrain what can be entered into a spreadsheet so errors are prevented at input rather than found in analysis. Use when a spreadsheet is filled in by people.
- ▌ Screen Reader Testing · amey-thakurTest with real screen readers, verifying announcements, live regions, and navigation, not just automated checks. Use when validating accessibility of UI that automated tools cannot fully assess.
- ▌ Agent Context Setup · amey-thakurGive a coding agent the right files and background at the start of a task, so it works from the real system rather than from assumption. Use when starting a non-trivial task with an agent.
- ▌ Subagent Delegation · amey-thakurSplit work across subagents so each has a focused context, and combine their results deliberately. Use when a task is too large for one context or has independent parallel parts.
- ▌ Long Term User Memory · amey-thakurPersist facts about a user across sessions with provenance, correction, and expiry, so an assistant improves rather than accumulating stale assumptions. Use when an assistant should remember a user between conversations.
- ▌ Polling Vs Webhooks · amey-thakurChoose between pulling changes on a schedule and receiving pushed events, based on latency needs, reliability, and control. Use when deciding how to learn about changes in an external system.
- ▌ Rate Limit Handling · amey-thakurStay within a provider's limits and respond correctly when you exceed them, without hammering or stalling. Use when calling any API at volume.
- ▌ Webhook Consumption · amey-thakurReceive webhooks reliably, verifying authenticity and handling duplicates, ordering, and retries. Use when a provider pushes events to your service.
- ▌ Hexagonal Architecture · amey-thakurIsolate domain logic behind ports it owns while frameworks, databases, and transports live in adapters that plug into those ports. Use when business rules keep getting entangled with the web framework or database and you want the core testable and swappable in isolation.
- ▌ Service Mesh Tradeoffs · amey-thakurJudge whether a service mesh's east-west traffic features justify its operational complexity, versus a library approach. Use when evaluating a service mesh or reconsidering one that added more pain than value.
- ▌ Perf Calibration · amey-thakurRun a performance calibration meeting so ratings across a group rest on comparable evidence and a consistent bar, not one manager's advocacy. Use when managers are finalizing performance ratings for a team or org and you need consistency and bias control before results are delivered.
- ▌ Cloud Architect Role · amey-thakurOperate as a cloud architect who lays the landing zone, governs cost, and sequences migration for an organization. Use when asked to stand up a cloud foundation, put guardrails and cost controls in place, or plan how workloads move to the cloud.