Apply a max threshold to check if a client is reasonably close to potential "co-located" clients.
You can't shrink physical distance. Pinging a server in a nearby US city is 13ms. Hong Kong is 232ms.
160 karma · joined April 17, 2013
Apply a max threshold to check if a client is reasonably close to potential "co-located" clients.
You can't shrink physical distance. Pinging a server in a nearby US city is 13ms. Hong Kong is 232ms.
[0] https://www.dmv.ca.gov/portal/dmv/?1dmy&urile=wcm:path:/dmv_...
I'm not a doctor, but I doubt that, say, "mild depression" or "previous history of depression" is enough to be considered mentally incapacitated. Is every person on anti-depressants mentally incapacitated?
The article highlights suicide rates.
> In 2014, Veterans accounted for 18% of all deaths from suicide among U.S. adults, while Veterans constituted 8.5% of the US population. In 2010, Veterans accounted for 22% of all deaths from suicide and 9.7% of the population.
> Approximately 66% of all Veteran deaths from suicide were the result of firearm injuries.
https://www.va.gov/opa/publications/factsheets/Suicide_Preve...
Edit to clarify: ...without also requiring eye correction. Of course you can wear glasses to drive, but it becomes mandatory, and without that eye correction you cannot get a license.
I agree that my terminal shouldn't crash. I handle so many fundamental parts of my workflow in terminal so it has to be stable and efficient.
Unfortunately, this is pervasive in the "real world", especially with regard to client-driven (agency) work. Deadlines beat developers almost without fail. I agree that it is destructive short term thinking. Entire weeks of programming can be destroyed in a 15-minute phone call that (re)highlights a limitation clients either didn't account for in their specification (if you can call it that) or just chose to ignore.
This isn't to say that using a language or framework a developer is familiar with is baseless, but I've heard this advice before and see it reinforced often:
1 - Hire people not skills.
2 - Success is 90% preparation.
The extensions first implementation was basically just a ternary operator! Now it's got a little more to it, but it's still super simple.
[0] https://chrome.google.com/webstore/detail/pesticide-for-chro...
Side note: `git status` is not a good means of "knowing what was changed". I see others use it constantly (doing git status -> git add . -> git commit) and it'a sloppy IMO.
Curious if they've tried other pricing models. Beyond, say, 10 or 20 users the value proposition shifts against that pricing model IMO.
To be fair, setting up AWS for the first time is a real PITA and I happen to have had it all set up (IAM, buckets, command line, etc) already, so my barrier to entry was low. Had I known of Netlify when I first moved my site to AWS I probably would have gone with Netlify for the convenience and free HTTPS cert.
Also, enterprise AR ad placement, buying, and management software could be desktop software.
This comment form could also use work. It doesn't fit the width of the screen, so I have to pinch/scroll to see what I've written then maneuver back to type. Nor does it auto expand or allow manual resizing. Just trying to scroll risks pull-to-refresh in Chrome for iOS or some embedded WebKit browsers.
I'd also say the navigation could be addressed. The first comment about sizing is a start, but the separate site and account navigation lists don't have enough space now, let alone once you up the font. Some sort of collapsing/hidden/drop down menu might need to be considered if you intend to keep 8 independent links with sufficient padding for accurate tapping.
A good start, but still not there IMO.
# git branch ahead/behind another
function gahead() {
# use first argument or master
original=${1-master}
# use the second argument or current branch if not given
current=`git branch | grep \* | sed s/\*\ //`
compare=${2-$current}
# run git rev-list and capture numbers returned
result=`git rev-list --left-right --count $original...$compare`
# print numbers in a pretty message
numbers=($result);
echo -e "$Red-$Color_Off $compare is currently $IRed${numbers[0]}$Color_Off commits behind $original";
echo -e "$Green+$Color_Off $compare is currently $IGreen${numbers[1]}$Color_Off commits ahead of $original";
}
Edit: if it's not clear you would use this like: $ gahead #checks current branch against master
$ gahead development #checks current branch against development
$ gahead development foo #checks foo branch against development
NB: this is checking local branches, not remote branches.I'm sure plenty of "regular" people (i.e. non-celebrities) would verify themselves for the blue check mark. To date it's been reserved for select users and gained a value on Twitter. They could capitalize on that here very easily.
E: typo.
Edit: It's not your Bootstrap example, it was the original question. Sorry to confuse that.
Why not just say "RealTalk lets businesses handle customer service via SMS"?
Also, how would this play with a custom domain (if it's possible)? What about security; is anything encrypted or secured at all?
This looks really nice, and the editor is a pleasant change from the usual early-00's look of some PM software. But for services that I plan to put business assets in (like all of the company's shared knowledge) I need more information before taking the leap.
In a way it's funny, either you hate it or you still use it on a regular basis.