skysight-inc/HackerNews huggingface dataset:
we want to begin front-end development right away

I think that beginning of the development is pretty easy task. Maintaining and modifying existing codebase it’s hard. If project is starting and codebase is small you can rewrite whole project from scratch in few days. But when project grows it is wiser to refactor than rewriting. But if you want to refactor your project has to be maintainable.

We know most of the front-end interactions we want, but more will be discovered and some might be changed.

You can make quick prototypes before you begin serious coding. Start new branch in your repository and don’t try to write some beautiful code. Just hack and tweak features. Mock some features if you need it. I think that prototype phase / sandbox phase is often necessary to gain technical knowledge and gather business requirements, to decide which features are useful and which are not (off course you may need to consult these decisions with your stakeholders, your client, etc. But having working prototype makes this easier than operate on *.psd based designs and unclear guidelines).

And after prototype phase you can delete your sandbox branch and start some serious coding for production.
Oh, I'm quite certain I understood the point. Women aren't as smart as men because they're more concerned with being pretty. They cave to social pressure because they're weak, unlike those strong nerdy men that go on to do important smart things like engineering.

The fact that not all men are sufficiently intelligent and brave and focused to be engineers is a sufficient defense of the sweeping generalization that women fail because of reasons completely different from men failing - specifically, desire for social status.
There are some Mozilla security folks feeling out the waters as we speak.
The disaster that may have saved D-Day (2009)
Anyway, what do you what to discuss about it? Do you agree with his points? Disagree? Would you like to expand on something the author said? Etc? I mean, just saying "let's discuss X" isn't saying much. Start us off by throwing something out there!
Secret US court allows resumption of bulk phone metadata spying
Kind of obvious question that hasn't been asked yet - what happened to the IP? Any chance it could be open sourced? (Would it even be pointful to open source it today?)
I can't agree with this more. As much as I sympathize with entrepreneurs and managers having trouble hiring engineers in this current environment, I feel like "they" brought it on themselves because wages were probably below what they should've been for years, and because of that, supply became depressed.

Now that a lot more infrastructure and tooling is in place, we're seeing the effects of that prolonged depressed supply. It's easy (relatively) to hire junior devs, and much harder to hire senior devs. And even still, I talk to senior devs who have trouble getting a raise. I'm like... ok... well I hear X is hiring.
One way to think of it is why would you use Cassandra when you already have a filesystem?

Those databases are quite raw, to be useful for a use case like monitoring you need to build on top of them to allow for ability to get data from agents, do some processing and enable efficient querying of the data.
Done and done. Let me know if you want it anywhere else and thanks for writing terra! :-)
9 lines copied by the guy who wrote the original implementation, let's not forget. This was literally a case of him saying "oh, I've done this trivial thing before, I'll just grab what I did then".

This whole thing is a travesty.
If I am on a call, it's seamless - no issues there. However, it doesn't seem to work for data in general.

I commonly try to get Google Maps directions as I leave the house, and often it just fails since it's still trying to use my WiFi which is too far away to be useful.
Staying at one firm is less scary, but is a career killer. You owe it to yourself and your career to move every few years. I aim for 5 years tops at one firm, unless I happen to get lucky and move within the firm to a substantially different job. That's happened to me once.

A different company offers you broader experience, if its well chosen, and of course, a better raise. I don't use a job offer as leverage at the old firm; I think that's a bad career mistake. Of course, jumping is scary, and the new firm might suck, but that's why networking is essential, whether you like it or not.
Wait, what?! Can you illuminate the intervening breadcrumbs?

Edit: wow, he's everywhere.
Its an upfront cost for sure, but it more than pays out throughout your program later as you have guarantees for the shape of the data
I just tried on my MacBook pro on another network, and don't see the warning now. I'll need to go back to my iMac and find the certificate chain.
Are there technical solutions you've seen/implemented/read about to solve these issues?

There is no silver bullet but from my experience these things let you to maintain (and modify) project more easily:

