Sharon Yurievich Shalmiev

Sole proprietor

Sharon Yurievich Shalmiev

I design and ship IT solutions within your constraints: integrations, APIs, web services, and UIs. I factor in maintainability, security, and scaling where it genuinely matches the problem—not as buzzwords, but as engineering trade-offs.

Expertise

What I can help with

From prototype to production: clear milestones, measurable outcomes, and straightforward communication along the way.

  • Software development

    Services and utilities for Linux/Windows, automation scripts, background jobs and workers. I structure data access, error handling, and configuration via environment variables. When it helps—Docker, and lightweight CI for linters and tests.

  • Websites

    Static generation or light SSR when you need server-side dynamics. Semantic markup, responsive layouts, baseline accessibility thinking, meta tags and structured data when SEO matters. LCP/CLS work: fonts, images, critical CSS, CDN caching.

  • Web applications

    Multi-page or SPA architectures depending on UX and SEO goals. Authentication (sessions, JWT/OAuth—scenario-dependent), roles and permissions, validated forms, file uploads, real-time only when justified. APIs for mobile or partner systems.

  • Support & consulting

    Legacy triage: where to simplify safely, where a module rewrite pays off. Profiling bottlenecks, database migration plans, architecture reviews. I can help draft specs for a team or vendors and sanity-check technical delivery.

How I work

As a sole proprietor, you talk directly to the person who implements and owns the outcome. Up front we align on goals, timeline/budget constraints, and a definition of done—so we don’t debate intent at the finish line.

I pick the stack for the problem, not for hype: sometimes static sites and server-rendered forms are enough; sometimes you need a separate backend and a message queue. Clear boundaries between components, predictable deploys, and handover-friendly code matter.

Documentation where it reduces risk: API descriptions (OpenAPI/Swagger or equivalent), README for local setup, short ADRs when a decision is contentious. Tests focused on critical business logic and regressions—not coverage percentages for their own sake.

Selected experience

Skolkovo

Smart bus stops

Led software development for intelligent bus stop solutions at the Skolkovo Innovation Center: scoping and breakdown, architecture, coordination between device firmware and service-side logic, and delivery quality within agreed timelines.

HoReCa

Restaurant CRM, Moscow

Built CRM systems for Moscow restaurants: guest and reservation management, floor plans and staff shifts, orders and kitchen coordination, reporting for management. Designed for multi-location groups, role-based access, and integrations with third-party services where the business needs them.

Web3

Blockchain & distributed systems

Hands-on with blockchain-oriented work: smart contracts, chain interactions, wallet and backend integrations; I factor in key custody and threat models, gas and throughput limits, and practical differences between L1/L2. Happy to discuss anything from dApp prototypes to internal tooling on distributed ledgers.

Technical depth

What guides technical decisions

These are guiding principles, not a universal checklist—scope is always agreed per project.

Architecture & code quality

  • Layering UI, domain logic, and infrastructure (DB, external APIs) so changes don’t ripple unpredictably across the repo.
  • Principles like SOLID and YAGNI as judgment tools, not dogma—complexity when there’s a real need.
  • Refactoring in small steps; feature flags when you can’t freeze the product for a big rewrite.

APIs & integrations

  • REST or RPC shaped by how clients consume the service; GraphQL when the data model truly benefits.
  • Predictable error codes, consistent problem payloads (e.g. problem+json / shared envelope), idempotency for payments and critical operations.
  • Rate limits, timeouts, and client-side retries; API versioning or an explicit deprecation policy.

Data & performance

  • Relational databases (PostgreSQL and peers) where integrity and reporting matter; indexes and query plans before “it got slow”.
  • Avoiding classic pitfalls (N+1, unbounded queries), caching with a clear invalidation story.
  • Schema migrations as code, backups, and a understandable rollback story for bad releases.

Security & operations

  • Secrets only in external stores or environment variables, least privilege for service accounts, HTTPS everywhere in production.
  • Baseline OWASP thinking for the web: injection, XSS, CSRF, object-level authorization—scoped to your threat model.
  • Structured logs, health/readiness probes, metrics where observability matters; a simple, repeatable deploy process.

HoReCa · Moscow

House-roasted coffee & tea for restaurants

100% Arabica with beans from Ethiopia, Brazil, and Rwanda—roasted to match your bar. Tea: 200+ SKUs from everyday classics to rare lots. Supply and curation for your beverage program.

Details in the Retail section.

Web · sample work

Business landing templates

Four animated one-pagers: real estate, café, B2B platform, and fashion atelier. Typography, layout, and micro-interactions.

The Web section has interactive previews.

Routers · VPN in hardware

Cudy WR3000 & TR3000

Wi‑Fi 6 with built-in VPN clients (WireGuard, OpenVPN, and more)—route your home network through your own server. Handy for cloud tools and AI apps via your infrastructure.

Hardware section—full specs and ordering.

Connect

Contact

Describe the problem or attach a spec link—I’ll reply with clarifying questions and a rough estimate.