HN user

halisaurus

160 karma
Posts5
Comments54
View on HN

Ping the clients and average out data from clients near the lat/long sent with the request and compare to the client in question.

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.

Those people usually go for the low hanging fruit that appeals to most people like preventing the mentally ill to buy firearms. However it is important to note some unpleasant facts like the fact that 11% of Americans are on some antidepressant and probably many more were on some anti depression medication in the past [0].

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...

I also gave Hyper a solid go but found the native Terminal and tmux/tmuxinator gives me all the same (worthwhile) utility without some bugs related to pane management and history preservation. With Hyper I regularly experienced history being cleared and lost even in the same pane/window, but I couldn't force replication which made it more frustrating. Also, it has some strange feature (?) that can spawn a browser window inside the terminal but I can never figure out how to escape it.

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.

Stressing the "deliver quickly" aspect of any language, if you're actually trying to deliver for a business or with a team of people, is extremely destructive short term thinking. And yes, sometimes, in rare cases, it may be a necessary evil, but I think it's become the norm with words like "agile" being thrown around as synonyms for "don't have to write anything down".

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.

I built the Chrome extension [0] for Pesticide[1]. It toggles the Pesticide CSS in the current tab making it easier to visualize the placement of elements in the DOM. Useful for front end debugging.

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...

[1] https://github.com/mrmrs/pesticide

I use `git add . -p` which allows me to 1) selectively create my commit, and 2) re-read what I've changed to understand it all better. I agree about wholesale adding, but of course there are exceptions when you already did `git diff` Or something.

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.

I was just looking at your pricing. :) All in all Netlify does offer a compelling service for this scope. I'm also interested in the Pro tier being free for OSS, that's fantastic!

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.

Nice guide. I have my personal site on the same AWS S3/Cloudfront combo and I effectively only pay for the domain name ($12/yr) and certificate (~$35 for a 2 year?). AWS invoices me monthly for ~$0.05/month in fees with a credit that erases the charge, so I'm not actually paying for hosting. If you're unfamiliar with AWS it can be daunting, but it's mostly initial setup to get it working then uploading changed files whenever you update the site, which was a better choice for me than $5/$10/whatever each month for little or no additional benefit. I'd recommend it for anyone with a static site. I think you'd need a lot of traffic and/or updates to the site to incur $10/month in fees on AWS.

Definitely a step in the right direction, but very difficult to read. The font is far too small and all links are similarly too small to allow easy tapping.

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.

Assuming functions count:

    # 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.

Twitter can fix this with an existing feature that has perceived value to the user base: Open up being a "Verified User" to anyone who uses a real name (or otherwise proves a real identity). Then, allow all users to filter notifications/replies/viewable tweets by whether or not someone is verified. It doesn't remove the option to be anonymous, but others can limit their interaction with anons if they choose. (They could even charge for verification I suppose.)

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.

If you didn't know you can put ssh configurations (hosts, ports, keys, etc) in ~/.ssh/config. You can use it in scp like 'scp prod:path/to/file path/to/destination'. Not sure if there's a pro/con to mapping an alias.

Sure it's not exactly an alias, but this is basically just splitting the usual `git status` output and coloring it. I have similar functions in my .bash_profile for git and it doesn't require node. Consider this: I can easily scp my dotfiles to a server and use all my shortcuts. To use this I have to install Node, npm, and this package to gain a couple of new shortcuts that make existing functions a little prettier.

Thanks for the response. (And responding throughout this thread, too.) I see the point in using this for dependencies, and there are other apps like Google Analytics that have minimal configuration to use.

Sorry, I don't understand your Bootstrap example. If I'm not technical to "install" BS (script/CSS tags and uploading files to a host) then I'm probably not technical enough to use Bootstrap's CSS/JS components by writing HTML or little JS snippets. What real benefit is the one-click install if that's (probably) the easiest part of using a JS/CSS library?

Edit: It's not your Bootstrap example, it was the original question. Sorry to confuse that.

I've had this question asked of me before, and it seems valuable for the same reason as the question on the article: It's an opportunity to show passion/enthusiasm for programming work. I think even novice programmers who love to code will have that one bug that got them. Even if the story is anticlimactic ("I missed a semicolon"). iMo, explaining how they got to that conclusion in a logical, positive way, didn't give up or just copy/paste the answer, and ultimately moved on in the project with a new lesson in syntax is the real "passing answer."

That description is a big turn off. I don't need RealTalk to communicate with businesses on my smartphone. I already have a phone, email and web access on it. Maybe even a dedicated app for that business.

Why not just say "RealTalk lets businesses handle customer service via SMS"?

The ability to export and "increased" storage for paid accounts, but neither are expounded on. How is the data exported? How much storage does each tier get?

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.

It's alluded to in the article that outdoor fields and green jerseys are the hardest. For outdoor fields the lighting is affected by the time of day, cloud coverage, players moving along the field, and plenty of other things I'm sure. It says they spent a lot of time creating a unique palette for the fields and that domed stadiums were preferred by the engineers on site. Indoor lighting probably reduced the shadows a lot.

Right, but the two "No" options don't leave room for having a positive outcome and still not being an active user. What about, "No, because my current job or state's laws or inability to access marijuana prevent me from using it." Or, "No, but I would if I could."

In a way it's funny, either you hate it or you still use it on a regular basis.