Skip to content
View yurii1exe's full-sized avatar
🍫
🍫

Block or report yurii1exe

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
yurii1exe/README.md
Yurii Shchehliuk, product-minded full-stack engineer, Chicago, open to work. I learn how the business works, then build the software it runs on. Illustration in an amber-haze cinematic style: a neural network glows like city lights over a brutalist skyline. How the work gets done, who does it, the cost of being wrong, the data it runs on and where it is going all fire into one core: software the business runs on. A lone figure stands below, facing it.

Yurii Shchehliuk · Senior Full-Stack Engineer

Seven years building software for businesses where mistakes are expensive: freight brokerages, hospitals, factory floors, online stores. In each one, the hard part was understanding how the work actually gets done, who it gets done by, and what breaks when the software gets it wrong. The code came after that.

LinkedIn · yshchehliuk@gmail.com · disit.tech

How I work

Start with the person doing the job. Before designing anything, I find out how the dispatcher, the operator or the clinician does the work today and where it hurts. Software that ignores that gets worked around.

Price the failure. Know what it costs when the system is wrong, a rejected invoice or a stale reading on a production line, and design for that case first.

Ship the smallest thing that pays for itself. Then grow it with real usage, not guesses.

Make what's there work together. Every business already runs on systems that were never meant to talk. Connecting them usually beats replacing them.


01 edi-x12-toolkit. Problem: trading partners reject files, and the rejection rarely says why, so support time goes into guessing. Decision: read the format the way the standard defines it, and explain every error in plain words. Outcome: problems surface before a partner sees them, and anyone can try it in a browser with nothing to install.

Built with C# (.NET Standard 2.0 and .NET 8), compiled to WebAssembly for the browser. No dependencies, MIT licence. ▶ Try it live

The playground reading two versions of the same partner file and pointing to the exact line that would get it rejected



02 freight-dispatch-board. Problem: every move a dispatcher makes owes the customer an update and billing a document. Decision: make the paperwork a side effect of the work, and check every document automatically. Outcome: no forgotten updates, no invoices that bounce, and one screen for the person doing the job.

Built with .NET 8 and Angular, with tests and CI.

Dispatch board: a new load arrives, the dispatcher moves it across a multi-stop route, and each step sends the customer its status update automatically



03 opc-ua-monitor. Problem: on a plant floor, an old number that looks live is worse than no number at all. Decision: stream live values, and say plainly when a connection drops and the data goes stale. Outcome: operators can trust what the screen tells them.

Built with .NET 8, OPC UA, SignalR and Angular.

Plant dashboard plotting live machine values, then marking them as stale the moment the connection drops



Also

fmcsa-carrier-check: brokers check a carrier before every load and usually pay a subscription for it. This puts the free government data on one page: authority, insurance, safety rating, inspections.

ECommerce-Restaurant: an online ordering system split into services, so the menu, basket and orders can each change without taking the others down.

Tools I reach for
Backend C# · .NET 8 / 6 · ASP.NET Core · EF Core · REST · SignalR · RabbitMQ / MassTransit · Node.js
Frontend Angular · RxJS · TypeScript · React · Next.js
Data SQL Server · T-SQL · PostgreSQL · MongoDB · Redis
Cloud & DevOps Azure (App Service, Functions, Event Hub, IoT Hub, Key Vault) · Docker · CI/CD · GitHub Actions
Integration EDI ANSI X12 · CargoWise · TMW · OPC UA · DICOM · HL7

Tell me how your business works. I'll tell you what to build, and what not to. Contact: yshchehliuk@gmail.com, linkedin.com/in/yurii1exe, disit.tech.

Open to senior full-time or contract roles, remote or in Chicago. Corp-to-corp through DIS IT LLC.

Pinned Loading

  1. ECommerce-Restaurant ECommerce-Restaurant Public

    .NET 6 microservices storefront - MassTransit/RabbitMQ order events, Redis basket, EF Core migrations, JWT across services, Angular 15, full Docker Compose stack

    C# 9 2

  2. Playbook Playbook Public

    .NET data pipeline: PuppeteerSharp scrapes a JavaScript-rendered results site into MongoDB, aggregation pipelines turn it into per-team season metrics.

    C# 1