yanko-belov
@yanko-belov
Public Skills
error-responses
by yanko-belov
Use when returning errors from APIs. Use when exposing internal errors. Use when error responses lack structure.
interface-segregation-principle
by yanko-belov
Use when designing interfaces. Use when implementing interfaces with methods you don't need. Use when forced to implement throw/no-op for interface methods.
fail-fast
by yanko-belov
Use when handling errors. Use when tempted to catch and swallow exceptions. Use when returning default values to hide failures.
composition-over-inheritance
by yanko-belov
Use when tempted to use class inheritance. Use when creating class hierarchies. Use when subclass needs only some parent behavior.
dont-repeat-yourself
by yanko-belov
Use when writing similar code in multiple places. Use when copy-pasting code. Use when making the same change in multiple locations.
encapsulation
by yanko-belov
Use when exposing internal state. Use when making fields public for convenience. Use when external code modifies object internals.
open-closed-principle
by yanko-belov
Use when adding new functionality to existing code. Use when tempted to add if/else or switch branches. Use when extending behavior of existing classes.
law-of-demeter
by yanko-belov
Use when accessing nested object properties. Use when chaining method calls. Use when reaching through objects to get data.
n-plus-one-prevention
by yanko-belov
Use when fetching related data in loops. Use when seeing multiple queries for one request. Use when database is slow on list endpoints.
lazy-loading
by yanko-belov
Use when loading all data upfront. Use when initial page load is slow. Use when fetching data that might not be needed.
error-boundaries
by yanko-belov
Use when deciding where to catch errors. Use when errors propagate too far or not far enough. Use when designing component/service isolation.
you-aint-gonna-need-it
by yanko-belov
Use when tempted to add features "for later". Use when building "production-ready" systems before needed. Use when adding flexibility that isn't required yet.
test-driven-development
by yanko-belov
Use when implementing any new feature or function. Use when asked to "add tests later". Use when writing code before tests.
api-versioning
by yanko-belov
Use when designing or modifying APIs. Use when adding breaking changes. Use when clients depend on API stability.
secrets-handling
by yanko-belov
Use when working with API keys, passwords, or credentials. Use when asked to hardcode secrets. Use when secrets might leak.
caching
by yanko-belov
Use when same data is fetched repeatedly. Use when database queries are slow. Use when implementing caching without invalidation strategy.
dependency-inversion-principle
by yanko-belov
Use when a class creates its own dependencies. Use when instantiating concrete implementations inside a class. Use when told to avoid dependency injection for simplicity.
input-validation
by yanko-belov
Use when accepting user input. Use when handling request data. Use when trusting external data without validation.
idempotency
by yanko-belov
Use when creating mutation endpoints. Use when trusting frontend to prevent duplicates. Use when payments or critical operations can be repeated.
separation-of-concerns
by yanko-belov
Use when component does too many things. Use when mixing data fetching, logic, and presentation. Use when code is hard to test.
immutability
by yanko-belov
Use when modifying objects or arrays. Use when tempted to mutate function parameters. Use when state changes cause unexpected bugs.
auth-patterns
by yanko-belov
Use when implementing authentication. Use when storing passwords. Use when asked to store credentials insecurely.
aaa-pattern
by yanko-belov
Use when writing tests. Use when test structure is unclear. Use when arrange/act/assert phases are mixed.
liskov-substitution-principle
by yanko-belov
Use when creating subclasses or implementing interfaces. Use when tempted to override methods with exceptions or no-ops. Use when inheritance hierarchy feels wrong.