PHP · Yii2 · Laravel
Business systems, APIs, reusable components and legacy updates. Earlier work at SourceOne also includes Laravel.
My technical skills connected to my work: languages, apps, data, cloud and delivery. Explore the skills and the projects that use them.
From application rules to services and integrations.
Business systems, APIs, reusable components and legacy updates. Earlier work at SourceOne also includes Laravel.
APIs, concurrent services, WebSocket and clear domain, application and infrastructure boundaries.
APIs, data connectors, automation and local tools. My role in Onerom is as a contributor.
APIs and business systems. InspectApp includes a dedicated report generation component. My contribution varies by project.
Web interfaces, integration contracts and apps with clear component responsibilities.
Flutter apps, testable rules and device features.
Native integrations in FretUp and ToOn: Android/iOS features, audio and widgets in FretUp; CallKit/PushKit and native calls in ToOn.
Earlier Java development at CI&T. This is work history, with no claim of a current Java portfolio project.
Physics, gameplay, presentation and offline storage in Jeepão, with assembly boundaries.
Messaging integration documented in naGestão, with a Node.js/Express adapter separate from the PHP system.
Products built for their screens and real use.
Feature-based interfaces, navigation, states and API integration.
Field app and interfaces connected to Inspect operations.
Mobile apps with local storage, permissions, sync and platform checks based on each product.
Responsive layouts, keyboard navigation, clear states and real use needs.
Vue application updates at SourceOne, alongside Laravel, React and C# APIs.
Real-time communication in ToOn and event transport in the FootGrid backend, with separate data storage.
Application databases, external sources and message transport have different roles.
Storage and queries in PHP systems, AIceberg runtime, FootGrid and Inspect Lead. Also an external data source for AInalise.
Business systems, queries, integrations and latency and concurrency diagnosis.
Platform storage and persistence contracts, data modelling, queries and access isolation.
Business data sources in AInalise, connector compatibility and permissions. Earlier work at TCEMG also includes Oracle.
Cache and operations in ToOn, Redis Streams transport in AIceberg and cache/queue infrastructure in Lobapp. Each case separates existing work from planned features.
Local database in Printora and mobile apps, with offline sync where used. ToOn uses SQLCipher for encrypted local storage.
Data modelling, indexes, queries, SQL scripts and storage diagnosis. Backup and restore need their own checks.
Infrastructure, connectivity and operations for each product.
Hosting and operation of AInalise in the AWS environment documented by the project.
AIceberg operations and delivery through a self-hosted GitHub Actions runner on OCI.
Azure SQL, Microsoft Fabric and Entra integration in AInalise; Azure AI connectors in AIceberg.
Agents and diagnostics for local network data sources; local device operation in Printora.
Linux, VPS and dedicated server operations: services, permissions, releases and diagnosis.
Repeatable environments, web proxy, services and workers, with configuration separate from code.
ToOn hosting with a Go API in Docker and PostgreSQL/Redis services defined in its Blueprint. Environment settings and health checks support operations.
Private ToOn media stored in S3-compatible R2; Inspect Lead web access through Cloudflare Tunnel. These services have separate roles.
Firebase and mobile notification integrations in Flutter apps. These links indicate app use, without claiming backend hosting or Firestore.
From a Git change to operations, with clear checks and rollback.
Validation and release workflows, self-hosted and hosted runners, branches and tags based on each repository’s rules.
Builds tied to versions and commits, environment checks, smoke tests and rollback steps.
Private configuration outside public assets, restricted permissions and separate local, staging and production environments.
Safe logs, request or job context and failure diagnosis. Release and real operation have separate checks.
Checks, packaging and operation scripts with validation and clear failures.
Decisions that connect requirements, code and evidence.
Decisions that separate UI, rules, data and infrastructure for each project stage. This includes planned architecture for products still being defined.
Rule and integration tests, API contracts and checks of affected flows. Local checks do not replace production or device acceptance.
A reusable base of context, requirements, decisions, work packages and evidence for AI-assisted engineering.
No skills found. Try another term.