Industries
Automotive aftermarket
The project is the application the stores and the warehouse already use.
Past work at Fisher Auto Parts, from June 2015 to February 2016, is the concrete example. A VB6 application had to work with a newer website. A Chromium bridge connected that client to .NET. Performance problems on the VB.NET site were traced through the calls the page actually made. An AngularJS and WebAPI application was the path for replacing the VB6 programs. That job ended in February 2016.
The same shape shows up wherever a counter system, a catalog, or a branch tool is older than the website it now has to feed. The consulting work is C#, ASP.NET, WebAPI, and the bridge.
Typical project shapes
The VB6 program that still takes orders
Keep it talking to the new site while a replacement is scoped. A cutover with no bridge is how a Saturday at the counter goes wrong.
A web front end with a finish line
AngularJS and WebAPI, or the stack the team already chose, aimed at the screens VB6 still owns.
The slow page, measured
Find the redundant calls before replacing the application that happens to host them.
Boundary
The engagement is the application project, and it ends with a handoff to the team that runs the stores.
If the system matters, start with a conversation.
A paragraph on the system, the constraint, and the timing is enough. Jon reads every note.