30

Ok so this happend in the last 3 days, I didn't post it till now because I had to seriously take a rest with all the bullshit and stress that came with it...
(Legacy project I have the lead in called: "Foo")

Monday:
Management decided it would be effective to add a senior and a junior to Foo, which would make (together with me) to be 2 juniors and one senior developer
Well I've spend most of that day helping both the junior and the senior to setup "Foo" on their local development machines... So I could not do any programming myself

tuesday:
The senior wanted to refactor EVERYTHING... and I had to stop him multiple times because we simply do not have the time to do that...
The junior tried to work on other things as much as he could, and after he had run out of things to do, asked me for EVERYTHING... EVEN WHERE TO FUCKING CHANGE SOME GOD DAMN STRINGS!....
Also he did in total 3 commits, two of which existed of my code (because I had to "help" him

wednesday:
Both the junior and senior were removed from the project and I got another senior.. who fucking deleted the production database on accident

god damn rough few days man...

Comments
  • 2
    Maybe management wanted to punish the Seniors and the 2nd one wanted to leave Foo asp
  • 2
    Remember tomorrow is Friday, and you have to enjoy your weekend
  • 4
    "Senior" and "deleted production database" don't fit the same sentence. That's called a monkey that runned with the circus for too long.
  • 1
    Production db unguarded, left for everyone to fiddle with? What are you doing there? Wordpress?
    It sounds like you could use strictier environment separation in your process. And perhaps some data redundancy.
  • 1
    @mt3o no it's even better, we create Laravel based ERP systems (creating custom software)

    But I do agree with you.. it's a mess, for quite awhile now
  • 1
    Hey, then it should be quite easy to set up env separation. Laravel has some nice features for this. Do you have any CI/CD pipeline? Like Jenkins or TeamCity? Last step would be reviewing the db access policies. I guess your sdev has plenty of habits orginating from old days like php4 (i do, but since then I migrated myself to java and work on a system where db is just a read-only api for me).

    You could use this opportunity to introduce some changes to the way the project is managed. And ask for rise.
  • 0
    @mt3o that's Nice and all but the legacy project Foo is not Laravel 😂 it's some handcrafted mess with a bit of cake PHP 2 thrown in
Add Comment