@raymondh@dataclass@dataclass@delegate("seq", methods=["__len__", "__getitem__", "append"])
@delegate("counter", methods=["increment"])
class A:
seq: list
counter: SomeOther
Can save some more typing. Also don't know, why only for dataclasses. Delegation would be useful for any class.
Roborace is the world first driver-less/autonomous motorsports category.
This is one of their first live-broadcasted events.
This was the second run.
It drove straight into a wall.
@laurenweinstein@Grady_Booch@vkhosla It's prediction that doesn't take into account that listening music is also social event. If everyone would listen only to their own music there would be no concerts, less common topics to talk about etc. I think flying cars are more probable :)
I'm going to spoil it for you because it's so damn important.
Microsoft did a scientific study - based on MS Vista code and found that the best predictor of bugs was:
ORGANIZATIONAL COMPLEXITY
More people = worse code
More departments = worse code
Higher turnover = worse code
@mike_bowler@RonJeffries To be honest I've seen near 50% coverage only in ill assertion free testing cases. In TDD code it was rather near 90% and in legacy code near 30%. In situations of bet as described by @RonJeffries I would behave differently than in case of searching for a real bug.
@mfeathers@mtnygard Is hard to change a desirable attribute? I'd rather go in direction mentioned by @pbloemesquire. A lot of comments and assertions (not necessary long method). It makes me stop and think why so many comments and assertions in such short method?
@KentBeck If reset leaves tests untouched it would be great.
If it removes tests also I'll be annoyed.
If I wouldn't be allowed to fail my tests before writing production code I'd loose trust in my tests and won't write them.