It's 2018 and I am forced to add new features on project that was deployed in 2003 and lastly updated at 2009.

Best part is that PHP version on the production server is [drum roll] 4.3.8. I found out that this version was the latest at July 2003. On top of that, server runs on Windows Server 2003 and the database is oracle (meaning php driver is needed).

I have spent a WHOLE WEEK just trying to recreate that environment in order to start working on the new features.

Sorry for grumping but I had to take it out somewhere.

  • 12
    Welcome to running the past in the future! Where nothing works and if it does you won't know why!
  • 5
    You can still be happy that you have to implement new features. There are people out there that have to fix bugs all day in such a project. 👌
  • 1
    size of code base and database complexity?
  • 0
    In that's case, make a backups for all, and deploy new instance in production server.
  • 0
    Hahaha that’s funny and we as developers understand your feelings.

    But seeing from the business perspective, why the heck would we change things if they’re just working? Hun?
  • 0
    containerize it
  • 1
    @heyheni not familiar with containers only read some articles. No time to study them now.
  • 2
    @varch new requirements from the client. They need “advanced search tools”
  • 1
    @JMente oh yeah backups. I forgot about that... eh whatever I am James Bond Code
  • 3
    @ralnivar about 200 php files and at a glance around 50 tables. I wish it does not come to a point where I should learn the complete project structure since there is no framework. I just want to get this of my head.
  • 0
    @N-o-X at this point this could be possibly better because I will only patch a part of code and not add to it meaning that new components have to be compatible with the rest project.
  • 0
    Get the infrastructure upgraded or leave that forsaken project.
Add Comment