If you were 4 and now you are 44 then you might be an integer variable. If sister is also a variable, we don’t know when she was allocated. She might also be an integer constant in which case she’s arguably immortal.
Also, we first have to define more precise what ‘being 2’ means. If we just count birthdays and one of them is born on Feb 29th in a leap year, that person ‘ages’ with 1/4 of the speed.
deleted by creator
deleted by creator
I’m a Dev with no QA so i just have to be neurotically pedantic so nobody goes to jail
I mean, no, the tester didn’t say anything wrong here, and all of those (and more) are conditions one must take into account if one were to write a piece of software without errors
deleted by creator
I think it’s more about how testers always run into all the edge cases programmers don’t think about
Can confirm, not even an official tester (just an open beta tester) and have acrued a reputation for having a legendary bug aura that can cause catastrophic and previously unseen edge cases to occur just by opening the software (game)
I used to have a QA job. Can confirm, this is the soup in my head. That’s why I was good at testing. Also, that’s not your sister. That’s your trans brother, who we also love. See?
I’m a programmer and my answer would be more like the tester’s answer.
But okay I also used to be a tester so this comment is probably invalid.
Based on the only comparison we have, the OP is twice the age of their sister. so the sister is now 44/2, or 22. Easy problem.
ML in action.
Based on the only information we have, OPs sister is two. So the sister is 2. Trivial.
Ugh, this is what you get when there’s no AC.
Managers when a tester does this in a planning meeting, asking for more time to write better teats: 😠
Managers when a staff level engineer does this in a post-fuckup root cause analysis meeting telling everyone what went wrong: 🤤
Managers when the tester points out it wouldn’t have happened if tests for it had gotten written:
Probably? Nah mate, your box of stuff, has already been chucked out of the window… You are next
!lemmySilver
I wish I had a QA like this.
import birthday; let myAge1 = 4; let sisterAge1 = 2; let myAge2 = 44; let sisterAge2 = birthday.deriveAge(myAge1, sisterAge1, myAge2); print(sisterAge2);
Any bugs should be reported upstream. Please open a tracking issue to sync changes with eventual upstream fixes.
The API has the wrong abstraction and the type definitions fail to capture necessary information (such as in which year you were of the given age) and thus conversions can not be guaranteed to be correct
You could also simplify by saying that assuming neither of them are dead, at some point while he is 44 she will be 42. Whether or not she is actually his sister seems to be irrelevant, she was stated to be his sister, so regardless of biological data, it is being presented as a fact assumption.
The space stuff is not currently possible and can be disregarded as well.
Also misses the edge case where sister was born on a leap day
Or maybe in a country that recently switched from the Julian calendar, adding the possibility of >12 months between birthdays as described by calendar.
https://github.com/eggert/tz/blob/main/calendars has entered the chat.
Also, as ever, relevant XKCD.
Real talk: I wish more orgs place a high value on QA. A good QA team is worth it’s weight in gold and helps prevent a lot of stupid mistakes.