skysight-inc/HackerNews huggingface dataset:
Show HN: A quizbot powered by Twilio
Hi everyone, I am a new to OSS development and wanted to create something that we could use at work. The idea was to make a framework that could be easily reused by someone with some ruby/Sinatra development experience. I have included documentation in the github repository that will take you through everything from signing up for a texting number to populating the quizzes.

Scenario---
Imagine you are in your doctor's office and you see a poster that says:
"Text FLU to 213-263-5445 to test your knowledge about the flu." (this is a working example)

It also will work as a lead generator for those interested in marketing. Let me know what you think.

Feel free to reach out to me at: http://robotscissors.com/contact/

Christopher
This is just the university demanding others do their work for them. Catching cheaters is a part of the service universities provide, and they want to push that cost onto others.

You talk as if cheaters haven't existed before. As if this is new. You cannot prevent this market from existing, the university simply needs to check.
IMO Go is in Go's way if becoming the next Java.
Form designers produce their own issues like compatibility between versions, poor interactions with source control and poor responsiveness.

I don't see an issue with creating UI's in code, with a decent API like Qt and Gtk provide it's quite straightforward. Why should UI code be treated differently to other code?
Imagine that the year is 1999, tech stocks are constantly discussed on HN, and someone says "in a few years most of these companies will be gone". Ha ha ha ha ha....

Today, someone (me) says: in the future, most cryptocurrencies will trade at ~$1 per coin (BTC, ETH, ...)
You claim that it is “totally irrelevant”. A Firefox maintainer, even in passing, claims otherwise.
MS Office skills lol.
It depends on how many jobs you've had and how old you are. If you have 3 jobs each being 1 year that would be a red flag. If you have 10 years of experience, 1 job for a year and the other 2 split across 9 years I would be less concerned.

An outlier versus a pattern is where I see a bad situation versus a concern for hire.

Personally, spending <18 months in a company or on a team doesn't yield enough time to accomplish much. It also doesn't afford you ability to learn from your mistakes and mature.
I don't have examples that come to mind of "red flags" on resumes that are otherwise reasonable.

I approach resume screening as a way of qualifying a candidate, not disqualifying them. I'm looking for positive signal, not negative. Do they have experience in the domain or technology I care about? Have they worked in teams and environments that would indicate they could succeed here? Are there are any notable successes, or interesting hobbies or side projects that make them stand out? If they clear the bar, I move to a phone screen.

It's not until much later in the hiring process that we start to look for "red flags" that might indicate something is amiss.

Depending on the volume of qualified candidates and number and urgency of roles available, I can dial different stages of the funnel up and down to optimize for efficiency vs. hiring speed (though the bar to get hired remains the same regardless).
> Yet every day there are stories (such as this article) showing crypto becoming more deeply ingrained in mainstream circles.

For all intents and purposes, this is fake news. The value in GS opening a bitcoin trading operation is mostly in them publicizing and having people write articles about it. It looks like they're on the avant-garde of new technology and prospective hires - especially the engineers and techies - pay attention.

Are they actually opening a trading operation? Probably. But as the article points out - its far less glamorous than it sounds - some new dude is sitting on the FX desk waiting for compliance and regulatory approval. And the truth is - many hedge funds have been trading crypto for years now - and I'm pretty sure other bigger broker dealers have gotten into the game already as well.
I wonder what % of that 62% are actually net taxpayers?

http://www.taxpolicycenter.org/taxvox/closer-look-those-who-...

http://www.pewresearch.org/fact-tank/2017/10/06/a-closer-loo...

https://taxfoundation.org/distribution-tax-and-spending-poli...

>American’s lowest-income families receive $5.28 worth of government spending (federal, state, and local) for every $1 they pay in total taxes.

Can't be hard to find enough people willing to vote for more benefits, especially if they know they aren't the ones paying for anything.
> lots of short stints employment. It costs a lot to find, hire and on board someone. Ideally I’d like them to stick around for a while.

