63
linuxxx
6y

I remember that time my class (first year of software development) wrote a huge project for a real company as practice for irl stuff.

I was the only Linux user and it would be deployed on a Linux server.

Spent 10 weeks of development and then the moment of deployment on a Linux server began!

.
.
.
.
.

Nothing was case sensitive, everything was programmed for a windows architecture (backward slashes etc) and mssql was used while we would host it on a MySQL server.

The tree core guys spent three days or so to make the entire fucker compatible 😂

It was enjoyable to see them (literally) sweat 😊 (it had been known from the very beginning)

Comments
  • 8
    I just want to mention ORMs with exchangable database backend. They might not be everybodys favorite, but for me they always worked.
  • 6
    @gitreflog first class, never programmed before (the most guys) and this was about 6 years ago :)
  • 4
    To be fair, case sensitivity sucks...

    Did any of the team members switch from Windows after they got it working?
  • 1
    @Torbuntu
    Please explain? I've ran into more issues with case sensitivity than I have with case insensitivity
  • 1
    @Torbuntu
    I'm mostly folder structure but that can still be easily fixed, a la "Danish (country), danish (pastery)". That may not be the most precise way, but it's more informative, especially if someone were to not know what one of the two things were.
  • 2
    @Torbuntu I agree.
    A != a
    65 != 97

    Fuzzy comparisons only ever lead to confusion, and confusion is bad.
  • 1
    Actually at my job, on our dev laptops, we have a case sensitive partition where we code in, because in the past there's been to many small screw-ups due to wrong cased files ending up on our case sensitive production systems... And those can be soo annoyingly hard to spot if you don't immediately realise what's happening...
Add Comment