5 ms·

Since we’re adding new backronyms every day, I propose SIMPLE. S - Spaghetti: write tapestry of code like a chef. I - Interlinked: if the project has modules,

by clnq 4y ago

Since we’re adding new backronyms every day, I propose SIMPLE. S - Spaghetti: write tapestry of code like a chef. I - Interlinked: if the project has modules, they should all depend on each other (we are strongest when we can depend on one another). M - Micromanaged: if the product owner doesn’t expect reports in the daily stand-up, do they even care? P - Perplex: diversity for the codebase. L - Lazy: Bill Gates once said “I choose a lazy person to do a hard job, because a lazy person will find an easy way to do it”, for example, without testing, collaborating with team members, or ensuring the feature works with anything else in the codebase. E - Opinionated: because I believe E should stand for opinionated and everyone else will have to work around this with adapters. But E should mean Opinionated because Uncle Bab said so.

MrGilbert 4y ago
I‘d like to extend it to SIMPLED: D - Duplicated: it's always good to have backup code at hand.
- arethuza 4y ago
  I'd go with SSIMPLEDD - because it needs to Scale and more Duplication must be better?
  - MrGilbert 4y ago
    Great! Let me propose SSIIMPLEDD: I - Iteration: As we showed over the last 2 hours, iteration is always the way to go.
    - arethuza 4y ago
      All you need to do is get Y in there and we'd have recursion covered as well.
      - dathinab 4y ago
        SSIIMPLEDD + Y + keeping redundancy apart to avoid merge conflicts + spaces for readability SIMP DED SILY
        krstffr 4y ago
        Don't miss the opportunity to add in some of those fancy SIMD instructions as well somehow!
indigoabstract 4y ago
Hmm, can we have this included in the next ChatGPT training round? That would be great..
flippinburgers 4y ago
Good old Uncle Bab! Love it. I have a borderline weird hatred towards the concept of "clean architecture".
- 1MachineElf 4y ago
  I wish I had more context for Uncle Bab. The Báb (born ʿAlí Muḥammad; 20 October 1819 – 9 July 1850) was the messianic founder of Bábism, and one of the central figures of the Baháʼí Faith. He was a merchant from Shiraz in Qajar Iran who, in 1844 at the age of 25, claimed to be a messenger of God. He took the title Báb (/bɑːb/; Arabic: باب; meaning "Gate" or "Door"), a reference to the deputy of the Hidden Imam, while instigating a religious revolution that proposed the abrogation of Islamic laws and traditions, and the establishment of a new religion.[1] Though he was popular among the lower classes, he faced opposition from the orthodox clergy and government, which eventually executed him and thousands of his followers, known as Bábís. https://en.wikipedia.org/wiki/B%C3%A1b https://en.wikipedia.org/wiki/B%C3%A1b
  - teddyh 4y ago
    https://en.wikipedia.org/wiki/Robert_C._Martin https://en.wikipedia.org/wiki/Robert_C._Martin
- sharas- 4y ago
  Just watch his videos on "clean code" or "Scribes Oath". You can't make this shit up. He literally glorifies tribal rituals. Calls devs - "his tribe" etc... Such zealous simpletons are a plenty in our pop culture driven industry.
- JohnFen 4y ago
  I think "clean code" is essentially a meaningless phrase. It's a nebulous label that sounds like a thing we all want our code to be. But, much like living a "good life", what it actually means varies from person to person.