This is a self inflicted problem across all companies. As long as companies are not willing to pay the market salary, people will move elsewhere.

> - poor formatting. If they don’t care enough to make their resume look clean and neat, why would I expect them to care enough to be thorough in other jobs. I don’t care too much about the aesthetic style of the resume as long as it is clear and consistent.

As neat and tidy as the resume is, certain employers are looking for buzzwords. So if those buzzwords aren't on the resume, it gets to meet the circular file.
The price of cutting off analysts? For Tesla, it's $2B
False. If you check Intel ARK, you can see, for example, the i7-2860QM has a max RAM of 32 GB (and this is a processor from 2011). Heck, the i7-8809G supports 64 GB.
This sure seems like a case of looking for a problem to justify the solution.
> Having it seem like a bug would be an effective way to block it intentionally.

Just like how only the true messiah denies his divinity, it doesn't give innocent bugs much of a chance.

In fact, now we can show that all bugs are suspicious, with apologies to the interesting number paradox:

The least intentional looking bug is the most effectively hidden, and therefore should probably be suspected of being intentional. Since it's now suspect, it's longer the least intentional looking bug, so the next least suspicious bug suddenly deserves a bit more scrutiny, and so on.
As a heads up it doesn't look like there is any sort of job posting link on the site.
If it's short, put an explanation. If it's contract work, label it as such. "Example, Inc. January 2018 - May 2018 (contract)." If the company folded or otherwise, you may opt to indicate it, or mention in your reach out to the company.
> what a mess doing what seem like simple file operations is

Proper handling and reporting of hardware-level errors all the way up through the stack (driver, block layer, filesystem, C library) to the application so it can recover in a reliable way is not a simple operation!

Simple operations are open/close/read/write. Those work. Until they don't, then you need to know how far back the operations you already did and "assumed" had worked didn't. And in this case the promise made to PostgreSQL by fsync() wasn't as firm as the "obvious" interpretation of the documentation would lead one to believe.
Could he be including revisions in those numbers?

There were six battery sizes on this vehicle. The largest is almost twice the size of the smallest. They may have modified the design several times to either fit or support different battery configurations.

Maybe some unplanned changes around 120/230V and safety?
this genuinely looks like a dope product.
Are you looking for a 1 day “mentorship” or a continual program?

I’m guessing since your coming at this issue from a corporate position, maybe helping them with skill towards employability may be helpful?

If 1 day, then consider some of these items to include in the schedule:

- provide examples of possible career paths. meet other employees and learn about what they do and education/training needed to get such a job

- introduce them to basic company etiquette: how to dress/introduce themselves when meeting an interviewer, what is appropriate language for a business email, etc.

- have them work with you to figure out/solve some simple, manageable problem. It’s important to find a task that has a clear reason and can be achieved within the short period of time. This could be anything from building a rack of test computers to designing a widget.

- ask them to design a team of people to make some sort of product they would be interested in. Have them describe what types of people they would want to have in the team and why they would want such people. This could be used to demonstrate introspection, a valuable tool in self help/learning.
This is highly contextual. I've got a series of 3 month stints on my CV as I'm a contractor. I usually come in to fix things, but by the time they call me in most of the money has been spent on shitty agencies.
I'm sorry, but some of my github activity is best be kept private.
Reported malicious module: getcookies
Thank you for this. The Efti course looks great.
I wonder?

Unreliable but redundant commodity grade hardware pretty much allowed "cloud computing" to eat 99.9% of "big iron" sales.

I strongly suspect what Google does internally with software defined networking looks a lot closer to what these people are doing than the traditional "buy a small number of powerful-but-expensive entrenched vendor network hardware" approach.