1. Separation of concerns

We have an incomplete schema for our API, it's mostly stable but some changes will happen

It's better to create some specialized service/module to connect with backend API end-points than have something like
$.get('/get/user/' + id)
spread across the project. If you follow SoC, when backend API changes you have to update only one file.

2. Modularize

If you have proper modularization (achieved by proper design or/and incremental refactoring) you can make global changes very quickly (you have to update just one module to apply changes everywhere) but you can also make local changes also quickly (you just have to decide what submodules you have to use in your parent module). If you treat project not as a monolith but as a interconnected set of decoupled components/modules developing is like building with Lego bricks.

3. Refactor constantly

Is there some code that can be written better? Refactor. Avoid unnecessary complexity. Simple and succinct code is easier to maintain and modify. And make your code reusable.

4. File/directory structure based on components rather than filetype.

I never understood why so many people create directories like “controllers”, “directives”, javascripts”, “stylesheets”. The truth is that if you work on some part of your code you will usually edit all of these files. And you end up jumping over 3-4 different directories to make very small change. Directory structure based on components / views / modules / other logical part of project / seems to be better than put 10 files in one directory only because they all have .js or .css extension.

5. keep third part library code separate (if possible).

For example you need to inject some third party slider/carousel/chart etc. on one of sub-sites. It's better to make directive for this and insert 1 line of directive <my-slider> than just throw some 20 lines of code in your HTML and JS. Imagine that you need to change library X to library Y. Wrappers/adapters add some additional layer of complexity but I think that outcome is still positive in many cases.
Two reasons:

1. It degrades design as a profession. It's essentially saying that logo design can be done by an algorithm. "There's no creativity to it". Wouldn't you be offended if someone said a basic algorithm could eliminate your job? (perhaps you wouldn't)

2. It's an overly simplistic view of what a logo/brand identity is. You can't just pick out some basic shapes and text for your logo. You need color theory, contrast analysis, a brand strategy, a well developed concept, etc.
Amazon launches in Mexico
This API call is just returning a PNG image with almost no EXIF data. In that case, the title is set by browsers to the filename, which is equal to the domain name itself. Are you seeing something else in the title? (I see fb.com)
Re collections: There are Java interfaces you can implement to make your own collections that work as built-ins. In general, nothing in the Clojure compiler or runtime is written based on concrete collection classes, only on the internal interfaces. It's perfectly feasible to write a deftype that implements Counted and Associative and whatever else and make your own things that work with all the existing standard library. There are plenty of examples of this.

Re sorted-set: Any 2-arg Clojure function that returns -1/0/1 comparable semantics will work.

Re staying "in vectors": The subtle blurring of the sequential collections between the collections and sequences is part of what makes so much of working with data in Clojure easy. However, there are certainly times when you want more control over this; fortunately in 1.7 with transducers you have the ability to control your output context (with functions like into or conj) and this is easier now than ever.

Re rx: several people have already implemented the use of transducers with Rx. I know there's a RxJs and I'm pretty sure I saw something re JavaRx although I can't put my finger on it right now.
Can Data Infrastructure Vendors Stop Hackers?
It doesn't have to be like that just because the language is compiled, though...for example, Elm's JSON parsing is quite nice: http://elm-lang.org/blog/announce/0.14#making-json-easier
Does this have any practical uses?
Could somebody please disrupt this business! No user likes Ticketmaster and their "service fees".
Kneser-Ney Smoothing Explained
> given that Clojure is a dynamic language

Yes, that helps in this case, but that doesn't mean being statically compiled allows you to disregard extra-linguistic downsides.

> however it has many things that need to be cleaned out.

No! There are things that could have been better; sure. But they don't need to be cleaned out because that would break backwards compatibility. Backwards compatibility is a very, very, very important thing. So much more important than a "perfect implementation" (something that can never be achieved anyway). This is something that is very hard for PL purists to understand, but extra-linguistic features and guarantees trump 100% consistency almost every time.

