feat: refine portfolio content, contact, and supporting media
This commit is contained in:
@@ -96,6 +96,18 @@
|
||||
"license": "All rights reserved",
|
||||
"attribution": "Original AI-assisted soundtrack produced by Luca Pîslaru with ACE-Step 1.5"
|
||||
},
|
||||
{
|
||||
"id": "contact-avatar",
|
||||
"fileName": "project-contact-avatar.webp",
|
||||
"sha256": "42f014f90f6d5cb12cf7eecd8819a8b4eb1c3a7fc6c703c12681e9f21bd8b7fc",
|
||||
"mediaType": "image/webp",
|
||||
"width": 264,
|
||||
"height": 284,
|
||||
"durationMs": null,
|
||||
"rightsHolder": "Luca Pîslaru",
|
||||
"license": "All rights reserved",
|
||||
"attribution": "Luca Pîslaru"
|
||||
},
|
||||
{
|
||||
"id": "currency-converter-interface",
|
||||
"fileName": "project-currency-converter.webp",
|
||||
@@ -108,6 +120,18 @@
|
||||
"license": "All rights reserved",
|
||||
"attribution": "Luca Pîslaru"
|
||||
},
|
||||
{
|
||||
"id": "healthcare-platform-interface",
|
||||
"fileName": "project-healthcare-interface.webp",
|
||||
"sha256": "9a8b10be64c3461b6a16d4fb0b45db30cb0014c5356fea82bf05c23ae3818ca1",
|
||||
"mediaType": "image/webp",
|
||||
"width": 1280,
|
||||
"height": 478,
|
||||
"durationMs": null,
|
||||
"rightsHolder": "Luca Pîslaru",
|
||||
"license": "All rights reserved",
|
||||
"attribution": "Luca Pîslaru"
|
||||
},
|
||||
{
|
||||
"id": "medication-mobile-data-settings",
|
||||
"fileName": "project-medication-data-settings.webp",
|
||||
@@ -168,6 +192,42 @@
|
||||
"license": "All rights reserved",
|
||||
"attribution": "Luca Pîslaru"
|
||||
},
|
||||
{
|
||||
"id": "private-game-loop-poster",
|
||||
"fileName": "project-private-game-loop-poster.webp",
|
||||
"sha256": "0c23f90028a7338cd0fddc4bf4fca885d6085f89b170a22a8e4a6384ec041835",
|
||||
"mediaType": "image/webp",
|
||||
"width": 960,
|
||||
"height": 540,
|
||||
"durationMs": null,
|
||||
"rightsHolder": "Luca Pîslaru",
|
||||
"license": "All rights reserved",
|
||||
"attribution": "Luca Pîslaru"
|
||||
},
|
||||
{
|
||||
"id": "private-game-loop-mp4",
|
||||
"fileName": "project-private-game-loop.mp4",
|
||||
"sha256": "30fc75ffbbf1c1fc048ed70cd744051c5a642b1b642847d242ffcb16c3d20a59",
|
||||
"mediaType": "video/mp4",
|
||||
"width": 960,
|
||||
"height": 540,
|
||||
"durationMs": 5000,
|
||||
"rightsHolder": "Luca Pîslaru",
|
||||
"license": "All rights reserved",
|
||||
"attribution": "Luca Pîslaru"
|
||||
},
|
||||
{
|
||||
"id": "private-game-loop",
|
||||
"fileName": "project-private-game-loop.webm",
|
||||
"sha256": "8e4455cc1849a9d5e24c49c2d40b574dc5a50a876da4e861867bcedf7888b78e",
|
||||
"mediaType": "video/webm",
|
||||
"width": 960,
|
||||
"height": 540,
|
||||
"durationMs": 5000,
|
||||
"rightsHolder": "Luca Pîslaru",
|
||||
"license": "All rights reserved",
|
||||
"attribution": "Luca Pîslaru"
|
||||
},
|
||||
{
|
||||
"id": "social-preview-nightdrive",
|
||||
"fileName": "project-social-preview.webp",
|
||||
|
||||
@@ -1,6 +1,9 @@
|
||||
{
|
||||
"schema": "portfolio-asset-recipes/v1",
|
||||
"assets": [
|
||||
{ "id": "contact-avatar", "kind": "image", "output": "project-contact-avatar.webp", "maxWidth": 264, "rightsHolder": "Luca Pîslaru", "license": "All rights reserved", "attribution": "Luca Pîslaru" },
|
||||
{ "id": "healthcare-platform-interface", "kind": "image", "output": "project-healthcare-interface.webp", "maxWidth": 1280, "rightsHolder": "Luca Pîslaru", "license": "All rights reserved", "attribution": "Luca Pîslaru" },
|
||||
{ "id": "private-game-loop", "kind": "video", "output": "project-private-game-loop.webm", "maxWidth": 960, "startSeconds": 3, "durationSeconds": 5, "rightsHolder": "Luca Pîslaru", "license": "All rights reserved", "attribution": "Luca Pîslaru" },
|
||||
{ "id": "medication-mobile-logs", "kind": "image", "output": "project-medication-logs.webp", "maxWidth": 720, "rightsHolder": "Luca Pîslaru", "license": "All rights reserved", "attribution": "Luca Pîslaru" },
|
||||
{ "id": "medication-mobile-data-settings", "kind": "image", "output": "project-medication-data-settings.webp", "maxWidth": 720, "rightsHolder": "Luca Pîslaru", "license": "All rights reserved", "attribution": "Luca Pîslaru" },
|
||||
{ "id": "medication-mobile-notification-settings", "kind": "image", "output": "project-medication-notification-settings.webp", "maxWidth": 720, "rightsHolder": "Luca Pîslaru", "license": "All rights reserved", "attribution": "Luca Pîslaru" },
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
"role": "System Administrator & Full-Stack Developer",
|
||||
"valueProposition": "I build full-stack software and operate the Linux systems behind it, from offline-first applications to access-controlled self-hosted services and careful data migrations.",
|
||||
"location": { "city": "Bucharest", "country": "Romania", "countryCode": "RO" },
|
||||
"availability": "Based in Bucharest and open to on-site, hybrid, or remote roles locally, as well as international remote opportunities."
|
||||
"availability": "I’m based in Bucharest and open to local on-site, hybrid, and remote roles, as well as international remote opportunities."
|
||||
},
|
||||
"navigation": [
|
||||
{ "id": "start", "label": "Start" },
|
||||
@@ -32,10 +32,10 @@
|
||||
"dates": "August 2025-Present",
|
||||
"location": "Bucharest, Romania",
|
||||
"highlights": [
|
||||
"Built the theatre group's first owned web presence, replacing a social-media-only discovery path with an indexable website and direct contact options.",
|
||||
"Developed a custom Vue frontend and a headless WordPress publishing workflow that lets an editor publish news and promotional content without changing code.",
|
||||
"Configured role-separated CMS access and restricted administrative routes and endpoints while keeping exact access rules private.",
|
||||
"Manage the domain, cPanel hosting, DNS/TLS configuration, custom .htaccess behavior, and controlled Git/SSH deployments with verification and rollback."
|
||||
"I built the theatre group’s first website, giving visitors a place to find performances, news, and contact details beyond social media.",
|
||||
"I developed a custom Vue frontend and connected it to headless WordPress, so an editor can publish news and promotional content without changing code.",
|
||||
"I configured separate administrator and editor roles and restricted access to administrative routes and endpoints.",
|
||||
"I manage the domain and hosting, configure DNS and TLS, and deploy releases through Git and SSH with a verification and rollback process."
|
||||
]
|
||||
},
|
||||
{
|
||||
@@ -45,8 +45,8 @@
|
||||
"dates": "June 2025-August 2025",
|
||||
"location": "Bucharest, Romania",
|
||||
"highlights": [
|
||||
"Contributed to eco-innovation work within the INOVATIV 2030 program.",
|
||||
"Developed and presented sustainable-technology business models."
|
||||
"I contributed to eco-innovation work within the INOVATIV 2030 program.",
|
||||
"I developed and presented business models for sustainable technologies."
|
||||
]
|
||||
},
|
||||
{
|
||||
@@ -56,58 +56,58 @@
|
||||
"dates": "June 2025-August 2025",
|
||||
"location": "Bucharest, Romania",
|
||||
"highlights": [
|
||||
"Processed and analyzed datasets using SPSS and Microsoft Excel.",
|
||||
"Prepared quantitative reports supporting business-development decisions."
|
||||
"I processed and analyzed datasets using SPSS and Microsoft Excel.",
|
||||
"I prepared quantitative reports to support business-development decisions."
|
||||
]
|
||||
}
|
||||
],
|
||||
"systemsOperations": {
|
||||
"id": "professional-systems-operations",
|
||||
"title": "Professional systems operations",
|
||||
"summary": "Application delivery and hosting work with explicit boundaries between public content, authenticated administration, controlled releases, and recovery.",
|
||||
"summary": "I look after both application delivery and hosting, from the editing workflow to access controls, releases, and recovery.",
|
||||
"evidence": [
|
||||
"Public Vue frontend backed by a role-separated headless WordPress editing workflow.",
|
||||
"Private source control followed by a deliberate SSH deployment, post-release verification, and Git-based rollback path.",
|
||||
"Domain, DNS, TLS, cPanel, and restricted-route administration performed alongside application development."
|
||||
"I give editors a publishing workflow while keeping administration separate from the public website.",
|
||||
"I use version control to prepare releases, verify deployments, and roll back changes when needed.",
|
||||
"I maintain the domain, hosting, certificates, and access rules alongside the application."
|
||||
]
|
||||
},
|
||||
"infrastructure": {
|
||||
"id": "self-hosted-platform-lifecycle",
|
||||
"title": "Secure self-hosted platform and lifecycle",
|
||||
"summary": "A self-hosted Linux environment operated as a long-term systems practice: traffic enters through a controlled edge, selected services receive an additional identity boundary, changes are staged deliberately, and important data has local and offsite recovery paths.",
|
||||
"summary": "I run a self-hosted Linux environment that I use every day. I manage how services are reached, who can access them, how they’re updated, and how their data can be recovered.",
|
||||
"bands": [
|
||||
{
|
||||
"id": "ingress-and-tls",
|
||||
"title": "Ingress and TLS",
|
||||
"summary": "Route services through Nginx, manage DNS and certificate lifecycle, and use Fail2Ban at exposed entry points."
|
||||
"summary": "I configure reverse proxies, DNS, and TLS to make services reachable through controlled, encrypted entry points."
|
||||
},
|
||||
{
|
||||
"id": "identity-and-access",
|
||||
"title": "Identity and access",
|
||||
"summary": "Place selected services behind Authelia and constrain administrative, filesystem, and container access without publishing the underlying policy."
|
||||
"summary": "I manage authentication and permissions, adding access controls around services and limiting administrative access."
|
||||
},
|
||||
{
|
||||
"id": "service-lifecycle",
|
||||
"title": "Service lifecycle",
|
||||
"summary": "Deploy and update services with Docker Compose, including a full platform migration from a Raspberry Pi to a dedicated Linux server."
|
||||
"summary": "I deploy and update containerized services, manage configuration, and migrate workloads when the platform needs to change."
|
||||
},
|
||||
{
|
||||
"id": "operations-and-recovery",
|
||||
"title": "Operations and recovery",
|
||||
"summary": "Use Btrfs storage, a pre-upgrade backup script, rsync-based copies, and an offsite backup for important data."
|
||||
}
|
||||
"id": "operations-and-recovery",
|
||||
"title": "Operations and recovery",
|
||||
"summary": "I prepare backups before major upgrades and keep local and offsite copies of important data."
|
||||
}
|
||||
],
|
||||
"featuredOperation": {
|
||||
"title": "Migrating a stateful Nextcloud service",
|
||||
"context": "The existing standalone deployment contained much more than files: contacts, calendars, tasks, and collaboration data all had to survive a move to Nextcloud All-in-One.",
|
||||
"context": "I moved my daily-use Nextcloud deployment to All-in-One. Alongside files, I needed to preserve contacts, calendars, tasks, and collaboration data.",
|
||||
"actions": [
|
||||
"Aligned application versions and updated installed applications before migration.",
|
||||
"Backed up the source deployment and prepared rollback checkpoints.",
|
||||
"Converted the existing MySQL database to PostgreSQL before the All-in-One migration.",
|
||||
"Exported and imported application state, transferred the data directory, corrected ownership and permissions, and preserved required instance configuration.",
|
||||
"Validated access to the expected files and services before relying on the new deployment."
|
||||
"I aligned application versions and updated installed apps before the move.",
|
||||
"I backed up the existing deployment and prepared rollback checkpoints.",
|
||||
"I converted the MySQL database to PostgreSQL before migrating to All-in-One.",
|
||||
"I transferred application state and files, corrected ownership and permissions, and preserved the instance configuration.",
|
||||
"I checked access to files and services before switching to the new deployment."
|
||||
],
|
||||
"outcome": "The migration completed without data loss. The All-in-One deployment has remained Luca's active Nextcloud instance for roughly a year, including storage, synchronization, contacts, calendars, tasks, and Nextcloud Talk."
|
||||
"outcome": "I completed the migration without data loss and have continued using the same instance for roughly a year—for file sync, contacts, calendars, tasks, and Nextcloud Talk."
|
||||
}
|
||||
},
|
||||
"projects": {
|
||||
@@ -117,17 +117,17 @@
|
||||
"title": "Private self-hosted medication tracker",
|
||||
"visibility": "private",
|
||||
"maturity": "active",
|
||||
"summary": "A solo-built, self-hosted medication-tracking system with an offline-first Flutter client, TypeScript API, PostgreSQL database, and Vue administration interface.",
|
||||
"problem": "A private medication routine needed dependable offline tracking, reminders, history, and synchronization without turning personal data into a public product.",
|
||||
"contribution": "Independently designed, implemented, deployed, and operated the complete mobile app, API, administration interface, database, synchronization model, and self-hosted environment.",
|
||||
"summary": "I built a self-hosted medication tracker from scratch, with an offline-first Flutter app, a TypeScript API, PostgreSQL, and a Vue administration interface.",
|
||||
"problem": "I wanted tracking, reminders, and history that would work offline and synchronize with a server I control.",
|
||||
"contribution": "I designed, built, deployed, and operated the complete system: mobile app, API, administration interface, database, and synchronization model.",
|
||||
"technicalDecisions": [
|
||||
"Use Flutter, Riverpod, and Drift/SQLite so the mobile workflow remains useful offline and can queue changes before pulling server updates.",
|
||||
"Use Fastify, TypeScript, Drizzle, and PostgreSQL for the API and synchronized data model, alongside a Vue administration interface.",
|
||||
"Apply authentication, refresh-token, TOTP, backup-code, biometric-lock, and database access-boundary mechanisms while continuing to harden the system through tests and audit findings.",
|
||||
"Run the containerized service behind Nginx/TLS and an additional Authelia access layer.",
|
||||
"Support schedules, as-needed entries, stock tracking, dose history, reminders, background sync, exports, analytics, an Android widget, and English/Romanian localization."
|
||||
"I used Flutter, Riverpod, and Drift/SQLite to keep the app useful offline, queue local changes, and pull server updates when a connection is available.",
|
||||
"I built the API with Fastify, TypeScript, Drizzle, and PostgreSQL, alongside a Vue administration interface.",
|
||||
"I added authentication, token renewal, two-factor authentication, recovery codes, biometric locking, and database access controls, then used tests and audits to identify further improvements.",
|
||||
"I deployed the containerized service behind Nginx and TLS, with an additional Authelia access layer.",
|
||||
"I added schedules, as-needed entries, stock tracking, history, reminders, background sync, exports, analytics, an Android widget, and English/Romanian localization."
|
||||
],
|
||||
"outcome": "The system has supported Luca's private medication tracking consistently for several months. Real use exposed Android reminder failures; investigation restored dependable delivery, and current work is replacing the remaining recurring behavior with occurrence-specific reconciliation to address duplicate and stale reminders. The project works for its current private use but is not presented as production-ready.",
|
||||
"outcome": "I’ve used the system privately for several months. When Android reminders arrived inconsistently, I investigated the scheduling process and improved delivery. I’m now moving toward native alarms and reminders scheduled per occurrence to address duplicate and stale notifications. It works for my current use, with further work needed before a wider release.",
|
||||
"assetIds": [
|
||||
"medication-mobile-logs",
|
||||
"medication-mobile-data-settings",
|
||||
@@ -138,9 +138,9 @@
|
||||
{
|
||||
"kind": "image",
|
||||
"assetId": "medication-mobile-logs",
|
||||
"alt": "Medication activity screen using an unmistakably fictional demo profile.",
|
||||
"caption": "Daily activity and history in a fictional demo state.",
|
||||
"longDescription": "The mobile view groups scheduled entries and their recorded status without exposing real medication information."
|
||||
"alt": "Medication activity screen with a fictional demo profile.",
|
||||
"caption": "Daily activity and history, shown with demo data.",
|
||||
"longDescription": "Scheduled entries and their recorded status are grouped in a single activity view."
|
||||
},
|
||||
{
|
||||
"kind": "image",
|
||||
@@ -163,16 +163,16 @@
|
||||
"title": "Footy Tracker",
|
||||
"visibility": "public",
|
||||
"maturity": "active",
|
||||
"summary": "A two-person university computer-vision project that processed previously unseen football footage and generated an annotated output video.",
|
||||
"problem": "Build a time-constrained demonstration that could identify football players, referees, and the ball in match footage and explore jersey-number recognition.",
|
||||
"contribution": "Led the project's data and machine-learning work: dataset acquisition and conversion, YOLO configuration and detector training, jersey-classifier design, experimentation, checkpointing, evaluation, and demo integration. A collaborator created the initial repository structure and video-processing pipeline.",
|
||||
"summary": "I led the data and machine-learning work on a two-person university project that detects players and the ball in football footage and produces annotated video.",
|
||||
"problem": "We needed to detect players and the ball in unseen match footage under a university deadline and limited training resources. We also explored referee and jersey-number recognition.",
|
||||
"contribution": "I handled dataset preparation, YOLO training, jersey-classifier design, experiments, evaluation, and demo integration. My collaborator created the initial repository structure and video-processing pipeline.",
|
||||
"technicalDecisions": [
|
||||
"Convert SoccerNet tracking data into a reproducible YOLO training layout and keep training behavior configuration-driven.",
|
||||
"Compare pretrained ResNet, MobileNet, and EfficientNet variants for jersey classification.",
|
||||
"Add class weighting, checkpoint/resume, focal loss, mixup/cutmix, label smoothing, and early stopping as controlled experiments rather than assuming each technique would improve the model.",
|
||||
"Prefer the simpler ResNet34 configuration after an eight-hour ablation set showed that aggressive augmentation increased overfitting and reduced validation performance."
|
||||
"I converted SoccerNet tracking data into a reproducible YOLO training layout and controlled training through configuration files.",
|
||||
"I compared pretrained ResNet, MobileNet, and EfficientNet variants for jersey classification.",
|
||||
"I tested class weighting, focal loss, mixup/cutmix, label smoothing, and early stopping, with checkpoints so training could resume.",
|
||||
"I chose a simpler ResNet34 configuration after an eight-hour set of ablation experiments showed that aggressive augmentation increased overfitting and reduced validation performance."
|
||||
],
|
||||
"outcome": "The submitted demo processed previously unseen, compressed broadcast footage and retained strong player detection. Measured validation results were 0.942 mAP@0.5 for players, 0.726 for referees, and 0.198 for the ball. The best jersey classifier reached approximately 0.778 validation accuracy, while integrated jersey labels remained inconsistent. The result is a working academic demonstration, not a production tracking system.",
|
||||
"outcome": "I tested the demo on previously unseen, compressed broadcast footage, where player detection held up well. My measured validation results were 0.942 mAP@0.5 for players, 0.726 for referees, and 0.198 for the ball. The best jersey classifier reached approximately 0.778 validation accuracy, but jersey labels remained inconsistent in the integrated demo. We delivered a working academic demonstration; ball detection and jersey recognition still need improvement.",
|
||||
"url": "https://github.com/LucaPisl/footy-tracker",
|
||||
"assetIds": []
|
||||
},
|
||||
@@ -181,15 +181,15 @@
|
||||
"title": "Opinion Dynamics Simulation",
|
||||
"visibility": "public",
|
||||
"maturity": "experimental",
|
||||
"summary": "An agent-based research experiment for observing how local interactions, network structure, and cascade conditions shape group-level opinion patterns.",
|
||||
"problem": "Explore how simplified local rules can produce polarization, rapid cascades, and uneven final distributions.",
|
||||
"contribution": "Built the simulation and analysis views used to inspect modeled runs and compare changes over time.",
|
||||
"summary": "I built an agent-based simulation to explore how local interactions and network structure shape opinion patterns across a group.",
|
||||
"problem": "I wanted to explore how simple local rules can produce polarization, rapid cascades, and uneven final distributions.",
|
||||
"contribution": "I built the simulation and analysis views to inspect runs and compare changes over time.",
|
||||
"technicalDecisions": [
|
||||
"Keep the work explicitly experimental rather than presenting it as a predictive model of real people.",
|
||||
"Expose polarization, cascade thresholds, graph degree, revolt frequency, and final distributions as inspectable outputs.",
|
||||
"Document performance and network-formation limitations alongside the results."
|
||||
"I used simplified agents and rules to study modeled behavior.",
|
||||
"I exposed polarization, cascade thresholds, graph degree, revolt frequency, and final distributions as inspectable outputs.",
|
||||
"I documented performance and network-formation limitations alongside the results."
|
||||
],
|
||||
"outcome": "The project produced useful exploratory visualizations and made the model's assumptions and limitations visible; conclusions remain limited to the simulated scenarios.",
|
||||
"outcome": "I used the visualizations to compare simulated scenarios and examine the model’s assumptions. These results describe the simulation; they do not predict how real people behave.",
|
||||
"url": "https://github.com/LucaPisl/opinion-dynamics-simulation",
|
||||
"assetIds": [
|
||||
"opinion-polarization-chart",
|
||||
@@ -233,39 +233,43 @@
|
||||
"title": "Private game prototype",
|
||||
"visibility": "private",
|
||||
"maturity": "prototype",
|
||||
"summary": "A private three-week prototype built to test a compact gameplay loop under a deliberately small scope.",
|
||||
"problem": "Test a game concept quickly while keeping the scope deliberately small.",
|
||||
"contribution": "Built and iterated on the prototype during a three-week development window.",
|
||||
"summary": "I built a side-view action prototype over three weeks, focusing on a short, playable loop.",
|
||||
"problem": "I wanted to test a game concept within a short development window.",
|
||||
"contribution": "I developed and iterated on the prototype, keeping the scope small enough to play and refine quickly.",
|
||||
"technicalDecisions": [
|
||||
"Focused the work on a short gameplay loop rather than a full production release."
|
||||
"I focused development on the core gameplay loop."
|
||||
],
|
||||
"outcome": "No real title, link, video, or identifying media.",
|
||||
"assetIds": []
|
||||
"outcome": "The clip shows the prototype in play, with character movement and pursuing enemies.",
|
||||
"assetIds": ["private-game-loop", "private-game-loop-mp4", "private-game-loop-poster"],
|
||||
"mediaLayout": "single",
|
||||
"media": [{ "kind": "video", "assetId": "private-game-loop-mp4", "fallbackAssetId": "private-game-loop", "posterAssetId": "private-game-loop-poster", "alt": "Side-view action prototype with a moving character and pursuing enemies.", "caption": "A short gameplay loop from my three-week prototype.", "longDescription": "The character moves through a blue industrial arena while enemies follow." }]
|
||||
},
|
||||
{
|
||||
"id": "private-healthcare-platform",
|
||||
"title": "Private healthcare platform",
|
||||
"visibility": "private",
|
||||
"maturity": "active",
|
||||
"summary": "A confidentiality-safe summary of Luca's web-interface contribution.",
|
||||
"problem": "A healthcare workflow needed a focused web-based interface.",
|
||||
"contribution": "Contributed to the private platform's web-interface experience.",
|
||||
"summary": "I contributed to the web interface for a healthcare platform.",
|
||||
"problem": "I worked on presenting the platform’s purpose through a focused web interface.",
|
||||
"contribution": "The landing page introduces bloodwork and treatment tracking, with clear sign-in and registration actions.",
|
||||
"technicalDecisions": [
|
||||
"Keeps product details and any identifying interface data outside the public portfolio."
|
||||
"I worked within the platform’s visual direction and web experience."
|
||||
],
|
||||
"outcome": "No product identity, private link, screenshot, or health data.",
|
||||
"assetIds": []
|
||||
"outcome": "This view shows the public-facing entry point to the platform.",
|
||||
"assetIds": ["healthcare-platform-interface"],
|
||||
"mediaLayout": "single",
|
||||
"media": [{ "kind": "image", "assetId": "healthcare-platform-interface", "alt": "Healthcare landing page with a purple visual theme and a registration action.", "caption": "Landing-page detail." }]
|
||||
},
|
||||
{
|
||||
"id": "currency-converter",
|
||||
"title": "Currency Converter",
|
||||
"visibility": "public",
|
||||
"maturity": "learning",
|
||||
"summary": "A scoped .NET/Avalonia desktop project integrating external exchange-rate data and practicing typed UI development.",
|
||||
"problem": "Practice a focused desktop workflow for currency conversion with external exchange-rate data.",
|
||||
"contribution": "Implemented the application as a scoped learning exercise.",
|
||||
"technicalDecisions": ["Uses .NET and Avalonia to explore a typed desktop interface."],
|
||||
"outcome": "A scoped project for developing desktop application fundamentals.",
|
||||
"summary": "I built a currency-conversion desktop app with C#/.NET and Avalonia, using external exchange-rate data.",
|
||||
"problem": "I wanted to practice desktop UI development with a useful data-driven workflow.",
|
||||
"contribution": "I implemented currency selection, dated conversions, and a view for comparing results across several destination currencies.",
|
||||
"technicalDecisions": ["I used .NET and Avalonia to build a typed desktop interface."],
|
||||
"outcome": "The project helped me develop desktop application and external-data integration skills.",
|
||||
"url": "https://github.com/LucaPisl/CurrencyConverterAvalonia",
|
||||
"assetIds": ["currency-converter-interface"],
|
||||
"mediaLayout": "single",
|
||||
@@ -284,13 +288,13 @@
|
||||
"title": "Linux Modding Guide",
|
||||
"visibility": "public",
|
||||
"maturity": "active",
|
||||
"summary": "Ongoing community documentation focused on practical Linux troubleshooting and reusable technical explanations.",
|
||||
"problem": "Useful Linux troubleshooting knowledge benefits from clear, reusable documentation.",
|
||||
"contribution": "Wrote and maintained community-facing technical guidance.",
|
||||
"summary": "I write and maintain community documentation for practical Linux troubleshooting.",
|
||||
"problem": "I wanted to turn troubleshooting knowledge into guidance other people could follow and reuse.",
|
||||
"contribution": "I explain the steps and reasoning behind resolving issues, so readers can apply the approach to their own setup.",
|
||||
"technicalDecisions": [
|
||||
"Favors practical explanations that help readers understand and resolve issues."
|
||||
"I favor practical explanations that help readers understand and resolve issues."
|
||||
],
|
||||
"outcome": "An ongoing example of practical technical writing.",
|
||||
"outcome": "I continue to maintain the guide as a resource for the community.",
|
||||
"url": "https://github.com/LucaPisl/LinuxModdingGuide",
|
||||
"assetIds": []
|
||||
}
|
||||
@@ -308,8 +312,6 @@
|
||||
{ "name": "TLS" },
|
||||
{ "name": "Authelia" },
|
||||
{ "name": "Fail2Ban" },
|
||||
{ "name": "Btrfs" },
|
||||
{ "name": "rsync" },
|
||||
{ "name": "Nextcloud" },
|
||||
{ "name": "Proxmox/KVM" },
|
||||
{ "name": "Git" }
|
||||
@@ -334,9 +336,7 @@
|
||||
{ "name": "PostgreSQL" },
|
||||
{ "name": "SQL" },
|
||||
{ "name": "Drift/SQLite" },
|
||||
{ "name": "Drizzle ORM" },
|
||||
{ "name": "SPSS" },
|
||||
{ "name": "Microsoft Excel" }
|
||||
{ "name": "Drizzle ORM" }
|
||||
]
|
||||
},
|
||||
{
|
||||
@@ -344,24 +344,24 @@
|
||||
"technologies": [
|
||||
{ "name": "PyTorch" },
|
||||
{ "name": "Ultralytics/YOLO" },
|
||||
{ "name": "OpenCV" },
|
||||
{ "name": "SoccerNet" }
|
||||
{ "name": "OpenCV" }
|
||||
]
|
||||
}
|
||||
],
|
||||
"contact": {
|
||||
"introduction": "I’m open to System Administrator and Full-Stack Developer opportunities in Bucharest, including on-site, hybrid, and remote work, as well as international remote roles.",
|
||||
"email": "luca.pislaru@gmail.com",
|
||||
"introduction": "I’m looking for System Administrator or Full-Stack Developer roles in Bucharest—on-site, hybrid, or remote—and remote opportunities internationally.",
|
||||
"email": { "localPart": "luca.pislaru", "domain": "gmail.com" },
|
||||
"avatarAssetId": "contact-avatar",
|
||||
"social": [
|
||||
{ "service": "LinkedIn", "url": "https://linkedin.com/in/luca-pisl" },
|
||||
{ "service": "GitHub", "url": "https://github.com/LucaPisl" },
|
||||
{ "service": "GitLab", "url": "https://gitlab.com/luca_pisl" },
|
||||
{ "service": "LinkedIn", "url": "https://linkedin.com/in/luca-pisl" }
|
||||
{ "service": "GitLab", "url": "https://gitlab.com/luca_pisl" }
|
||||
],
|
||||
"cvMessage": "For a current CV or role-specific information, contact me directly."
|
||||
"cvMessage": "Get in touch for my CV or to talk about a role."
|
||||
},
|
||||
"metadata": {
|
||||
"title": "Luca Pîslaru — System Administrator & Full-Stack Developer",
|
||||
"description": "Portfolio of Luca Pîslaru, a Bucharest-based System Administrator and Full-Stack Developer working across Linux infrastructure and end-to-end software delivery.",
|
||||
"description": "I’m Luca Pîslaru, a System Administrator & Full-Stack Developer based in Bucharest. Explore my work in Linux infrastructure and end-to-end application development.",
|
||||
"socialPreviewAssetId": "social-preview-nightdrive"
|
||||
},
|
||||
"soundtrack": {
|
||||
|
||||
Reference in New Issue
Block a user