This mesh is kinda the network equivalent of autoscaling or autorepairing cloud computing strategies that are so common these days. Once this grows to 2 or 3 IXP connections it won't surprise me much to find they stomp the traditional ISP model reliability-wise, and if they can build that "virtually", where they don't need much more than a bunch of somewhat transient mesh participants with a few medium reliability "super nodes" which are mostly completely remotely configurable...
The storage has anomalously high latency and throughput variance with some patterns that you don't see with non-virtualized storage and a modest degradation in average performance. This is expected, but it makes it difficult to schedule I/O efficiently. This is more noticeable if you are doing direct I/O because having a VM intercept your storage access defeats the purpose.

What was surprising is that the direct I/O behavior appears to be conditional on whether you are accessing the storage through a file system. My database kernel is block device agnostic, using files and raw devices interchangeably via direct I/O. Against expectations, when we accessed the same virtualized storage as raw block devices, the behavior was like bare metal even though we are running the exact same operations over the same direct I/O interface in a VM. Basically, the only difference was the file descriptor type.

I'm guessing that file systems are virtualization aware to some extent and access through them is actively managed; raw device accesses are VM oblivious and simply passed through by the storage virtualization layer.
Ah that's a really good point!
In my mind the main contention is the difference between assets that exist entirely within the ledger (BTC, ETH, CryptoKitties) and assets that purport to reliably track some physical asset. Mathematical certainties about cryptographic security don't help reconcile the reality of meatspace with the state of the ledger.
I've said it before and I'll say it again: Modern filesystems straight out expose the wrong API for 99% of applications. App developers almost never think of data as a stream of bytes. We think of data as a set of records. Values in the set change through atomic modification events.

The fundamental API primitives should be atomic changes. Atomic write (bytes), and atomic append. The funny thing about it is that POSIX already supports basically this API (datagrams) for both IPC and networking. It just doesn't support this API in the one place it would be most useful - the filesystem.

Ideally I want:

- Write() to be blocking / atomic by default. Don't return until data is safely committed.

- A transactional API: begin(fd); write(); write(); err = commit(fd). If any error happens, commit returns the error and none of the data is stored.

- An IOCP-style API for non-blocking applications. This is the API databases want to use, with the loop being <get network request>, <write data to filesystem>, <yield>, <get write completion event>, <send confirmation to client>.

- Deprecate fsync & friends. If you don't want to wait for the data to get committed, write in non-blocking mode and ignore the completion event.

Solving this problem in end-user applications is really hard - almost no applications implement atomic write on top of filesystems correctly. And they shouldn't have to - this should be the job of the filesystem. The filesystem can do this much more safely, with better guarantees, better performance and better error handling. Modern filesystems already have journals - buggy reimplementions of journals in userland doesn't help anyone. "Do not turn off console while game is saving" is an embarrassment to everyone.
Boycott all AT&T services we can if they are blocking. Mobile + DirecTV too.
Any career longer than about five years that has a focus on a single technology or language with no attempt to branch out or learn new things. Especially for those without a comp sci degree.

For example, if your resume says you're a "SharePoint developer" or "Java expert" it's automatically suspect. I've worked with too many people who only know a single thing and are trying to ride that train as far as they can.

Those people have a great first three months if the job is for their exact skill set. But anyone more well-rounded will run circles around them after that.
Be careful with the "photo" bit. Some parts of the world include photos on resumes as a default, along with age and marital status. I still dislike seeing them on principal, same reason I liked Hired.com's "hide name" option to help remove biases in the resume screening process.
Announcing the deprecation of GitHub Services
I was using 1.1.1.1 with AT&T Fiber and it stopped working. I didn't really question it, I figured maybe something went down at Cloudflare so I just switched my Mac back to using the defaults again. It never even occurred to me that AT&T might be blocking it.

Maybe stupid question, but why would AT&T block it?
@mbeissinger thanks, great to see Lobe have low levels for play.
How would it make sense to block it only on a small fraction of their entire network? It wouldn't accomplish anything.
The resume that lists every version of every library, database, IDE, programming language, development tool, browser and Microsoft Office product the candidate has ever used in any job for however briefly.

