suppressingfire
suppressingfire on Hacker News
In the meantime we have Lyft and Uber. I don't think we need fully autonomous vehicles to want to eliminate the need to own a vehicle that needs to be housed and stored for 95% of it's lifetime. Waiting for an L4 transport service is just an excuse.
I tend to agree. While I find it painful to hear criticism when I inadvertently use words or phrases that are taken hurtfully, I nevertheless would prefer to be offered a wider perspective about how my words and actions are viewed so I can more clearly communicate in the future making fewer verbal blunders that detract from my point.
"you all" or "youse" can work as reasonable alternatives. I haven't tried "tons" since I've never actually heard it "used in anger."
One less fraught, but equally confusing terms are "a couple" vs. "a few" vs. "a handful" (some believe "couple" = 2 whereas others treat it and the others as explicitly more fuzzy). Often it's best to just assume as little context as possible and be a little more explicit and verbose.
To be fair, I see plenty of folks in open office settings that DGAF about that and looks at memes or YouTube or Reddit on 30" monitors visible to any passers by.
I've seen it go both ways. Definitely agreed that it's a human process and it can be gamed a bit. There are (or had been in the past) some checks on that with secondary committees that re-reviewed primary committee results (not just appeals of negative cases). I think the removal of those checks and move to org based promos has allowed more of what you described to take place in unfortunately.
There were lots of states with similar problems in the 70s. Others solved it better (e.g., NY Star program that helps specific classes of people that need help). Prop 13 was a chainsaw solution to something that needed a scalpel.
As a kid, we ate at Ponderosa quite often. All you can eat soft serve.
Though I recall putting some chunked (presumably canned) pineapple on my plate once, taking it back to my table, and chomping into it before realizing it had (apparently) fermented.
We still went back months after month.
The one in my hood closed overnight inexplicably before we ever got to try it. Oh well.
Could be that the plans or companies offering coverage in her region have changed from year to year? While I wouldn't call this being "dropped" others might.
Another possibility could be due to fraudulence during the application process?
But yeah, grabbing at straws here.
IIRC, doordash used to provide a live map a couple years back. I'm guessing they have all the data and could share it again if they desired. Presumably they have some product reason for not offering it.
i.e., distributed systems.
Also, SMS is not guaranteed to reach the recipient in any reasonable timeframe.
Also, if they're supporting desktop clients I again call shenanigans on your argument.
Mobile web is an edge case, too.
Shenanigans!
I call shenanigans for two reasons:
1) you can never assume a recipient ever has their phone on, with them and in a non-silent mode
2) users can disable push notifications for individual apps anyway
"It was introduced with those words. They have changed since (a long time ago too)."
While I broadly disagree with the OP, I don't think this critique resonates.
The OP argues for more communication and collaboration throughout the day: Don't wait for the standup if you're blocking. Share status information immediately. Keep up to date with teammembers constantly.
Also, dammit, it's not a sync! And if your team has so many members that it last 15 minutes, there are too many people on the team (or the team is being too lenient with the format).
And protobuf.
No, wait, that was someone else.
:-)
You're totally right, the transcript is quite readable 1/1 Powered by Rabbit 0.9.2
The FSF is not a court of law.
As such, their opinion on the interpretation of the license has no particular standing. It's helpful that they're the author of the license, and if it came down to it in court, it may be persuasive. But another lawyer might have a different opinion, so the question of how it will actually be interpreted if two parties disagree remains open and unsettled. Therefore, anyone undertaking to release a bit of open code should consider the range of interpretations when choosing the license.
That's all that antoncohen was getting at, I think.
Naw, don't worry about it.
You're a great friend :-)
Hah. I like how the author pluralized "targets'" while keeping all the other facts intact.
My only problem is that it's marked "fixed." I'd rather the bug be OBSOLETE or WONTFIX (I guess LP's closest status to those is "Invalid" which is fine, too). That would short circuit most of the arguments about the fact that the desired action isn't verifiable, and anyone that disagrees would have to argue at a higher level: is owning the desktop/laptop market a worthy goal, especially now that OS X is a serious contender? Is it sufficient that Android is Linux-based in the mobile/tablet market?
Though to be fair, those that are interested in it probably already have it. I'd rather see a post about a concrete alternative than a direct link to some special offer.
I guess you're arguing that the upvotes are coming from happy users that are lending their support by clicking an up arrow. That just feels weird for HN.
I don't quite know why, but your post made me open up 4chan for the first time in years.
If I haven't made any progress since the last day, I just talk about what I plan to do for the upcoming day. I also might say "I'm still working on (the thing I was working on yesterday)". With a well functioning, trusting team that should be a perfectly reasonable thing to say every so often.
I think there's a stigma attached to the notion of the status meeting. Beyond that, at least to me, a status meeting is a kind of assymetric situation where one person with some kind of authority (manager, PM, ...) is trying to keep tabs on everyone else's work, where each attendee has to prove that they've been doing their job. In a standup, it's a kind of egalitarian environment where everyone is speaking to everyone else, and nobody is taking notes to report up the food chain.
Guava's Hints.tryParse is about as good as it can get in Java... Maybe it could return an Optional instead of a nullable boxed type, but the calling code wouldn't be much different.