> It's also disheartening to see that the sorted-set wants things that implement Java's Comparable.

That's only disheartening if you're a purist. If you care about extra-linguistic concerns, such as Java interoperation, this is a mark of great design. You see how the language designers took into account concerns outside the language itself. Every Clojure map is a Java map and vice versa. Every Clojure sequence is a Java collection and vice versa. Every Clojure sorted set is a Java sorted set and vice versa. This is great design around constraints and what Rich Hickey always talks about. The language itself is no more important than how it fits within the larger ecosystem and its constraints.

> as I can't see how it can be applied to reactive streams (e.g. Rx) when back-pressure is involved

Clojure is an imperative language first and functional second. It is even more imperative than Scala (in spite of Scala's mutability) -- at least with Scala's (recent-ish) emphasis on pure-functional concepts (a terrible idea, BTW, but that's a separate discussion). Back-pressure is therefore automatic (and implicit) with pull-based channels (that transducers can be applied to).

> I prefer languages that fix their mistakes

Because you're a purist. I prefer languages that see the big picture consider what's important in the grand scheme of things, and realize that code is important but secondary to working programs. As Rich Hickey is not a PL researcher, I am sure that those mistakes will only be fixed if they don't break compatibility or Java interoperability, which are more important for the industry than a perfectly clean language.

> not sure why we're having this conversation

Because supporting separate compilation -- if not perfectly then at least treating it as a top-priority concern -- is one of the key ways to ensure binary compatibility between runtime-library versions.

> On the other hand certain features, like traits providing method implementations or default parameters are landmines.

That's exactly my point. Separate compilation (as many other crucial extra-linguistic concerns) is just not a priority for Scala. Kotlin, OTOH, implements default arguments on the receiver end rather than at the call-site, so changing default values in the target doesn't necessitate recompiling the caller.
Fair enough. My cat is only four years old. But my point is that we treat tooth decay like an inevitable consequence of failing to brush and floss when we actually know it's caused by the blooming of certain specific bacteria. Brushing with fluoride helps enamel resist the decay, but it does nothing to prevent the bad bacteria from blooming again in 12 hours.

Admittedly, I hate taking care of my teeth and thinking about things this way comforts me when I fail to do so.
Looking to increase lead engagement?
They could just add yet another surcharge to cover it and what can we do?

Basically nothing.
I can't really get into the details, I apologize. I can tell you that the specific topic of jamming isn't a concern. Try and think about UAVs in the same way you might think about commercial planes. It would tend to make sense that the UAV model was most likely forked from there, at least initially.
X_i is a valid variable name. Although it seems in math you can only use single-letter variable names, which is kinda ridiculous (coming from a computer science background).
I had a similar idea! I'm glad something like this is being implemented.

The most important idea imo is that companies can never claim ownership of personal data because they never have access to it. Another cool idea is that if you have a currency that can be cashed in for fractional computing power on the network you could pay tech companies in computing power, either providing it from a device you own or paying for it with the currency.

I look forward to the papers/code that they release.

Edit: I'm not really clear on this, is there any currency component to Enigma? I was thinking there could be a currency that's a transferrable debt of fractional computing power of the network.

Edit 2: Apparently it isn't a currency and uses bitcoin for fees...
Generally Europe doesn't fluoridate its water, true, but the practical effect is a bit more nuanced. For example, Germany has mostly moved its fluoridation program from water to salt: http://www.ncbi.nlm.nih.gov/pubmed/16156167

In Denmark the water isn't fluoridated, but its natural levels of fluoride are only slightly lower than the levels that U.S. cities add (for example in the Copenhagen water supply, fluoride is around 0.6 mg/L). So it's a bit pedantic to claim that it isn't fluoridated. It's true that the utility company is not adding more fluoride to the water, but the end result is still that the pipes are delivering tap water with fluoride in it.
So you mean that it's alright that the possibly most prestigious science journal on this planet is used for self promotion?
> Is there a specific reason that makes you prefer an impersonal compiler?

It complicates parsing
Great to see this release of Red Hat Ceph Storage.
Scientists have created 3D holograms that you can touch
This is mostly an issue with terms. Most (all?) of the operations we call constant-time, say, comparison, are technically logarithmic in the number of bits on real computers.

Since that's usually not relevant to big-O analysis, we can sidestep the issue by specifying what we're counting: rather than say that mergesort is in O((log n) log (log n)) time, we say it takes O(n log n) comparisons.

Whether you think of that as a theoretical computer with a constant-time comparison instruction or as a real computer with a commonsense (2^64) upper bound, the upshot is that we don't care. As long as what we're studying is sorting, not comparison, it will fall out of every algorithm, so the difference isn't important even in theory.

It's still an important thing to notice, though-- there are plenty of cases where you definitely do care about counting bits.

In more detail: http://cs.stackexchange.com/questions/1643/how-can-we-assume...
>quality

I take it you're new here. HN has been "tech reddit" for at least a couple of years now.

(This will probably whoosh miles overhead, too).
Ask HN: Weird that the “Uber $470M losses” not picked up by top tech press?
Anyone else find it weird that the "Uber has $470M losses" story did not get picked up by top tech press (techcrunch / recode)?
http://prog21.dadgum.com/56.html agrees with you:

I still like to implement my own ideas, especially in fun languages like Erlang and Perl. I'm glad I can program, because personal programming in the small is fertile ground and tremendously useful. For starters, this entire site is generated by 269 lines of commented Perl, including the archives and the atom feed (and those 269 lines also include some HTML templates). Why? Because it was pleasant and easy, and I don't have to fight with the formatting and configuration issues of other software. Writing concise to-the-purpose solutions is a primary reason for programming in the twenty-first century.
This is what UniversityNow attempted with its takeover of Patten University: http://www.businesswire.com/news/home/20120709005304/en/Univ...
I wasn't really involved in that, being a mere foot soldier, but --- from memory --- we licensed intent to them and then they rebranded and extended it to become Amiga Anywhere. The idea was that AA games could be written using our tooling and run on a runtime based on intent. So, they'd run anywhere with our runtime. I think they were trying to exploit the Amiga brand to leverage synergies, or something.

I don't know why it failed; we didn't have anything to do with Amiga's operations, apart from offering support. (I don't think any of us were Amiga people.) My impression was that the general feeling inside Tao was that the Amiga of the time was cursed, and we didn't want anything to do with it. Tao itself wasn't doing well then and we were all a bit superstitious. It didn't help that the main person we dealt with was called Fleecy Moss.

I did get one perk out of it: I own a copy of the Amiga comeback album. Lucky me. https://www.youtube.com/watch?v=szMGxqwfxiI

Here's a terrible video of someone from Amiga demoing it. God, those iPaqs. I had one on my desk with a PCMCIA hard drive in it for doing the ARM Linux port. Horrible, horrible things. https://www.youtube.com/watch?v=HfHcwpzxSdk

I'd be interested in playing with a copy of AA if I could get my hands on a version which would run on a modern machine.
I was updating with my personal breadcrumbs when you replied. Richard was a colleague of mine - the plan9 scene leads very quickly to luminaries - I have had the privilege of meeting some very talented programmers who are humble so one day you will be on a webpage and go "gosh, I know that guy"
The actual warning is:

> Keep out of reach of children under 6 years of age. If more than used for brushing is accidentally swallowed, get medical help or contact a Poison Control Center right away.

Note: more than used for brushing

So, it's fine to swallow your toothpaste if you want. But if your 4 year swallows a whole tube of it, they are probably going to get sick to their stomach.
I don't know why it does that. I get the blacked out page on both Chrome and Firefox.
I was researching right now about bots for slack... Thanks!
There is an informal honour's code among scientists that you don't take credit for other people's ideas. While it is forgivable for a PhD or postdoc to be unaware of older work -- after all there's sooo much of it -- a senior researcher should not act carelessly with attributions. And where they do, it's useful to remind them that they have transgressed dearly held ethical norms.
Ticketfly is doing a good job. They do charge some fees, but not to the egregious extent of Ticketmaster, and have a much better interface that holds up against traffic.

Unfortunately, Ticketmaster has a habit of just buying/merging with competitors (including Live Nation, in a merger that should have never been allowed to go through).

Plus, Live Nation actually owns a lot of venues, so you'll never see them use another ticketing provider: https://en.wikipedia.org/wiki/Live_Nation_Entertainment#Venu...
Great read. Tom is a master when it comes to clear communication.
This seems a well-thought out retrospective. It was made more than ten years ago. I wonder if it were done today if the support by Java, Python, and other languages is as good as the Lisp support.

Has anyone used some of the tools mentioned here and could explain what the current state of the art is ?
I do love the tech of this era. Here are some contemporary throwbacks:

(video) https://www.youtube.com/watch?v=z7q5DLS1rAU

(audio) https://www.youtube.com/watch?v=yT0gRc2c2wQ
Oh, my bad thanks. Though I think my point still applies. STOVL is useful enough that they kept the Harrier around in multiple incarnations, since 69.
> Russia's economy is shrinking at 2-4% per quarter right now and burning through its reserve trying to keep things running.

Nice try. Have you seen their GDP numbers? Their worst quarter was just over 1% contraction, their GDP is around 2% off their all-time high.

http://www.tradingeconomics.com/russia/gdp
Rich didn't claim you couldn't implement it. He just claimed that some aspects of transducers are difficult to represent as types. Or at least, that's how I took it.
Examples are Reader Mode and Power Saver, both features designed to reduce the impact of, let's say, non-central content. Ad-supported browsers are not exactly eager to implement these, naturally.
I'm always amused when I see the criterion for a "very dense" time series as data being collected more than once per second. In my business (telemetry), we often record parameters thousands of times per second, depending on what we are trying to measure.
> Wouldn't you be offended if someone said a basic algorithm could eliminate your job?

Of course not. In fact, I spend quite a large portion of my time automating most of my work, so I can do other, more interesting things.

Besides, if a company looked for and used a "free logo generator", would that company really be the type of client you wanted to pick up?
It depends on your level. Companies are falling all over themselves to bring in more women, but might get your resume glossed over for a senior or lead dev position, or they might assume that she's looking for a more junior position, or perhaps something with more visual design or front end work. Because hey! You're hiring women in tech either way!
Complementary reference: Negotiation Advice
from Silicon Valley :)

