Vladislav Guzey

Set up metrics, logs, and traces for a service. Use when a mid-level developer needs basic observability coverage.

The English summary is being prepared. Showing the original description.

Create a plan to migrate platforms or runtimes. Use when a senior developer needs a phased migration approach.

The English summary is being prepared. Showing the original description.

Plan a zero-downtime migration for data or infrastructure. Use when a senior developer needs a safe migration strategy.

The English summary is being prepared. Showing the original description.

Guide collection and analysis of performance traces. Use when a mid-level developer needs to diagnose slowness.

The English summary is being prepared. Showing the original description.

Plan safe dependency upgrades with risk notes. Use when a mid-level developer is tasked with upgrading libraries.

The English summary is being prepared. Showing the original description.

Define engineering standards across teams. Use when a senior developer needs to align practices.

The English summary is being prepared. Showing the original description.

Review a pull request for correctness, regressions, and missing tests. Use when a mid-level developer needs structured review guidance.

The English summary is being prepared. Showing the original description.

Create a staged refactor plan for a module. Use when a mid-level developer needs a safe refactor path.

The English summary is being prepared. Showing the original description.

Prioritize roadmap initiatives with tradeoffs. Use when a senior developer needs help ranking projects.

The English summary is being prepared. Showing the original description.

Suggest small refactors that improve readability without changing behavior. Use when a junior developer asks to clean up code.

The English summary is being prepared. Showing the original description.

Assess and prioritize tech debt items. Use when a senior developer needs an investment plan for debt reduction.

The English summary is being prepared. Showing the original description.

Design safe queue consumers and retries. Use when a mid-level developer needs reliable background processing.

The English summary is being prepared. Showing the original description.

Review system costs and propose reductions. Use when a senior developer needs cost-saving recommendations.

The English summary is being prepared. Showing the original description.

Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.

The English summary is being prepared. Showing the original description.

Manage Buffer content via the GraphQL API. Use when creating, scheduling, editing, or deleting posts, saving ideas, reading scheduled queues, or pulling post analytics. Not for general API debugging.

The English summary is being prepared. Showing the original description.

Model domains and bounded contexts for complex systems. Use when a senior developer needs domain-driven design guidance.

The English summary is being prepared. Showing the original description.

Review database migrations for safety and rollback. Use when a mid-level developer needs validation of schema changes.

The English summary is being prepared. Showing the original description.

Draft release notes from changes and PRs. Use when a mid-level developer needs a structured changelog.

The English summary is being prepared. Showing the original description.

Explain a configuration file and its key options. Use when a junior developer is confused by a config file.

The English summary is being prepared. Showing the original description.

Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.

The English summary is being prepared. Showing the original description.

Summarize noisy logs into likely causes and next steps. Use when a junior developer needs help interpreting logs.

The English summary is being prepared. Showing the original description.

Design a multi-region architecture strategy. Use when a senior developer needs geo-redundant planning.

The English summary is being prepared. Showing the original description.

Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.

The English summary is being prepared. Showing the original description.

Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.

The English summary is being prepared. Showing the original description.