> Building a real time ridesharing engine is not hard - I did it once
You did about 0.01% of the work.1,932 karma · joined February 2, 2011
> Building a real time ridesharing engine is not hard - I did it once
You did about 0.01% of the work.Doesn't mean I'm not cut out for software development nor that I can't deliver value to anyone else.
Nor does it mean I can't find a rewarding and interesting job that suits me and the lifestyle I want.
It's a common challenge for Elm beginners.
Though it does emit another message when rejection is handled asynchronously.
> var p = new Promise((_, reject) => reject('lol')) \
setTimeout(() => p.catch(() => console.log('handled')), 0)
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): lol
PromiseRejectionHandledWarning: Rejection handled asynchronously (rejection id: 5)
Consolation prize?Fortunately, most of the run of the mill promises I can think of off the top of my head get rejection handlers attached synchronously, like in upstream middleware. I might be drawing a blank, though.
Forgetting to handle rejection is probably the most common error I see when people post Promise snippets in #node.js. Silent failure is so deadly. "Why do my requests hang?"
What about all the small websites, from creative to forums, that aren't big enough to graduate from ads but can pay their own rent with them?
Seems like a net loss for humanity to lose them from the internet while keeping only the large businesses online.
Also, it feels wrong setting the iPhone down on a bar table or whatever. Either the touchscreen lays against the table or it's seesawing on its protruding camera lens.
Putting it in a minimal rubber case took an $800 load off my mind for $15.
option-u and then a vowel will create {ä ë ï ö ü ÿ}
option-n and then an 'n' will create ñ
Found this out while learning Spanish since holding down keys to select their alternate was way too slow.
For example, http://apex.run/.
Sometimes it rolls a yahtzee and the three people talking all have the same color and the same length of chars in their name.
I figure that even if the people talking luck out and have a shade of green like in my screenshot, it's still better than if they all fell into the identical green bucket.
And each person needs to care enough about IRC (e.g. run a VPS) to receive pings or messages while they are away and to see the message history when they return.
Maybe IRC is "plenty popular" which apparently means popular enough to find someone willing to shoot the shit with you if you're in one of its largest channels. But that's a far cry from "IRC is everywhere".
I use IRC every day. I'm just not left scratching my head when I find out that yet another ecosystem chose Slack/Discord over IRC. It blew me away when I saw how active Elm's Slack was while #elm is dead. But that's pretty much how it is with every community I'm part of with a Slack channel.
Sometimes people here suggest "maybe IRC is just for developers", but you can't even format a code block on IRC. :)
Meanwhile, Elm's Slack channel has more regulars than #node.js.
IRC is kept alive by a small holdout. I'm one of those people, but it's no mystery to me why nobody else uses it when I'm paying irccloud.com or running weechat-ncurses on a VPS just for basic features everyone expects from a communication tool.
'#' + username.md5().take(6).join('')
I did it for a chat I once built, users liked it, and it helps you keep track of who said what. Though I added some styling to keep it legible, like a 30% white blend, a stroke, and a drop shadow.https://dl.dropboxusercontent.com/spa/quq37nq1583x0lf/xf17fn... (not the best example since everyone happened to be shades of green)
Example: /r/@theymos/bitcoin. Now, instead of looking like Reddit's canonical Bitcoin discussion forum, you're reminded that it's just one person's forum at the mercy of one person's agenda.
If you're on the hook to sanitize all inputs, doesn't that mean you're not escaping output?
The biggest security mistake I've made so far in production was that one time I used an HTML templating library that didn't escape output by default.
I'd like to know if people are still getting that email.
The only ways I can think of finding the origin involve user error:
1. DNS history lookup where they're still using the same IP address.
2. Scanning the internet where they aren't ignoring non-Cloudflare
requests.
You can file an abuse or DMCA request to Cloudflare, but they only reveal your provider.Often by the time the abstraction is such a failure that it needs to be rewritten, it's evolved into its own system with a menagerie of hacks latched on to let it live another day. You're not going to just come up with a regeneralization because more often than not it's not generalizing anything anymore.
Seems a bit much to "throw up in your mouth a little". Premature abstraction and the high cost of indirection are responsible for some of the hardest problems in software and you don't offer a solution beyond "try anyways".
> Usually the person applying thinks highly of their
> ability to identify a DK scenario.
This is a critical component of the DK epithet, often accompanied by a tacky link to the wiki page.https://hn.algolia.com/?query=dunning%20kruger&sort=byPopula...
Google introduced nofollow in 2005 to either let people help fill a gaping hole in Google's tech at the time or for the smart marketing move of making people fixate on their magic attribute. Both under the guise that spammers would care.[1]
It's been twelve years.
The SEO advice industry and Matt Cutts' blog these days are probably like when I try to ponder why my cat scoots its waterdish around the room before it drinks: attempting to find backsplanations for the idiosyncrasies of a neural network that nobody quite understands.
[1]: https://googleblog.blogspot.mx/2005/01/preventing-comment-sp...
Imagine you're building the perfect internet indexer. In an effort to generalize your model, you anticipate a scenario where a nofollow link shows up consistently on various Wikipedia pages where it persists for a long time. What are you going to do? Ignore the link because, sorry, them's the rules?
Or are you going to realize that nofollow is about as useful of a signal as <meta name="keywords">?