5

Current directory:

upstream
potatoecode

find ./upstream -maxdepth 1 -type d -ls >> potatoecode/.gitignore

pushd potatoecode
git add .gitignore
git commit -m 'Updated gitignore" .gitignore
git rm -r --cached .
git add .
git commit -am "Purgatory"
popd

*watching with a big smile the burning CI*

--

Story of how I made some devs today very sad. They now have the joyful task to think of a better way to code than to create a nightmare blob of modified source code from upstream - where upstream has ...

- a rest API
- an extension / plugin system
- an system to even modify db schema via an API.

But nooooo.... That would be too good.

Instead one just creates an potatohead of upstream source code with modifications without any version tracking or stuff like that.

Sometimes I really wonder if the devs at our company are masochists and want to be punished....

Comments
  • 0
    Any other types of punishment available? I might want to get hired there... 😏
  • 0
    @NoMad nah.

    But it just amazes me that whenever I think they hit rock bottom they still manage to surprise me.

    I really hope you never did this - I'd file for divorce. :)
  • 0
    @IntrusionCM I didn't, but the spice in this marriage is lacking. So am wondering if removing all gitignores (one by one in a long while) or full merging all dev branches into main (and removing the branches themselves) would spark a hardcore sex session. 😎
  • 1
    @NoMad if u really want to annoy me, you can try the DDOS style LDAP query they did a few days ago...

    Suddenly every tool went bananas as authserver couldn't handle the load.

    (yeah... It has a replica... But that's not enough if dev doesn't use rate limiting and makes bad life choices. I was in meeting luckily and only had to clean up the mess afterwards) :)
  • 1
    @NoMad Look, I don't kinkshame but this is plain evil
  • 0
    no comment this time.
    none at all.
    fffuuuuuuuuuuuuu
Add Comment