Blacksmith Developer

Job Title: Blacksmith Developer Location: Remote Duration: 6+ months MOI: Video Visa: Any independent visa (OPT, USC, GC, GC-EAD, H4-EAD) Description: • Need someone with 2 + years experience with Blacksmith • Good troubleshooting skills • Will support clients using this product • Company is a consulting firm • They have several clients using Blacksmith MultiValue / Pick fundamentals. Blacksmith is built on MultiValue technology and runs on environments like MVON, UniVerse, and UniData. A developer needs a solid grounding in Pick BASIC programming, the MultiValue data model (nested/multi-valued fields, dynamic arrays), and TCL (Terminal Control Language) for command-line operations. Without this foundation, the rest won't make sense. Understanding the Blacksmith framework itself. Blacksmith uses a visual, drag-and-drop "screen painter" approach to building entry screen programs from application objects. A developer needs to understand how Blacksmith's object model works, how screens are defined and configured, and how the framework handles data binding between UI elements and the underlying database. Database independence awareness. Each customer installation may use a different mix of databases — UniVerse, UniData, SQL Server, Oracle, or others — sometimes concurrently within the same application. The developer needs to understand which databases are in play at a given customer site and any nuances in how Blacksmith abstracts across them. UI mode familiarity. Blacksmith applications can run as either character-based (green screen) or graphical. The FUSION component handles graphical modernization of green-screen apps. A developer needs to know which mode(s) the customer is using and how FUSION works if the site is mid-modernization. Topology and architecture of the specific installation. Blacksmith is topology-independent — applications, users, and data can sit on workstations, data servers, or application servers. Each customer's deployment architecture will be different, so understanding how their particular environment is laid out is essential before making changes. The customer's application-specific code and business logic. Like any MultiValue shop, the bulk of the learning curve is often the customer's custom BASIC programs, dictionaries, data structures, and business rules that have been built up (sometimes over decades). Tooling. We offers MV# extensions for Visual Studio Code (including a developer IDE extension and a debugger), which could accelerate onboarding if the customer's environment supports them (the debugger depends on MVON#). In short, the core prerequisites are MultiValue/Pick development experience plus Blacksmith-specific framework knowledge. The customer-specific configuration (which databases, which topology, which UI mode, and their custom business logic) is what takes additional ramp-up time on-site.