If you need to be somewhere at 8:30 and the journey “takes 17 minutes”, one psychologically sets 8:13 as the deadline for leaving the house. You pick up your keys at 8:13, actually leave a few minutes later, hit traffic or take a wrong turn or two, and end up crossing the threshold at your destination fifteen minutes late.
It’s no big deal and quite a grumpy old man thing to say, and I also don’t know if tech is the root cause, but squeezing travel into unrealistically small and algorithmically created windows of time has killed most people’s sense of punctuality, including mine if I’m not careful.
There's more than one reason for that, here is one that might be easy to overlook when someone is critizising USA with good reason:
America is not perfect but as a citizen and compared to the bad old commies it was mostly really good.
If there are more commits for the same task, all of them bare the same commit message. After each review, we add a comment to project management tool. That way we focus only on newer commits when performing another round of reviews.
Every other attempt to describe changes and intentions in one line seems doomed to me.
Problem #2: It's expensive to support millions of users who post shit
Problem #3: Twitter's revenue base is too small for its cost base
Solution: Eliminate advertising and charge $20 per 1000 tweets. Free to read, costs a tiny bit to tweet.
People who post shit will disappear. People who have an audience and something to say won't bat an eye at this low cost.
If this weeds out 80% of the shit while keeping 80% of the good stuff, Twitter will simultaneously shrink their costs while growing revenues to become a sustainable business.
With this model, Twitter is a $1 billion per year profitable business [2] with a much higher signal-to-noise ratio. [3]
Improve the signal-to-noise ratio and Twitter becomes THE place to be for all kinds of communities. That means a return to growth and higher rates per 1000 tweets.
[1] https://en.wikipedia.org/wiki/Sturgeon%27s_law
[2] Start with 200 billion tweets per year. 90% are shit, and 80% of these go away, leaving 36 billion shitty tweets. 10% are good, and 80% of these stay, leaving 16 billion good tweets. 52 billion tweets in total, monetized at $20 per thousand is a billion bucks a year.
[3] Signal-to-noise ratio before is 1:9, after it's 1:2.
BTW, I don’t know if it’s coincidental but just yesterday I received a notification from Yahoo to disable access to Mail from third party apps.
I want to be able to modify/add code, try it out, then rewind, and try something else. Then save my changes once they work perfectly.
Simply setting breakpoints and watching variables is nice, but I can do basically the same thing by echoing/console.log'ing things. If you are going to go to the effort of making a debugger, then make it do something I can't do another way.
Having all the states and being able to see execution in the past blows my mind. Every debugger should support this.