[-] Lysergid@lemmy.ml 5 points 3 days ago* (last edited 3 days ago)

No, that means you falling into author’s bait where they misuse term “delete”. Refactoring is not equal to deleting. One can be result of another. But the truth is that extendable code needs to be modular to be extendable. And modular code is easy to refactor. Author couldn’t not name it “Write code that is easy to refactor, not easy to extend” coz it’s even more dumb

[-] Lysergid@lemmy.ml -3 points 3 days ago

No, title only

[-] Lysergid@lemmy.ml 5 points 3 days ago

See no problem as long as person genuinely likes branding, not because “flex”. For example i have Adidas Original hoodie and I like it has huge logo coz it’s iconic design of hoodie from golden era of hip-hip and break dance. I would never wear same from other brand or even “three stripes” logo from the same brand.

[-] Lysergid@lemmy.ml -3 points 3 days ago

Right, but my initial comment was about article’s statement being wrong. Refactoring in the way you described will make code harder to delete which is bad according to the article.

[-] Lysergid@lemmy.ml 3 points 3 days ago

I don’t understand too. Are you suggesting me to drop bunch of features in the product?

[-] Lysergid@lemmy.ml 18 points 4 days ago

TLDR;

My current project has mostly easy to delete code and not easy to extend. Why? Coz shit was copy-pasted 50 times. It’s not fun to work in this project.

[-] Lysergid@lemmy.ml 1 points 1 week ago

Post commit hook to push + always squash on merging feature branches

[-] Lysergid@lemmy.ml -1 points 1 week ago

I’m not dying, or was that a joke? Then you are bloody stupid

[-] Lysergid@lemmy.ml -2 points 1 week ago

Do you take everything written on internet literally?

[-] Lysergid@lemmy.ml 3 points 1 week ago

While I agree that if you are dog shit you can not expect people wanting to be with you. But your judgement is one-sided. Entertainment also made people believe every successful, jacked, Hollywood star wants to be with average Jane coz she is princess. Not all problems of zoomers created by zoomers

[-] Lysergid@lemmy.ml 23 points 1 week ago

I mean, mom could be right. Maybe there’s a rule on router to block Fortnite servers after 21:00. She just doesn’t tell that she the one turning it off

[-] Lysergid@lemmy.ml -1 points 1 week ago

He just applied Russians’ favorite soviet era saying “those who is not with us is against us”

10
submitted 4 months ago* (last edited 4 months ago) by Lysergid@lemmy.ml to c/programming@beehaw.org

Hello my fellow, lemons? I have this problem in my current project I’m out of clue how to approach it. Maybe someone had similar experience and can give an advice.

Our requirements captured in JIRA. Throughout years we accumulated thousands of user stories. Say suppose following naive requirements team knows about:

  • Day 1: create home page
  • Day 20: create profile page
  • Day 50: add green footer to all pages
  • Day 100: create admin page Day 150: change footer color to blue

Now I’m doing refactoring (yes, I know, this is the actual problem) on day 400 and noticed that footer on profile page having green footer. Because requirements are just set of individual statements not consolidated with all history of system no one on the team knows why is that, is it bug or requirement did change on day 300 but we cant find it now.

When I worked in Waterfall we had BRD and FRD stating current actual desired state of system which was “reduced” from individual requirements which were coming in throughout project life. When in doubt devs can check FRD and not only know how system expected to behave but also which are other parts of the system that will be affected. How is it in Agile? To my understanding FRD is not a thing in Agile. Do I need to scan through hundreds of tickets and hope I didn’t miss anything every time i’m doing any non-trivial change to system?

413
view more: next ›

Lysergid

joined 1 year ago