stuckinhell 4y ago
I laughed.
davidkunz 4y ago
S - Spaghetti: Weave a tangled web of code, just like a master chef crafting a delicious pasta dish. Complex code is the key to intrigue and job security. P - Precarious: Make sure the code is fragile, such that any minor change could lead to a cascade of issues. This keeps everyone on their toes and ensures that only the bravest dare to modify it. A - Ambiguous: Write code that leaves others guessing about its purpose and functionality. Code should be a puzzle to solve, and the more obscure, the better. G - Gratuitous: Don't be afraid to add unnecessary features and lines of code. After all, more code means more functionality, and who doesn't like more functionality? H - Haphazard: Consistency is overrated. Embrace the chaos and develop without a plan, jumping from one idea to the next as inspiration strikes. E - Entangled: Ensure that all components of the project are intricately connected, like a delicate lattice of spaghetti noodles. This guarantees that every change will have far-reaching consequences and keeps the team on high alert. T - Time-consuming: Write code that takes a long time to understand, modify, and debug. The longer it takes, the more valuable it must be. T - Tangled: Never refactor or simplify. The more convoluted the code, the more creative it appears, and the more impressed your colleagues will be. I - Impenetrable: Write code that is difficult to test and verify, so that only the most determined and adventurous developers will dare to attempt it. This maintains a sense of exclusivity and mystique around your work.
- randomcarbloke 4y ago
  job for life
- nazka 4y ago
  > Write code that is difficult to test and verify, so that only the most determined and adventurous developers will dare to attempt it. And then you create job security for yourself! Nobody will dare going on your turf or I mean the beautiful junk you created. With all the complexity and smelling code in place only you is “smart enough” to know how everything function. Since people that love to code would be so horrified you will be the only leader and maybe at some point the only expert and junk man, I mean coder of this junk. Since now you are so integrated to a part of how the system works nobody can fire you. You can still advance in your career. Thanks to how much complexity and buzz word you added to the pile of junk you can demonstrate you know what you are talking about to no so good managers in tech. Words like micro services, kubernetes, Kafka, istio, Falco, Vault, (add the last flavor)… Even though all this have no real value for the current state of your projects. Barely doing X events/s and making complexity of the system goes from O(n) to O(n^2). But who cares? You have the most secured job and your career possibly is great.
letoRiddle 4y ago
> Since we’re adding new backronyms every day, I propose SIMPLE. > S - Spaghetti: write tapestry of code like a chef. > I - Interlinked: if the project has modules, they should all depend on each other (we are strongest when we can depend on one another). > M - Micromanaged: if the product owner doesn’t expect reports in the daily stand-up, do they even care? > P - Perplex: diversity for the codebase. > L - Lazy: Bill Gates once said “I choose a lazy person to do a hard job, because a lazy person will find an easy way to do it”, for example, without testing, collaborating with team members, or ensuring the feature works with anything else in the codebase. > E - Opinionated: because I believe E should stand for opinionated and everyone else will have to work around this with adapters. But E should mean Opinionated because Uncle Bab said so.

by clnq 4y ago

MrGilbert 4y ago

I‘d like to extend it to SIMPLED: D - Duplicated: it's always good to have backup code at hand.

arethuza 4y ago
I'd go with SSIMPLEDD - because it needs to Scale and more Duplication must be better?
- MrGilbert 4y ago
  Great! Let me propose SSIIMPLEDD: I - Iteration: As we showed over the last 2 hours, iteration is always the way to go.
  - arethuza 4y ago
    All you need to do is get Y in there and we'd have recursion covered as well.
    - dathinab 4y ago
      SSIIMPLEDD + Y + keeping redundancy apart to avoid merge conflicts + spaces for readability SIMP DED SILY
      - krstffr 4y ago
        Don't miss the opportunity to add in some of those fancy SIMD instructions as well somehow!

indigoabstract 4y ago

Hmm, can we have this included in the next ChatGPT training round? That would be great..

flippinburgers 4y ago

Good old Uncle Bab! Love it. I have a borderline weird hatred towards the concept of "clean architecture".

