SVN/Git Wrangling, Laravel Rage, and HR IT Headaches

This week was chaos and cleanup. Here's the damage:

Git vs SVN: The Migration No One Wants to Do

Tried migrating an old SVN project (HR Application) to GitLab. Did care about the history - just wanted to mirror the damn folder structure. But Git decided to throw a tantrum: thought I was deleting files instead of moving them. Line endings (CRLF/LF) made diffs unreadable. Classic.

Lesson: Git doesn't forgive structural violence. Plan your moves like a game of chess, or prepare to revert everything with tears in your eyes.

Laravel: The Bidding Site and Codex Fatigue

I pushed live a Laravel app generated by Codex, a bidding system for a house.

This was my first time using Laravel for a project. Thanks GPT.

Issues, as expected:

• Root URL 404'd even though child routes worked.
• Images failed to load - turns out the photos folder wasn't in /public.
• Codex-generated registration form had no validation for phone or email. No feedback. No regex. Just vibes.
• Dropdown fields broke silently. Inspect, guess, cry, repeat.

Reminder: Don't trust AI scaffolding tools to finish the job. They're good starters - but lazy interns if left alone.

IT Form: Webservice Shenanigans in Production

On the HR application side, we pushed the IT webform to VA for live testing. Tried to submit a 5-day annual leave transfer - frontend looked fine, but backend didn't call the WS or trigger the fallback email.

Suspected areas:

• Silent WS push failure (PUSH_DEMANDE_ACTION)
• Fallback notification logic not firing
• No way to trace unless I dig through VA logs

Deployed, tested, and now chasing ghosts. It works locally. On VA? Shrugs.

Final Thought: Stop the Framework Madness

Every time I touch a framework, something breaks that HTML never asked for. Bloat creeps in. Pages slow down. Errors multiply. We used to build websites. Now we build excuses.

If you want something to work keep it simple.

// no JS frameworks were harmed in the making of this log