Software Development – Professional Development for BioPharma, LIMS & Healthcare IT
My approach: requirements engineering + software development (and, for smaller projects, project management where appropriate) in one person — I understand what needs to be built, AND how to implement it technically.
Core stack: C#/.NET Core, ASP.NET, Oracle, MSSQL, Azure Cloud, REST APIs, microservices.
Principles: clean code, testability, maintainability, documentation — especially important in regulated environments (GxP, CSV).
Software Development in the Context of Requirements Engineering & Project Management
Software development is not an isolated process . In successful projects, three disciplines work together seamlessly:
Requirements Engineer
As requirements engineering, I understand:
- What should be built (business requirements, use cases)
- Why it is being built (business value, stakeholder needs)
- For whom it is being built (user personas, workflows)
- Which constraints apply (governance, GxP, performance)
Developer
As a developer, I can:
- Assess technical feasibility early
- Suggest alternative solutions that are often simpler than initially expected
- Move directly from requirement to implementation — no “telephone game” effect
- Ensure traceability (code ↔ requirements ↔ tests)
Project Management
Ensures that it gets built:
- Timeline, milestones
- Resource planning
- Risk management
- Stakeholder communication
My Advantage
I can cover all three disciplines — which means:
- No “telephone game”: requirements do not get lost between RE → PM → Dev
- Early technical assessment: feasibility, effort, and risks are recognized immediately
- Traceability: code ↔ requirements ↔ tests — fully transparent
- Especially valuable in regulated environments: GxP, CSV, validation — no loss of information
The Result:
Software that actually does what it is supposed to do — because requirements are not only understood, but also implemented correctly from a technical perspective. Especially in regulated environments (LIMS, BioPharma, healthcare IT), this end-to-end responsibility is critical.
Technology Stack
Languages:
Frameworks:
Databases:
Cloud & Tools:
Testing:
Design Patterns:
LIMS Platforms:
Legacy (if relevant):
Core Technologies & Expertise
C# / .NET / .NET Core Primary
Experience: 2006–present (~20 years)
Versions: .NET 1.0 → .NET Framework 4.7.2 → .NET Core 2.1–8.0
Backend Development:
- ASP.NET Core: REST APIs, web services, middleware
- Microservices: Azure Functions, background services
- Windows Services: .NET Core worker services
- Integration Services: file processing, data transformation, ETL
- Real-time Processing: SignalR, WebSockets
Frontend/UI:
- Blazor: Server & WebAssembly
- Razor Pages: server-side rendering
- WPF/WinForms: desktop applications (legacy)
Tools & Frameworks:
- Entity Framework Core, Dapper (ORM)
- AutoMapper, FluentValidation
- Serilog, NLog (logging)
- Polly (resilience & fault handling)
Databases Expert
Oracle Database
Experience: 1997–present (~28 years)
- PL/SQL: stored procedures, functions, packages, triggers
- Advanced SQL: analytical functions, CTEs, XMLTABLE, JSON_TABLE
- Performance: execution plans, indexing, partitioning
- Integration: database links, external tables, Java bindings
Microsoft SQL Server
Experience: 1999–present (~26 years)
- T-SQL: stored procedures, functions, triggers, views
- Database Design: normalization, indexing, constraints
- Performance Tuning: query optimization, profiling
- Versions: SQL Server 7.0 → 2019
ORM & Data Access:
- Entity Framework Core
- Dapper (micro-ORM)
- ADO.NET (low-level, performance-critical scenarios)
Cloud & DevOps Azure
Azure Services:
- Azure IoT Hub: device-to-cloud messaging (QIAGEN project)
- Azure Event Hub: high-throughput event streaming
- Azure Functions: serverless microservices
- Azure Blob Storage: file storage, data lake
- Azure SQL Database: managed MSSQL
DevOps & CI/CD:
- Git: version control, branching strategies, code review
- GitHub: repositories, Actions (CI/CD), pull requests
- Azure DevOps: pipelines, artifacts, work items
- Docker: containerization, Docker Compose
Deployment & Automation:
- PowerShell scripting (automation, deployment)
- Azure CLI, ARM templates
- Continuous integration / continuous deployment
Web Technologies & JavaScript Node.js
Node.js (2014–present):
- Backend: Express.js, REST APIs, authentication (Passport.js)
- Reporting: HTML report generator (custom framework)
- Integration: Oracle DB (node-oracledb), file processing
- Document Generation: Microsoft Word DOCX generator
Frontend Libraries:
- jQuery / jQuery UI: DOM manipulation, AJAX
- Bootstrap: responsive UI
- DataTables: interactive tables
- D3.js, Plotly: data visualization
- FancyTree: hierarchical data
Oracle APEX (2016–2020):
- Low-code web application development
- Custom JavaScript integrations (D3.js, AnyChart, Oracle JET)
- PL/SQL backend, REST services
Development Principles & Best Practices
Clean Code
- SOLID principles
- DRY (Don't Repeat Yourself)
- KISS (Keep It Simple, Stupid)
- Readable, self-documenting code
- Meaningful naming conventions
Testing & Quality
- Unit testing (NUnit, xUnit)
- Integration testing
- Test-driven development (TDD)
- Code coverage (>80%)
- Mocking (Moq, Typemock)
Documentation
- Technical specifications
- API documentation (Swagger/OpenAPI)
- Code comments (XML documentation)
- README, architecture docs
- User manuals, SOPs
Agile Development
- Scrum framework (since 2008)
- Iterative development
- Sprint planning & reviews
- Continuous feedback
- Retrospectives
Version Control
- Git workflows (feature branches)
- Pull requests & code review
- Branching strategies (GitFlow)
- Merge conflict resolution
- Release management
Security & Compliance
- Input validation & sanitization
- Authentication & authorization
- Encryption (data at rest & in transit)
- OWASP Top 10
- GxP-compliant development