246 lines
11 KiB
JSON
246 lines
11 KiB
JSON
{
|
||
"identity": {
|
||
"name": "Luca Pîslaru",
|
||
"role": "System Administrator & Full-Stack Developer",
|
||
"valueProposition": "Building and operating reliable systems and software."
|
||
},
|
||
"navigation": [
|
||
{ "id": "start", "label": "Start" },
|
||
{ "id": "profile", "label": "Profile" },
|
||
{ "id": "experience", "label": "Experience" },
|
||
{ "id": "infrastructure", "label": "Infrastructure" },
|
||
{ "id": "selected-builds", "label": "Selected builds" },
|
||
{ "id": "additional-work", "label": "Additional work" },
|
||
{ "id": "toolkit", "label": "Toolkit" },
|
||
{ "id": "contact", "label": "Contact" }
|
||
],
|
||
"profile": {
|
||
"introduction": "I work across Linux infrastructure and full-stack delivery, pairing practical operations with software built to be understood, maintained, and improved over time.",
|
||
"screeningFacts": [
|
||
{ "label": "Education", "value": "Bachelor's degree in Business Management IT, Romanian-American University, 2023–2026" },
|
||
{ "label": "Languages", "value": "Romanian (native), English (C2), French (A1)" },
|
||
{ "label": "Certification", "value": "PCEP — Certified Entry-Level Python Programmer, 2022" }
|
||
]
|
||
},
|
||
"experience": [
|
||
{
|
||
"id": "mihai-razus-pfa",
|
||
"role": "Full-Stack Developer & DevOps collaborator",
|
||
"organization": "Mihai Razus PFA",
|
||
"dates": "Aug 2025 – Present",
|
||
"highlights": [
|
||
"Contribute to full-stack delivery across application and deployment work.",
|
||
"Support practical DevOps collaboration alongside software development."
|
||
]
|
||
},
|
||
{
|
||
"id": "camera-consultantilor-fiscali",
|
||
"role": "Green Innovation Intern",
|
||
"organization": "Camera Consultanților Fiscali",
|
||
"dates": "Jun 2025 – Aug 2025",
|
||
"highlights": [
|
||
"Contributed to green innovation work in an internship setting.",
|
||
"Applied structured problem-solving and digital skills to assigned work."
|
||
]
|
||
},
|
||
{
|
||
"id": "isense-solutions",
|
||
"role": "Data Science Intern",
|
||
"organization": "iSense Solutions",
|
||
"dates": "Jun 2025 – Aug 2025",
|
||
"highlights": [
|
||
"Contributed to data science work in an internship setting.",
|
||
"Applied analytical and programming skills to assigned tasks."
|
||
]
|
||
}
|
||
],
|
||
"systemsOperations": {
|
||
"id": "professional-systems-operations",
|
||
"title": "Professional systems operations",
|
||
"summary": "Professional work that connects application delivery with the Linux environments and deployment practices that support it.",
|
||
"evidence": [
|
||
"Linux server administration and service management.",
|
||
"Docker and Nginx deployment work, including TLS-aware service delivery.",
|
||
"Operational troubleshooting alongside full-stack development."
|
||
]
|
||
},
|
||
"infrastructure": {
|
||
"id": "self-hosted-platform-lifecycle",
|
||
"title": "Secure self-hosted platform and lifecycle",
|
||
"summary": "A personal Linux platform operated as a compact systems case study: secure ingress, deliberate access controls, service lifecycle discipline, and routine maintenance.",
|
||
"bands": [
|
||
{
|
||
"id": "ingress-and-tls",
|
||
"title": "Ingress and TLS",
|
||
"summary": "Routes services through Nginx with certificate issuance and renewal managed through Let's Encrypt and Certbot; exposed entry points receive fail2ban protection."
|
||
},
|
||
{
|
||
"id": "identity-and-access",
|
||
"title": "Identity and access",
|
||
"summary": "Uses an authentication layer for protected services, with passkeys, two-factor authentication, and recovery considered without publishing policy details."
|
||
},
|
||
{
|
||
"id": "service-lifecycle",
|
||
"title": "Service lifecycle",
|
||
"summary": "Deploys containerized services, manages updates, and treats service enrollment and retirement as part of ongoing maintenance."
|
||
},
|
||
{
|
||
"id": "operations-and-maintenance",
|
||
"title": "Operations",
|
||
"summary": "Investigates service issues and performs routine maintenance while keeping the platform understandable and manageable."
|
||
}
|
||
]
|
||
},
|
||
"projects": {
|
||
"selected": [
|
||
{
|
||
"id": "private-medication-tracker",
|
||
"title": "Private self-hosted medication tracker",
|
||
"visibility": "private",
|
||
"maturity": "active",
|
||
"summary": "A private multi-device medication system for schedules, stock awareness, adherence logging, and shared administration.",
|
||
"problem": "Medication routines need a dependable way to handle scheduled and as-needed entries across devices.",
|
||
"contribution": "Designed and built the private client, server, synchronization, and administrative workflow.",
|
||
"technicalDecisions": [
|
||
"Supports profiles, scheduled and as-needed medication, stock tracking, notifications, and logged activity.",
|
||
"Keeps a server component and administrative interface alongside the multi-device experience."
|
||
],
|
||
"outcome": "The product remains private; this portfolio presents its scope without a public link or media.",
|
||
"assetIds": []
|
||
},
|
||
{
|
||
"id": "footy-tracker",
|
||
"title": "Footy Tracker",
|
||
"visibility": "public",
|
||
"maturity": "work-in-progress",
|
||
"summary": "A work-in-progress computer-vision pipeline for football footage.",
|
||
"problem": "Football footage needs a repeatable way to detect and follow players over time.",
|
||
"contribution": "Built the player detection and tracking pipeline and continue to explore jersey recognition.",
|
||
"technicalDecisions": [
|
||
"Separates player detection and tracking from the ongoing jersey-recognition work.",
|
||
"Keeps the pipeline focused on footage analysis rather than claiming production readiness."
|
||
],
|
||
"outcome": "Player detection and tracking are the current focus; jersey recognition remains ongoing work.",
|
||
"assetIds": []
|
||
},
|
||
{
|
||
"id": "opinion-dynamics-simulation",
|
||
"title": "Opinion Dynamics Simulation",
|
||
"visibility": "public",
|
||
"maturity": "experimental",
|
||
"summary": "An experimental agent-based simulation for exploring how group opinions change.",
|
||
"problem": "Explore how local interactions can produce different group-level opinion patterns.",
|
||
"contribution": "Built the experimental model and the result views used to inspect its runs.",
|
||
"technicalDecisions": [
|
||
"Treats the work as an experimental model rather than a predictive product.",
|
||
"Uses structured result views to compare changing variables and observed trends."
|
||
],
|
||
"outcome": "The project is presented as research exploration, with conclusions limited to the modeled scenarios.",
|
||
"assetIds": []
|
||
}
|
||
],
|
||
"additional": [
|
||
{
|
||
"id": "private-game-prototype",
|
||
"title": "Private game prototype",
|
||
"visibility": "private",
|
||
"maturity": "prototype",
|
||
"summary": "A private three-week prototype focused on testing a compact gameplay loop.",
|
||
"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.",
|
||
"technicalDecisions": [
|
||
"Focused the work on a short gameplay loop rather than a full production release."
|
||
],
|
||
"outcome": "The prototype remains private and is described without a public link or media.",
|
||
"assetIds": []
|
||
},
|
||
{
|
||
"id": "private-healthcare-platform",
|
||
"title": "Private healthcare platform",
|
||
"visibility": "private",
|
||
"maturity": "active",
|
||
"summary": "A private web platform presented here only at a high level.",
|
||
"problem": "A healthcare workflow needed a focused web-based interface.",
|
||
"contribution": "Contributed to the private platform's web experience.",
|
||
"technicalDecisions": [
|
||
"Keeps product details and any identifying interface data outside the public portfolio."
|
||
],
|
||
"outcome": "The platform remains private and has no public link or media.",
|
||
"assetIds": []
|
||
},
|
||
{
|
||
"id": "currency-converter",
|
||
"title": "Currency Converter",
|
||
"visibility": "public",
|
||
"maturity": "learning",
|
||
"summary": "A modest .NET and Avalonia learning project.",
|
||
"problem": "Practice a focused desktop workflow for currency conversion.",
|
||
"contribution": "Implemented the application as a scoped learning exercise.",
|
||
"technicalDecisions": [
|
||
"Uses .NET and Avalonia to explore a typed desktop interface."
|
||
],
|
||
"outcome": "A deliberately modest project for developing desktop application fundamentals.",
|
||
"assetIds": []
|
||
},
|
||
{
|
||
"id": "linux-modding-guide",
|
||
"title": "Linux Modding Guide",
|
||
"visibility": "public",
|
||
"maturity": "active",
|
||
"summary": "Community documentation that shares Linux troubleshooting and technical writing practice.",
|
||
"problem": "Useful Linux troubleshooting knowledge benefits from clear, reusable documentation.",
|
||
"contribution": "Wrote and maintained community-facing technical guidance.",
|
||
"technicalDecisions": [
|
||
"Favors practical explanations that help readers understand and resolve issues."
|
||
],
|
||
"outcome": "An ongoing example of technical writing without relying on popularity counts.",
|
||
"assetIds": []
|
||
}
|
||
]
|
||
},
|
||
"toolkit": [
|
||
{
|
||
"title": "Systems & delivery",
|
||
"technologies": [
|
||
{ "name": "Linux" },
|
||
{ "name": "Docker" },
|
||
{ "name": "Nginx" },
|
||
{ "name": "Proxmox / KVM" },
|
||
{ "name": "Git" }
|
||
]
|
||
},
|
||
{
|
||
"title": "Software & data",
|
||
"technologies": [
|
||
{ "name": "Python" },
|
||
{ "name": "Vue.js" },
|
||
{ "name": "JavaScript" },
|
||
{ "name": "C# / .NET" },
|
||
{ "name": "Flutter / Dart" },
|
||
{ "name": "PostgreSQL / SQL" },
|
||
{ "name": "Headless WordPress" }
|
||
]
|
||
},
|
||
{
|
||
"title": "Additional experience",
|
||
"technologies": [
|
||
{ "name": "Java" }
|
||
]
|
||
}
|
||
],
|
||
"contact": {
|
||
"email": "luca.pislaru@gmail.com",
|
||
"social": [
|
||
{ "service": "GitHub", "url": "https://github.com/LucaPisl" },
|
||
{ "service": "GitLab", "url": "https://gitlab.com/luca_pisl" },
|
||
{ "service": "LinkedIn", "url": "https://linkedin.com/in/luca-pisl" }
|
||
],
|
||
"cvMessage": "For a current CV or role-specific information, contact me directly."
|
||
},
|
||
"metadata": {
|
||
"title": "Luca Pîslaru — System Administrator & Full-Stack Developer",
|
||
"description": "Portfolio of Luca Pîslaru, a System Administrator & Full-Stack Developer building and operating reliable systems and software."
|
||
},
|
||
"sceneDescription": "A restrained retro-futuristic night drive supports the reading journey while the portfolio content remains fully available as a semantic document."
|
||
}
|