I'm surprised nobody made this joke yet...pic.twitter.com/cZRNAjhF2e
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
I'm surprised nobody made this joke yet...pic.twitter.com/cZRNAjhF2e
Lol. Took me a second.
And measuring impact is ...easy?
my most important metric: debuggability.
How do you measure this?
What about signal/noise or useful code/boilerplate ratio?
Agree, I think there is always a balance to strike regarding readability and the amount of information in a single line. Hard to make one generic rule the encompasses all scenarios. For me it's a mix of both: Amount of impact + noise ratio
Given your bitwise operator code golfing proclivities, I'm not surprised at all. 
If I put a random unmatched { in some code, it impacts 100% of the program. Does that count?
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.