nicksardo

15 ms·

1.
by nicksardo 4y ago
Thanks for the feedback! 1) Click on the stopwatch timer title; you can edit it in place. Indeed, discovery of this is not great. My UX designs tends to be quite minimal. I'll try to make this more obvious. 2) I'm considering buil
2.
by nicksardo 4y ago
I'll do that, thanks. I've never had feedback that's indicated people wanted to know. It uses NTP's clock synchronization algorithm to get the servers' time. This is done over a websocket as it's twice as fast
3.
by nicksardo 4y ago
Shameless plug: I created https://chronograph.io back in 2014 so people can share accurate , live stopwatches and timers. Other sites "share" by putting the start epoch & duration in a url querystring; Chronograph
4.
by nicksardo 4y ago
Former Google engineer here. My team used the open source Go B-Tree implementation but I replaced it with a non-interface version over a year ago because of performance issues. The lack of generics at the time wasn't a problem because
5.
by nicksardo 7y ago
Many years ago I created a site that similarly syncs time between server and clients for the purpose of sharing stopwatches & timers. I found that using a websocket connection yielded a higher precision. https://chronograph.i
6.
by nicksardo 11y ago
https://github.com/nicksardo/jsonpath can pull out parts of a JSON document without unmarshalling.
7.
by nicksardo 11y ago
Indeed, it's frustrating when you're reading flat files of code. When reading foreign F#, I pull the code into Visual Studio so I can hover over the variables. It'd be quite convenient for GitHub to provide the type informat
8.
by nicksardo 11y ago
If a developer is frequently ignoring returned errors, then they have larger problems and it's their fault. Panic was not added to assist lazy programmers. Even though some API has solidified, an author could later add different return
9.
by nicksardo 11y ago
I strongly disagree. The package author means the error will be nil when the secret is 32 characters long; he doesn't mean you can completely ignore checking it. Regarding when to use panic: "The convention in the Go libraries i
10.
by nicksardo 11y ago
Guns don't make me feel safe. Being properly trained on how to use defensive force makes me feel safe. The error in your logic is that you're imagining yourself with a weapon, which indeed, is laughable and provably unsafe. Edit:
11.
by nicksardo 11y ago
First, your statistics are moot. As I just said, a statistic is still a risk. A risk I will not take when it comes to family. You play it your way; I'll play it mine.
12.
by nicksardo 11y ago
When a stranger is in my home at 3am while my spouse and two kids are upstairs sleeping, I won't risk judging what he/she will or will not do. Even if I were alone, I wouldn't take that chance. My intention is not to preserve
13.
by nicksardo 11y ago
The use of `append` is absolutely clear. It always returns a new slice; the compiler forces you to take the value returned. What scares you is the possibility that the underlying array may be copied to a newer, larger array giving enough s
14.
by nicksardo 11y ago
Regarding toArray, the creator probably went that route to be more performant. http://jsperf.com/array-prototype-slice-call-vs-slice-call/1...
15.
by nicksardo 12y ago
Used to use PasswordBox but then switched to 1Password - I'm much happier. Unlike my experience with PasswordBox, I can keep my data on my cloud and can export any/all my passwords. However, my 1password trial has expired and I
16.
by nicksardo 12y ago
I care about these things specifically because the IRS doesn't tax it. I save about 6k per year because my startup feeds me 5 lunches/3 dinners per week and pays for my public transportation. That's probably ~8k pre-tax dolla
17.
by nicksardo 13y ago
I disagree with most of what you said. "exception oriented" programming is dirty. It's especially filthy when your expecting exceptions from a database for these reasons a) Returning errors to the user is asking for a slipup
18.
by nicksardo 13y ago
SQL constraints are a given; always use them. However, it's best practice to also validate your data before it gets to the database for several reasons. A) Depending on a database check constraint failure is analogous to using a try&#
19.
by nicksardo 13y ago
He's referring to accounts for formspree, not the static sites.