56

So where to start... Let me preface this by saying I am a Software Architect for C# and do 99% dotnet development.

I just received a phone call from our Director of Development asking me to look at adding a feature for SSO with our companies main development project, which is written in PHP. I hope I made the correct changes but since I am not a PHP dev... I am not 100% confident in my code.

Now I am writing this as we are making the deployment Friday, December 29, 2017 at 5:00 pm. I should add that I am going on vacation for the next week.

So let me summarize... I am not a PHP developer, the non-PHP developer is making PHP changes on a Friday Night, and before a long weekend and before going on vacation.

I would like to point out that I said I was not 100% comfortable with this... but well this is what they wanted. I am not even sure what really to say about this though.

Comments
  • 4
    Damn, my hearts out with you bro lol
  • 3
    I read the into wrong and though you were one of the devs FOR C# and .NET, I got confused when I read PHP πŸ˜›

    I enjoyed reading this rant a lot πŸ˜›
  • 0
    Well software architect means ur like crazy experienced?

    I'm not there and doubt I ever will be but I guess I could hack something together... So for you shouldn't be a problem?

    btw just wondering whats the diff between n architect and a developer?
  • 3
    @billgates Architect is someone who works on the design of the systems and not just works on specific aspects of code, I was a Senior Dev for about three years before that promotion. That being said any deployments when they were pushing them was a bad idea, but doing PHP by someone who does dotnet is just not a great idea. Not to mention it is our internally written IDP SSO solution and effects other SSO platforms.
  • 2
    my thoughts are with you =) how did the deployment go?
  • 2
    @lenniep rofl, well it fixed the one problem but something else was reported as broken, I am not sure how. I told them to test all aspects prior to the deployment but the said the other SSO stuff was fine so they didn’t need toπŸ™„.

    We ended up rolling back and the stuff that was broken during the deployment was broken again... for about three minutes, which again wouldn’t be possible.

    In the end, the third party was able to certify the SSO code worked, because it did for 3 minutes, and our director said they can fix it next year.
Add Comment