64
atroxi
2y

My colleague's vision of the word "structure"...........

Comments
  • 1
    Dear god.
  • 3
    I'm fucking depressed about it as he's not ready to change.. Also... Another funny thing about it..Well not funny at all actually but as it's a satire... The src folder is in the directory that gets deployed automatically... Fml
  • 7
    I also wish this rant gets more than 20++ so I can tell him how I got my sticker.. Common guys I need you on that. Share my rant please!
  • 16
    Dafaq?! O.o
    Also why is noone concerned where did the 07 & 08 went.. ??!?
  • 1
    Haha What the hell right?!
  • 1
    @sladuled First thing I noticed
  • 2
    I have a lot of work mates who think that this is a nice naming structure for SharePoint library content. Not understanding that tagging information and providing filters helps all, also users who are not​ familiar with their directory structure. Their argument: I know that structure and find every file quickly this way.
    F*ck, and what about your mates??
  • 1
    @MrThompson my mate probably doesn't have a clue of what a good, maintainable and deployable structure is I'm afraid.. I'm not sure he even experienced it once. But that's OK if he's open to learn from others. What isn't ok is that he's stubborn AF only in order to stick with his own preferences. I believe a good structures are reusable/understandable by any dev without too many effort in order to get started. He just loves to create exceptions and fucking random namespaces. But... Don't get me started on the details, please 😂
  • 1
    @MrThompson and no, this isn't related to sharepoint as far as I know 😉
  • 0
    @atroxi it is to "structure" in general. SharePoint might be ugly and slow but still can be used to structure something. 😂
  • 2
    My 2 cents - I've worked in code bases that were complete dumpster fires in terms of structure. Every now and then, someone would try to start a project to move all the code. Basically it just made things worse. No one ever finishes everything completely in a large code base.

    Honestly that structure is far from the worst thing I've seen. It's main problem appears to be the synonyms. What's a module vs a component? Plugins vs vendors? Base vs layout? I don't mind the numbering, except for the obvious missing no.

    Oh maybe it is kinda of a bad structure ha.
  • 2
    @meowth precisely. Synonyms = headf#*k 😂
  • 1
    @atroxi hah, ya I kept revising my comment as I found more things wrong with it.
  • 1
    @meowth Hehe... Believe me that's the top of the iceberg regarding synonyms, hidden files, configs all over etc.. But I didn't bother showing. That's enough of a headf**k and it gets you wondering. Enough for me to make my point 🦄
  • 1
  • 1
    @SISheogorath love that 😂🦄
  • 2
    @sladuled I guess this time 9 ate 7.
  • 3
    @shellbug and 08.. 😂😂
Add Comment