I'm not seeing these often these days, fortunately.
>Bitcoin is anything but it was it was supposed to be

Bitcoin was suppose to be an open, peer-to-peer, decentralized, self-sovereign value transfer network. After GS facilitates BTC trades, bitcoin will be an open, peer-to-peer, decentralized, self-sovereign value transfer network.
"It's Wagile!"
It also highly depends on where you were working. Bouncing between Google and Amazon and Cisco and IBM at 9 month intervals is a pretty big WTF. Going between a few series A startups in the same period of time might be perfectly explainable.
1. Some links on the resume (github, portfolio, linkedIn) return 404 or access denied. This is suprisingly common.

2. Little facts / actual performance data, and over use of words such as "passionate", "strong", "self-motivated", "success", "thrive", etc when describing themselves in the resume.

3. Changing jobs very frequently and no consistent theme in jobs, say 5 jobs in 5 years, one in A.I., one in e-commerce, one in gaming, without specific pursuit of interest.

4. Have a big, long "technology used" for a project. For example, "technology used" in a project includes "Python, Java, Javascript, HTML, CSS, jQuery, SQL, C#, Django, Messaging, C, Bash.."

5. Too specific on trivial details in a large project, such as "work on JSON network request and return error codes to frontend".

6. When sending your document, try sending a PDF but not a .docx
In general, anything that is a red flag is probably something I would just clarify in a 20 minute phone screen. Most of the time, what looks like a red flag on a resume has a good explanation. That being said, the two that come to mind that I've seen the most of are:

- Not taking direct ownership of achievements (e.g. I was part of a team that did x). I don't care what your team did, I care what you did even if it's less impressive.

- Recent Coding Bootcamps. Not necessarily a no go, but I've had very mixed results with this one, some good, some bad. This will probably get me to look at what you did prior to software development and evaluate if you are a capable person in general.
> This is a self inflicted problem across all companies. As long as companies are not willing to pay the market salary, people will move elsewhere.

Why do you say this? Surely underpaying people is one way to make them leave but not the only reason. Some people think “the grass is always greener” elsewhere. Others don’t last long because they are not easy to work with. Others are not great employees and so are encouraged to move along sooner rather than later. Lots of possible reasons. Most do not signal the type of person I want to hire.
They want you using their DNS for traffic snooping?
PWLSD (Papers we Love - San Diego) is meeting tomorrow and has some really cool people & beer. I'm a tall white man with black glasses who will likely be wearing a blue sweater - hit me up and ill talk your ear off!
>someone (me) says: in the future, most cryptocurrencies will trade at ~$1 per coin

Will you sell me a call option?
I'd like to know if this will help enable support for more authentication methods at boot time for unlocking full disk encryption, such as Yubikey challenge-response or smartcard PKCS #11. Sort of a drag if you're using token-based login but you still need to memorize a password for FDE.
Anything containing Ninja or Wizard
Mesh networks are going to be incredible when they're widespread!

It's truly superior to centralized control by ISPs/Governments and the world will be grateful for this after this whole net neutrality debacle recently.

You guys are brilliant and doing an amazing job and I'm grateful people like you guys exist!

Thank you for the response!
* Lots of typos. One is fine. Too many suggests someone who is poor at English communication. It doesn't matter how good someone is, if they build the wrong thing.

* Generic boring template-ish resume. Usually these guys don't care much for craftsmanship.

* Too much specialization. 80% specialization is fine, just not 100%.

* For startups, a history of only working at big companies. Especially at the management level, where they tend to overspend and frustrate programmers.

* For larger teams, someone who has a history of only working solo. Some of these guys refuse to communicate, attend daily stand ups, or do daily commits.