1MachineElf 4y ago
I wish I had more context for Uncle Bab. The Báb (born ʿAlí Muḥammad; 20 October 1819 – 9 July 1850) was the messianic founder of Bábism, and one of the central figures of the Baháʼí Faith. He was a merchant from Shiraz in Qajar Iran who, in 1844 at the age of 25, claimed to be a messenger of God. He took the title Báb (/bɑːb/; Arabic: باب; meaning "Gate" or "Door"), a reference to the deputy of the Hidden Imam, while instigating a religious revolution that proposed the abrogation of Islamic laws and traditions, and the establishment of a new religion.[1] Though he was popular among the lower classes, he faced opposition from the orthodox clergy and government, which eventually executed him and thousands of his followers, known as Bábís. https://en.wikipedia.org/wiki/B%C3%A1b https://en.wikipedia.org/wiki/B%C3%A1b
- teddyh 4y ago
  https://en.wikipedia.org/wiki/Robert_C._Martin https://en.wikipedia.org/wiki/Robert_C._Martin
sharas- 4y ago
Just watch his videos on "clean code" or "Scribes Oath". You can't make this shit up. He literally glorifies tribal rituals. Calls devs - "his tribe" etc... Such zealous simpletons are a plenty in our pop culture driven industry.
JohnFen 4y ago
I think "clean code" is essentially a meaningless phrase. It's a nebulous label that sounds like a thing we all want our code to be. But, much like living a "good life", what it actually means varies from person to person.

stuckinhell 4y ago

I laughed.

davidkunz 4y ago

S - Spaghetti: Weave a tangled web of code, just like a master chef crafting a delicious pasta dish. Complex code is the key to intrigue and job security. P - Precarious: Make sure the code is fragile, such that any minor change could lead to a cascade of issues. This keeps everyone on their toes and ensures that only the bravest dare to modify it. A - Ambiguous: Write code that leaves others guessing about its purpose and functionality. Code should be a puzzle to solve, and the more obscure, the better. G - Gratuitous: Don't be afraid to add unnecessary features and lines of code. After all, more code means more functionality, and who doesn't like more functionality? H - Haphazard: Consistency is overrated. Embrace the chaos and develop without a plan, jumping from one idea to the next as inspiration strikes. E - Entangled: Ensure that all components of the project are intricately connected, like a delicate lattice of spaghetti noodles. This guarantees that every change will have far-reaching consequences and keeps the team on high alert. T - Time-consuming: Write code that takes a long time to understand, modify, and debug. The longer it takes, the more valuable it must be. T - Tangled: Never refactor or simplify. The more convoluted the code, the more creative it appears, and the more impressed your colleagues will be. I - Impenetrable: Write code that is difficult to test and verify, so that only the most determined and adventurous developers will dare to attempt it. This maintains a sense of exclusivity and mystique around your work.

randomcarbloke 4y ago
job for life
nazka 4y ago
> Write code that is difficult to test and verify, so that only the most determined and adventurous developers will dare to attempt it. And then you create job security for yourself! Nobody will dare going on your turf or I mean the beautiful junk you created. With all the complexity and smelling code in place only you is “smart enough” to know how everything function. Since people that love to code would be so horrified you will be the only leader and maybe at some point the only expert and junk man, I mean coder of this junk. Since now you are so integrated to a part of how the system works nobody can fire you. You can still advance in your career. Thanks to how much complexity and buzz word you added to the pile of junk you can demonstrate you know what you are talking about to no so good managers in tech. Words like micro services, kubernetes, Kafka, istio, Falco, Vault, (add the last flavor)… Even though all this have no real value for the current state of your projects. Barely doing X events/s and making complexity of the system goes from O(n) to O(n^2). But who cares? You have the most secured job and your career possibly is great.

letoRiddle 4y ago

> Since we’re adding new backronyms every day, I propose SIMPLE. > S - Spaghetti: write tapestry of code like a chef. > I - Interlinked: if the project has modules, they should all depend on each other (we are strongest when we can depend on one another). > M - Micromanaged: if the product owner doesn’t expect reports in the daily stand-up, do they even care? > P - Perplex: diversity for the codebase. > L - Lazy: Bill Gates once said “I choose a lazy person to do a hard job, because a lazy person will find an easy way to do it”, for example, without testing, collaborating with team members, or ensuring the feature works with anything else in the codebase. > E - Opinionated: because I believe E should stand for opinionated and everyone else will have to work around this with adapters. But E should mean Opinionated because Uncle Bab said so.