skysight-inc/HackerNews huggingface dataset:
Psychopathy is a medical definition in a psychiatric handbook with specific clinical guidelines for diagnosis (https://en.m.wikipedia.org/wiki/Psychopathy).

You can't tell that someone is a psychopath without having actual psychiatric credentials and actually performing diagnostics on the patient.

"For example, if someone keeps talking over you, he's probably a psychopath."

I'm pretty sure that it does not suffice as evidence.

You're focusing on the wrong thing - on the specific action and not on the feeling it generates. A non professional individual seldom has enough experience on personality disorders to tell what exactly is wrong. This means collecting anecdotal evidence has little value unless one knows the subject really intimately. But one can trust ones feelings.

The key to identifying difficult people is first realizing that the interactions with the person leave you mostly feeling worse. Not in a single interaction, mind you, but over time. That is probably a good time to read a "how to deal with difficult people" guidebook and assess ones situation.

The diagnostics part should be left to professionals.
> 5. ...maybe if we build a big enough quantum computer we can overflow the universe's buffer.

Except black holes are a thing.
It's satellite from the network to the affiliates, but from the studio to the network it would seem to be much simpler to mail a tape or maybe use Aspera.
>The reason global namespace shouldn't be polluted is that it's so damn useful.

No, the reason is because the more interacting components you stick on it, the harder your code becomes to reason about.

It's more a restatement of the notion that software should be loosely coupled.
It's been like that for decades. Or do you really know what assembler your program compiles down to?
If you are interested in this topic, I recommend you reading Martin Odersky's papers on Scala design.
You posted an ad hominem attack on police in America. That doesn't even belong on reddit, although it's more common there.

That said, police in America are stuck dealing with the consequences of many short-sighted policy decisions. They are not properly trained for social work, mental health services, and so on.
CSCI 4035: Refactor Your Own Term Projects from Past Semesters
El Niño reaches 'strong' intensity, will dramatically reshape world's weather
Even more important than that for me (possibly for you too) is that you make sure that none of these pages make it into googles index.

The duplication of content (potentially sending the original pages down in search ranks) and the fact that you are polluting the organic search results for the sites you mirror could be a big issue for the owners of the pages.
The $5 USD retail looks suspiciously like $47.95, or am I missing something [1]? Could not see a sku w/out charger, though [2]

[1] http://www.amazon.com/d-light-Rechargeable-S300-Lantern-Char...

[2] http://www.amazon.com/d-light/b/ref=bl_dp_s_web_3023737011?i...
I understand your frustration, but the field has become too big for a single (average) person. When problems arise , you team up with someone who knows more about the issue or you learn on the spot. Nothing wrong with not knowing everything.
There are many things in AWS that are not HIPAA-compliance yet, so I am not sure how Herkou (if that's the one you are referring to) can be HIPAA compliance in everything.
Bachelors is for real-world software engineering, Masters or PhD is where the serious CompSci should happen, IMO.

(I say this as someone with a bachelors only)
Have you checked out typing.io [0]?

[0] https://typing.io/
>I heard a quote recently that "the best services are extracted from existing systems, not designed up front." I think that's right.

Damn right. Architecture should be an emergent property of your system and built incrementally. The people who do it up front almost always do it wrong.
I'm in Colorado and remember the big snowstorms in 1997. There were a lot of downed power lines and trees due to the heavy, wet snow.
CSCI 3350: Debugging- Beyond Print

CSCI 4600: When Big-O Complexity Becomes a Lie and Why
My OS class at least didn't even come close to covering that sort of stuff. Half the semester was on concurrency primitives and System V IPC :(
If you're running inconsistently, then it's no surprise why then.

I've lifted and run at various times in my life, and I found running a lot more rewarding, especially with all of the bad advice out there that surrounds lifting.

After the past 5 years of mostly running (with some time away at times due to injuries), I went from a 12 minute mile to a sub-7 minute mile in 3 years (with 1 year not doing much in the way of exercise). Consistency with the frequency of exercise matters a lot.
> And agile was created by people who don't understand that most organizations need specific software developed on a specific budget.

That's an odd criticism of agile. The whole point of agile is to prioritize so that the important stuff gets done first and does what it's supposed to, so when the money runs out you've got the most important bits working the way they should.

If you've got a fixed budget, you're waterfalling and the money runs out, odds are very high that the software is going to do what the requirements said it should do, but it will be near-useless in real life.
Finite element analysis modeling is really hard, even for nuclear engineers whom can code.

A lot of scientific control system apps get built with LabVIEW or Agilent VEE. If it makes beyond the niche consultancy stage, such things are often (re)written in whatever an engineer happens to know: C, Python, Haskell, LISP, [favorite language religion here].

Edit: BTW, just came across a supposed successor to VMEbus [0] (a standard industrial data bus): VXIbus [1]

0: https://en.wikipedia.org/wiki/VMEbus#/media/File:VMEbus.jpg

1: http://www.vxi.org/specifications.html
Network speeds I don't know about, but the book "High Performance Python" comes pretty close to the description of "CSCI 4020: Writing Fast Code in Slow Languages". Check it out!
related https://github.com/joshprice/graphql-elixir an elixir implementation of graphql I've been watching
Talking about merges in Git always reminds me of this Linus post:

http://marc.info/?l=linux-kernel&m=139033182525831

there's clearly a balance between "octopus merges are fine" and "Christ, that's not an octopus, that's a Cthulhu merge".

(Also, GitHub's logo is reminiscent of the "octopus merge".)
Thank you for being honest about the challenges you have faced with this hardware goal. I'm a little disappointed I won't be getting my Ohm battery, but it is better than promising something you can't deliver or delivering something that wouldn't live up to your promises.

I might be in a different market though, since I specifically wanted an ultra light weight battery for a stripped down street legal race car. Any plans to continue pursuing this market segment? We obviously don't have any high electrical needs beyond simply starting the car and running the on board ECU.
http://parlos.tamu.edu/MEEN651/E4.pdf

Read page 3. It completely validates what I'm saying. Monty might be a really smart guy, and he might be worthy of lots of praise for a great many things. But in this particular very limited instance, he is not as correct as he could be.

If all you can do is link me to the Wikipedia page about this, you're way out of your depth. I took multiple classes on this in college and I raised exactly this issue with my professors. They said that technically I was right, but in practice nobody samples at exactly the Nyquist rate (or even that close to it!) and it's really more of a guideline for the slowest sample rate you could possibly get away with, not the sample rate you should pick once you know your frequency content. Both Shannon and Nyquist were very smart and they've made a gigantic contribution to DSP. But knowing the phrases "Nyquist rate" and "2x the highest frequency" doesn't a signal processing expert make.

You can read plenty more here too if you'd like to get more educated. http://www.wescottdesign.com/articles/Sampling/sampling.pdf

Here's a snippet:
"The theme of this paper can be summed up to this: the Nyquist rate isn’t a line in the sand
that you can toe up to with complete safety. It is more like an electric fence or a hot poker;
something that won’t hurt you if you keep your distance, but never something you want to
saunter up to and lean against."

I totally understand if you just want to argue on the internet and given that I don't have the same credentials or reputation that Monty does, feel free to disregard what I'm saying. But that doesn't make me wrong one iota. The truth isn't dictated with the folks with the proper credentials, the truth is and you have to try and figure out what it is.
Pororo world map 뽀롱뽀롱 뽀로로 세계지도 ポロロの世界地図 Travel around the world with Pororo
MUSIC+ALERT:+Demax+(Demaxsinger)+–+SUPERMAN+|+TopNaijaMusic.com
It's a methodology from when you had to schedule time for your program to run and at a minimum 24-72 hour turnaround on the smallest change. In that case it's worth taking extra time to verify things on paper and institute heavy practices to ensure correctness. Then you can just type "exec" in a terminal that completely changes the equation.
CSCI 2550: Software complexity and the art of Keeping It Simple.
Kind of.

There's a flood of blog posts (including this one I think) that have conflated the two, probably unintentionally. I'm happy that decoupling their systems worked out well for them. I'm not so happy this is fomenting a new fashion for creating unnecessary network API end points.

That isn't to say that you should always combine your services into one big mega-service. Just that dividing up services should be something you do only when it becomes obviously necessary and for good reasons unrelated to coupling.
neteng where I work uses one with an external wifi adapter to test our wifi infra.
This is Networks and Distributed Systems at UChicago:

CMSC 23300. Networks and Distributed Systems. 100 Units.
This course focuses on the principles and techniques used in the development of networked and distributed software. Topics include programming with sockets; concurrent programming; data link layer (Ethernet, packet switching, etc.); internet and routing protocols (UDP, TCP); and other commonly used network protocols and techniques. This is a project-oriented course in which students are required to develop software in C on a UNIX environment.

http://collegecatalog.uchicago.edu/thecollege/computerscienc...

The 3 major C programming assignments last year: an IRC server, a TCP stack, and a router.

Best course I've ever taken.
AccursedUnutterablePerformIO: “a malevolent agent of chaos”
this is so good
We often teach Boy Scouts that tying their shoelaces correctly (a square knot) leaves the laces across the shoes, but if they go lengthwise along the shoe, it's a granny...
Unless you are willing to pay me to rm -rf your source tree, you are contorting the definition of liability.
> PS. I was truly impressed with Richard Hipp fixing each and every of these cases within a couple of hours of sending in a report.

I can't stress how quickly this will turn me from "it's a good library" to "it's an amazing library". (Or prevent me from tacking on, "but it's kinda abandoned".) I've never sent patches SQLite's way, but I've sent patches to other open source projects, and whole quarters go by with nary a peep. This is not only frustrating, but often it feels like it pushes more work onto me than just accepting an even potentially buggy patch would cause. If I'm sending a patch, there's a good chance I'm using it myself, and thus your library has become a special-cased wart in my deployment process that I'd very much like to kill. (E.g., since I work in Python: I can't `pip install package==version` anymore; it needs to be on Github or something; thankfully pip makes this fairly easy; patches to things that some other package has decided to bundle rather than just use the package-manager approved version of are especially painful.)

While I'm not sure I'd go this far, the lament reminds me of http://felixge.de/2013/03/11/the-pull-request-hack.html
You're living in a different world than I am. In my world, most organizations don't know the software they need until they figure out what they don't need in UAT.

The exception to the rule is when they're replacing an existing system (or consolidating multiple systems.) Then, they think they know exactly what they need, but then they won't figure out what they need until UAT when the real users finally see the system and point out the business rules that were considered unimportant.

So, why not iterate quickly, developing the software in one of two orders:
* If one portion of the system can be used independently and generate value, why not build that first and get everyone using that?
* If the system cannot provide value independently, build the MVP of the first screen they will use in the workflow and a view-only portion of the second screen? Then get real world users to tell you what they absolutely need before calling it done.

Once the first screen is done to their approval, then you take stock of the budget. You tell them there is a balancing act between cost and scope, and everything flows from there. (Or, you find that the value can't be realized and bail to another project.)
> It is in the context of building a larger
> cryptographic protocol. But they aren't
> building a cryptographic protocol in this
> case, so none of that applies here at all,
> even a tiny bit.

"Crypto" in the context of "don't roll your own crypto" does not mean "cryptographic protocol", it means "crypto system". The Wikipedia page uses protocols as examples of crypto systems.

> "Encryption" has a very specific meaning that is
> hundreds of years old, "crypto" is just a shorthand
> way of writing encryption

You're wrong. As I said before, in the case of "rolling one's own crypto" it refers to "crypto systems". Not every word containing "crypto" refers strictly to encryption. E.g., MD5 is a "cryptographic hash function".

> or cryptographic, and neither term is a synonym for
> authentication.
> ...
> I cannot tell if this confusion originates from
> people not understanding what the words "encryption"
> or "cryptographic" mean, or from them not
> understanding the difference between authentication
> as a broader topic and encryption/hashing as a
> singular component within it.

Cryptography encompasses more than just encryption. Authentication is included in the definition of "cryptography" here: https://en.wikipedia.org/wiki/Cryptography. An authentication system is totally a crypto system and totally falls under the definition of "cryptography"!

MD5 is a bunch of XORs and MODs. Bcrypt has a bit of that, but mostly it uses Blowfish. Scrypt is used for more or less the same purposes as bcrypt, and is built on top of PBKDF2_HMAC_SHA256. Do you see the difference? Bcrypt and scrypt are built out of things at MD5's level.

Once again, from Wikipedia, https://en.wikipedia.org/wiki/Cryptosystem:

Typically, a cryptosystem consists of three algorithms:
one for key generation, one for encryption, and one for
decryption.

That sounds like bcrypt and scrypt qualify. I don't know, but they are clearly much closer to it than MD5. Anyway, the distinction is not always black and white. The point is to use as high-level and complete an implementation you can find for any crypto-related things you need to do. Including password hashing. MD5 was too low-level, and look at how badly they messed it up. They tried to achieve what bcrypt and scrypt were designed for by using a much lower-level construct in MD5. They rolled their own crypto.

> Do you really think an authentication scheme
> is a cryptographic protocol? Is AES an authentication
> scheme? Is Kerberos a cryptographic protocol? No

No I don't. But an authentication scheme is a crypto system. Kerberos is a crypto system. Hence the term "don't roll your own crypto" would apply to both.
I'm an embedded systems engineer. It's always been that way for me: I own and compile the bootloader, kernel, filesystem, runtime libraries, and the application code. I have the schematics and gerbers for my boards. I have the reference manuals for every chip.

What's weird is watching people play with stuff like Raspberry Pi and they expect things to just apt-get and launch like it's always been done for them. And most of the time it does just work that way. Except when it doesn't.
>Monolith: Bring down the service completely.

Unless you've scaled your "monolith" horizontally, in which case it takes out one server.

If you've got a decent system, it can self heal from that and ping you via a monitoring system.

>Microservices/SOA: Timeouts to part of the system

Causing all manner of annoying behavior and difficult to track down bugs like an endlessly loading web page on a completely different system that happens a couple times a week instead of a clear error message.

>Assuming you've done a decent job of engineering for partial failure

If you assume a fantastic job done when engineering then you can make the worst architectural patterns "work". It doesn't mean that they are good ieda.
> CSCI 0666: Implementing Reverse Binary Trees on whiteboards.

Not of much practical use later in life, but an A in this course guarantees a technical interview pass with any major Silicon Valley company.
The old fashioned way - do benchmarks and collect data.
It's very neat stuff (it saves on multiple round trips to collect just what your UI needs right now), but GraphQL isn't about graphs (although one of my primary use cases does use an underlying graph database), just like React isn't reactive.

I think Facebook's naming people do this on purpose. (j/k)
I put up something similar here after experimenting with a related idea https://github.com/claes/osql
Welp, There you go, https://github.com/nukep/llamadb
If you can remove lines of code and retain functionality, then yes, I will pay you to remove code.

Conversely, adding lines of code but NOT adding functionality isn't worth a cent.
You realize that there's a war between people who write static code analysis software and "software architects", the former trying to detect global state buried in object hierarchies and the latter disguising global state as something else in the interest of "decoupling" things that need coupling.

Every class property is effectively global state (has the printer been initialized? what objects of this type have been created?) If you don't think class properties are useful...

Globals are a tool. Used badly they're terrible, but so are design patterns. For a long time many very useful pieces of software ran very well with lots of global state, but the egregious cases of misuse spoiled it for everyone. The problem with the "never use globals" approach is that if you need them, disguising them as something other than what they are makes things FAR, FAR more difficult to reason about.
You don't really have to know the internals but I personally think you ought to know the abstactions themselves at the very least. To be more specific, you need not know say the internals of your compiler but you ought to know how compilers in general work. Same with protocols, filesystems, OS {vm,scheduler} ...etc.
A more usable Apache server status page
As an IBMer, many of the complainers I've heard and much of the heartburn around layoffs come from outside of CAMSS. It's like folks at Apple complaining that the iPod team isn't treated as well as the iPad team. Of course, your group isn't making money.
How to set up cron job for Wordpress Automatic Plugin?
The new Notes-based webmail is Verse. It's not horrible. It's not great. It's just bad in different ways than Notes was.
Yup. And here's 7 more damn awesome articles:

1. http://www.damninteresting.com/the-birth-control-of-yesterye...

2. http://www.damninteresting.com/the-clockmaker/

3. http://www.damninteresting.com/the-derelict/

4. http://www.damninteresting.com/the-ethyl-poisoned-earth/

5. http://www.damninteresting.com/the-zero-armed-bandit/

6. http://www.damninteresting.com/spies-on-the-roof-of-the-worl...

7. http://www.damninteresting.com/undark-and-the-radium-girls/

Full archive: http://www.damninteresting.com/archives/
You should look at NixOS[1] and GuixSD[2].

[1]: https://nixos.org

[2]: http://www.gnu.org/software/guix
Good question.

I am not skilled in econ, but isn't this because the utility of new technology increases faster than inflation? In other words, utility(technology1, t1)/cost(technology1, t1) < utility(technology2, t2)/cost(technology2, t2).

Ignoring any affects of supply and demand,

If I buy a tractor 1.0 today for X dollars to produce Y units of utility (i.e. Y/X), but tomorrow tractor 2.0 costs 2X dollars (with inflation) to produce 4Y units of utility (i.e. 2Y/X), then my tractor 1.0 should be worth 1/2 dollars tomorrow (assuming that it still has Y units of utility). And, I may buy a tractor 2.0.

But, if on the next day, tractor 3.0 comes out and still has 4Y units of utility (technology stagnation) but costs X dollars (deflation occurs and production costs have gone down), then my tractor 2.0 should be worth 4X dollars. I'm not going to buy tractor 3.0.
Ask HN: Is RSS still worth the time?
I'm dealing with a project that lives through content and I was wondering if it's still worth the time to invest making some RSS features that someone suggested.

I honestly rarely hear about RSS. My idea is to build whatever users are asking and stop investing time in features that will go unnoticed but, since this is a young project, I might be wrong and losing something.

My question towards this community is...how many of you still use RSS to subscribe to content?
Police bosses from third world countries are not the most reliable people.
removing the tree without maintaining the functionality is damaging the asset
> The key to identifying difficult people is first realizing that the interactions with the person leave you mostly feeling worse.

But you're not a psychiatric professional so how could you possibly identify "difficult people" like that? :p

Even if it happens over and over again with some specific individual, you're still not in a position to conclude anything based on that, because you lack psychiatric credentials!
CSCI 099: How to apply what you learned in comp sci.
I hear you on the support side. I used to work for a company that used a product that was bought by IBM. Before that, you could pick up the phone and talk to the lead developer. After, you opened a support ticket online and waited 24-48 hours for a response from someone in Costa Rica or India. Now I work at IBM with this same product, and even I as an employee who supports the product, even I have to go through the same Level 1 tech support crap.

However, the cash injection made the core product worlds better, and it was good to begin with. Support got worse, the product got better. It's almost an even balance.
You must have had different business classes.

The one class I had with business majors, I was completely underwhelmed as to their capabilities. I was amazed at having an upper division course that had such atrocious writing and thinking skills.
RIT already has done this.