* Putting a salary history in your resume.
Do not underestimate the importance of Unix familiarity. I encounter engineers every day that don’t understand command-line flags or how to use the shell, and a big reason for this is people coming from a IDE/Windows/MSFT world that does not teach these skills. There’s a considerable gap of training between “C# developer who has only used windows” and “developer who has used C# and has used a command line”.
Why would you treat gaps in employment as red-flag ? Do you expect everyone whom you are interviewing to be like you ?
This looks neat, think it'd do well with upcoming projects like Star Citizen from CIG? Physics sims have to be limited dramatically atm.
Have you watched David Beazley's talks about using generators to implement coroutines? That might give you a similar pattern to goroutines. If non-blocking IO isn't the challenge, do you make use of the concurrent.futures module?

While I also encounter efficiency issues, most of them are frustrations with the overhead of serialization in some distributed compute framework or the throughput of someone else's REST API. As much as so many people complain about the GIL, it's never been a blocker for me (pun intended). Perhaps it's because my style in Python is heavily influenced by Clojure.

Now that I think about it, Python's string processing is often my bottleneck.
...mmhmm, look dude, I do iOS/macOS development as well, and I've corrected you in a few threads around here already. I'm very acutely aware of how UINavigationController works. I've worked on ports of it for React Native, and even ported it backwards to macOS.

All the JS in that package is doing is driving the native interactions on an in-memory UINavigationController. I've used this in recent contract work where I can confirm that the title handling and animations are the same as what you'd get with a stock UINavigationController. That project is not replicating the behavior in JavaScript, contrary to what you seem to be implying - e.g, tapping the status bar does indeed scroll shit to the top. It's all driven by JS that simply calls the native layer code.

There are a lot of reasons to prefer the Apple dev ecosystem on a native level, but this is a moot point at the end of the day.

Finally, look... I was your age once, and believe me, I too thought I was an expert when I was in high school. Age and time are gonna show you otherwise sooner or later. Blind allegiance to a particular tech stack isn't healthy for your career, and throwing this stuff in every thread you find just gives a really bad image to projects that are starting to beat [Apple/Qt/etc]'s dev environment at their own game. These environments need to step up their game to stay competitive, and plugging your ears (and giving this fodder to everyone else) and pretending otherwise isn't helping anything.

This is almost willful ignorance on the level of Twitter's Cocoa community.
> "career objective"

is interesting to me because that's usually one of the first things I'm asked when interviewing.
People here comment about how python is slow, but even fast/slow is I'll defined in my opinion. You don't see people hacking tensor flow (generally) in native languages to speed it up, they just enable CUDA. I'm imagining fast definition is limited to massively parallel server workloads with io.
when 1.1.1.1 was first announced a few weeks ago, many people pointed out at the time that it was already blocked because so many people had effectively polluted it by over-using it for demo examples and testing traffic. CF announced they knew this and intended to do a project analyzing the data. Perhaps this done, whether conveniently or not, with the same intention. We'll see if they reverse it.
Yes, you can attach your Bitlocker recovery keys to your Microsoft account. I trust them well enough, since my threat model doesn't include state actors or MS themselves--if they really wanted my data, they could just ship an update to my machine while everything's decrypted anyway.
It's almost trivial for computer vision to recognize a child -- we already have backup safety cameras to protect children (among other things), why not a backseat cam?
Depends on context. If someone is a consultant/contractor, short stints are ok. But then have a clear reason why they want to go back to standard employee.

If someone has a number of longer stints, then a short one here or there is no big deal. But I want their resume to tell a story.

Don’t be afraid of explaining circumstances in a cover letter.
I usually look for some obscure buzzword which I know something about and ask the candidate about it. For example, if he has Foo on his resume I will ask a concrete technical question related to Foo. Oftentimes it turns out the only experience with it he or she has was in a college, years ago. For me, that is an indication that candidate tends to exaggerate his knowledge and whatever else he lists on his resume has to be taken with a grain of salt.
Would you say those who do recent coding bootcamps are worse than those recently graduated from college?
Yep, you'll be surprised how many candidates list this.