https://www.youtube.com/watch?v=N6Zz-Nkkaxc
Yah, that is the obvious choice, but it wasn't as clear cut. Especially with the behavior we were seeing where the performance problems would remain long after the lines were flushed from the CPU caches. I spent a fair amount of time looking at Intel docs on snoop filters and the like and never really satisfied myself that I knew exactly what was causing the problem.
Tooth decay has plagued humanity since before recorded history. Before dentistry, it used to kill people. It routinely kills animals in zoos. Presumably it kills them in the wild, too --- just, more slowly and painfully.

Which is not to moralize about your own dental hygiene. Dealing with the consequences of poor dental hygiene is what dentists are for. :)
Farm Waste and Animal Fats Will Help Power a Jet
Fly.js: New generation build system
It vanished into a lawyer's basement, and so passed out of history. 10+ years of work, gone. NOT THAT I'M BITTER OR ANYTHING.

Open sourcing it's probably not useful: it was based almost entirely on tribal knowledge, passed from developer to developer, and learning curve was pretty steep. I worked on our translator for a while, porting it to new CPU backends, and... yuck.

However, please try; somewhere in that lawyer's basement is a short story which I wrote in my lunch break, emailed to a friend, shortly before the company went bust... and I forgot to send a copy to my personal account. And my friend lost it. I want that back, dammit.