skysight-inc/HackerNews huggingface dataset:
People often imagine they'll make huge amounts of money by making a tiny amount on each trade, very frequently and consistently. The arithmetic on the percentages makes it appear possible. It just works just as well (or better/worse) in reverse.

I'm not sure what's typical these days, but let's say the spread on a large cap liquid stock is 0.02% and the spread on a small cap illiquid stock is 0.40%.

If you trade once a year, the cost is comparable to the management fees on an index fund. Not much, but already you're paying more than someone who is fully diversified.

If you trade everything once a month, and average -0.40% each time, you are down 20% after five years!

If you trade more frequently, say 200 times a year (not every day, but most days) and stick to the liquid stocks so that it only costs 0.02%, then you are also down roughly 20% after five years, before the actual returns.
They aren't safe to read or write concurrently.
A lot of people use PlusCal, which is basically pseudocode that compiles to TLA+. Depending on what you're modeling, PlusCal or directly writing TLA+ might be a better fit.
You want to have a source of truth. For simplicity I use a global variable. I however use Object.defineProperty so that it can only be written to via an "API" (methods on a global object), which is also responsible for calling event listeners.

For persistence localStorage works great. But often you want to have the source of truth on the back-end. For example if the user opens the app on two devices A and B, change the background to green on device A, and change the background to red on device B, then open up the app on a third device C, what background should device C get? :)

For simplicity I prefer to serialize to JSON, either to localStorage, or a .json file on the server, which is only for persistence in case of a sudden power loss, otherwise data lives in a in-memory object.

Clients today is very capable so I like to store as much data on the client as possible for fast reads. Then update that data in the background, which would also fire events (like "newMessage").

For binary blobs however, like images and video, I store them on a server, and let the browser's cache take care of the caching. I sometimes also let the browser cache take care of the caching of .json files if the data is rarely updated. For all static data you can use a high expire date and let the browser handle it. Only use the in app memory for data that is often read/written.

If you like to micro-manage the browser cache, you can use service workers. Service workers let you do complicated things like manually updating the cache, upload files from the client to the cache, wake up on push notification to prime the cache, etc. So even if the user is offline when he/she comes back to the web "app" most data is fresh and accessible.
Especially if it's a project with multiple people working on it. Refactoring will cause major merge problems for everyone doing anything else on those files. And if your team does best practices with code reviews and testing, then refactoring a chunk of code becomes a big project.
Couchbase could be a reasonable alternative, depending upon your requirements. Couchbase is written in Erlang iirc and Couchbase's indexing is written in Go.
Name it however you want, gets the job done (sometimes).
I use a text editor rather than an IDE. I just write the full descriptive variable name straight off the bat. It probably takes <1 second to type it the first time, and my editor will autocomplete it for subsequent uses. I don't really understand the value of using 1 letter variable names.
There are plenty of sysadmin knobs to check w.r.t. security, and you can learn those without knowing how to code. Many folks attack Active Directory and haven't seen its source code, for example. You'll eventually learn to code to advance, but it just isn't a hard prerequisite.
Show HN: Self Managed Link Aggregator
> This article makes a lot of assumptions that only hold true in a very specific set of circumstances:

Yes. The assumption that you are working on a web based service is so core to this piece that it doesn't seem any more necessary to say "this doesn't work for desktop" than it would be to say "this doesn't work without internet".

given that you are delivering software on the web, your customers are going to get changes to it and like it, because their other option is to run systems on the internet with known exploits. Customers who don't want changes host their own instance.

And if your next release is a year away and you have no way to roll back the release, but you have no manual validation - then you aren't following this advice to begin with, and you have an appallingly broken process.
The observed mortality rate already accounts for advances in medicine that are actively being used, no? Mortality rates are easy to compare: x% died back then and y% die now. Those numbers take into account the various characteristics of the disease and health care.

People aren't saying this acts like the 1918 disease so it should have the same mortality rate. People are saying the observed mortality rate is the same. That's in spite of medical advances.
For GitHub, I would have to imagine only being able to search public repos with regexp would be good enough. GitHub has many strategies, but the main one is, they want to maintain, if not, expand their open source mind share.

The more reasons you give people to go to GitHub, the better off they will be in the future. So I do agree with you that as a commercial solution, this may not be viable, but for GitHub's public repos, this can turn into a very positive thing.
I have training data which includes examples with missing fundamentals (synthetically removed), and the network does learn to recognize this. (The heavy regularization also helped a lot.)

Although I was able to test with real instruments (and my grotesque voice), I didn't find any good live examples of audio with missing fundamentals to test with. It did recognize held-out synthesized data correctly though.
“ Things You Should Never Do: They decided to rewrite the code from scratch.” This is a great general rule.

The rule is situation dependant and some people can break it and succeed: the parent comment was very clearly one of those situations.

The actual risk is that the majority of us think we can break the rule, when it turns out we can’t. But a minority of people/situations can successfully do a complete rewrite, success defined as where the gains abundantly outweigh the pains.
> I think the proper way to do certs is to have the server (Web, VPN, whatever) create a certificate signing request and private key on the server, send the signing request to the CA to sign it, and then install the resulting signed cert on the server. Is this correct?

Yes. The CSR is public information so it's fine to send that somewhere. "Sign it" [the CSR] is a phrase that doesn't entirely reflect what's happening with the relationship between a CSR and Certificate, experts know it's technically wrong but they say it anyway, so don't sweat it but it's probably misleading.

I will try to circle back to see if I have any suggestions for your specific scenarios later.
> If you're set up to do A/B tests or deploys with canaries or give potential customers test accounts you're probably able to start testing in production in a sane, contained way.

Basically you're outsourcing QA to your customer. Some systems may afford this, others not.
Too bad. A solid reason not to touch Credit Karma ever again.
This article is mostly good, but saying machines are deterministic breaks down at the limits - - some emulators start hitting cases where physical chips enter inconsistent states, which non-deterministically then fall into another state. Emulating such things requires treating machines as analogue.
If you start from philosophical questions of mind and identity (e.g., substance dualism vs physicalism, etc.), it’s not hard to get to an argument that qualia are neither substances nor physical identities but instead properties of systems (cf Whitehead), so you can ask not only “what is it like to be a bat,” but also “what is it like to be any system capable of qualia?” It’s possible that such systems could include societies, economies, corporations, and so on, depending on what you assume the criteria are for a qualia-capable system. (This is also how you get to the Gaia hypothesis, which sounds utterly crazy taken on its own, but almost axiomatic if you build it up from a systems approach to mental states with loose enough coupling and coherence restrictions).

The kicker of this approach is that the modes of qualia or consciousness at different system levels are likely to be so completely alien and the causal mechanisms so hard to discern that you could never definitively answer the question of “what is it like to be an economy;” it’s as impossible as a neuron wondering what it’s like to be Proust eating his madeline.

Scientifically, it’s virtually unfalsifiable but, if correct, it does have the delightful side-effect of turning social sciences such as economics from attempts to formulate natural “laws” to something more like efforts to psychoanalyze alien gods.
Embedding just the web player in native apps would be a pain due to communication between the native and web layer. If you just did the whole thing in JS (electron, etc) you’re barely any better off than the official client in terms of resource consumption, defeating much of the point of building an alternative client.

There are reverse engineered libraries available (mainly librespot[1]) but they come with the caveat of violating the EULA and risking the accounts used with it. AFAIK Spotify hasn’t banned anybody for using it yet, but it’s always a possibility.

[1] https://github.com/librespot-org/librespot
No. ELK is a slow and expensive way to store and retrieve logs. The reason people use it is that nothing else exists. (I was blown away when I started using it at my last job. I used the fluentd Kubernetes daemonset to extract logs from k8s and into ES... and the "cat a file and send it over the network" thing uses 300+MB of RAM per node. There is an alternate daemon that can be used now, but wow. 300MB to tail some files and parse JSON.)

I think a better strategy is to store logs in flat files with several replicas. Do your metric generation in realtime, regexing a bunch of logs on a bunch of workers as they come in. (I handled > 250MB/s on less than one Google production machine, though did eventually shard it up for better schedulability and disaster resilience. Also those 10Gb NICs start to feel slow when a bunch of log sources come back after a power outage!)

For simple lookups like "show me all the logs in the last 5 minutes", you can maintain an index of timestamp -> log file in a standard database, and do additional filtering on whatever is retrieving the files. You can also probably afford to index other things, like x-request-id and maybe a trigram index of messages, and actually be able to debug full request cycles in a handful of milliseconds when necessary. For complicated queries, you can just mapreduce it. After using ES, you will also be impressed at how fast grepping a flat file for your search term is.

The problem is, the machinery to do this easily doesn't exist. Everything is designed for average performance at large scale, instead of great performance at medium scale. Someday I plan to fix this, but I just don't see a business case, so it's low priority. Would you fund someone who can make your log queries faster? Nope. "Next time we won't have a production issue that the logs will help debug." And so, there's nothing good.
Some banks now offer this for free.
> Regarding the 'buy vs build' I think buying software is one of the most risky things that you can do. Since it cost money you cannot then say 'o well, i guess it just did not pan out, let us just not use it'. Now you are kind of married to the software.

It is usually way more costly and risky to develop your own. It's many hours spent on what is a separate product to your actual product, and you're way more married to it: you've just spent money, time and energy developping a custom homegrown solution. What are the chances you'll go "o well, i guess it just did not pan out, let us just not use it"? Very, very low

So you end up spending more money and a significant amount of time/energy for a product that's probably subpar because there's no reason you'd do better than companies that are focused on this product.

I think buying software is one of the least risky things you can do, you know exactly how much money you have at risk and you usually know pretty well what you're buying. You don't know how much money/time/energy it will take to make your own solution, and you don't know what result you'll get.
Even with --depth=1?
My two latest failed projects were a SaaS to help landlords manage their properties, including rent payment management, and an analytics tool that consolidated data from real estate property in a excel so people looking to buy or rent could analyse the options in a more effective way than going property by property in the listing site. Both projects failed because I could not attract users in a consistent way. I could not find any paying user during the 2 months that each project stayed online. Nevertheless, it was a good learning experience and it was one of the motivations to derive the project that I am working now (https://turbovar.com/), which is a full-stack Java Web APP template.
I haven't written a prototype in forever. I don't find them effective. And they typically take way longer than you expect at the outset.

Do some wire charts or graphics and present those. It's far more boring to do than writing a prototype, and learning design tools is cumbersome, but they allow you to demo things better to executives, redraw stuff on the fly in meetings, copy and paste to a document or slideshow, share with external parties, and people don't get hung up on minutae that come with presenting a prototype. Stakeholders far prefer seeing a well thought out document or slideshow than a dinky fake app.

Once you get signoff on the design and flow, then jump straight into the real code, skip the whole prototype step.

I'd rather be coding, but sometimes it's just not the most efficient use of my time.
I didn't look very hard for deep learning approaches to pitch detection, mainly because I was really interested in chord recognition (which is a far more interesting problem, IMO.) I didn't find any good research here (would love pointers.)

I did though spend a lot of time studying non-DL approaches to pitch-detection, mainly because I wanted better real-time performance for my game Pitchy Ninja (https://pitchy.ninja).
According to the Bureau of Labor and Statistics, the median salary for software develors is $103,000. Top 10% earned $166,960 or higher. Take out the cities I mentioned and those numbers are even lower.

If you know plenty of people outside of the major tech big cities (and I should have included Austin and Seattle in that, for sure) making over $200,000 year, they you have a statistically unusual sample of friends.

All the data back up what I'm saying. Go look at the numbers. Look at salaries on monster.com or your favorite job site. Perhaps you and your friends don't realize how unusual it is (granted, you also have higher cost-of-living in those cities, sometimes by enough to eat up the additional salary).
I don't find the credit karma tax UX to be quite as good as TurboTax, although I very happily used it this year because it's free. I suspect Intuit will not maintain a free alternative to one of their main products :/
I agree. I think this signifies as the "biggest fool" flag. When we take a position that seems foolish from a fundamentals point of view, expecting to make our profit from a bigger fool.

And "smart investors" frequently in earlier, look for their exit in events like this. Made much more explicit in pump and dumps...

Buckle up, 'cause here we go!
I think you solve it by making amazon directly liable for fraud on their platform. They’d clean up the problem pretty quickly after losing a few billion dollars in lawsuits.
What the Apollo Astronauts Did for Life Insurance (2012)
I have friends who are no longer buying from Amazon. Especially friends with kids. You can’t trust anything safe for your kids when crap like this is allowed. Amazon is in a race to flood the market with availability at the cost of consumer confidence.

Remember all the hoverboard fires you saw on the news several years ago? They weren’t knock offs, but items sold that didn’t have any real safety certifications in mind. Amazon only cares something bad happens on the news and they’re involved.
Whatever makes sense to your users for their search results. Do they want to get back the whole document or just the relevant parts?

If there are separate sections in the office documents that you can pull out and index as separate fields then you should do that. For example, if you were indexing patents, you would want to index abstracts and claims into separate fields.
That's tough. I can't say I'm a 10x dev or a superstar either.

From the post it sounds like you might not be motivated. Like perhaps this isn't your passion? Do you just find learning how to be better boring or hard or do you (if you honestly asked yourself) feel like dev work (or perhaps it's just this dev work) is boring?

What interests you?

Is there a niche that you're really good at? Where things come easy? Perhaps specializing there might be good?

Have you thought about blogging? Perhaps blogging your journey into getting better (if that's what you choose to do) might help and could help others and also build your own brand and at the same time keep you honest i.e if people are expecting new blog posts it will give you a reason to keep at it.
I have started buying most products directly from manufacturer's websites or in physical stores now. The amount of fake products on Amazon is appalling, I wonder why they don't put effort into stopping this.
That's definitely interesting, never thought about it. Prob hard to find "angry voice" training data though :-)
HN has become a cesspool for certain topics in recent years. Go threads being the worst; all the ego's seem to come out of the woodwork. I almost never bother reading the comments on anything Go related these days because it's just full of wannabe 10x programmers overstating academic edge cases as if no other language in history has ever had a shortcoming.
Not sure if you are aware of this. We ran this at Y!

https://vespa.ai/
Ask HN: How do I develop aggressiveness?
I'm 41 years old and I find I'm not aggressive enough, neither at work nor (probably) in personal life. It was something my boxing coach (various years ago) told me quite often.

I'm not passive or shy; I speak up, I tell people (and managers, and girlfriends) uncomfortable truths, I'm usually confident and (quite) assertive, but I'm usually too calm and understanding when things heat up in a discussion. It's totally OK for me to give up and think something like "ok, that person is having a bad day, I shouldn't fight fire with gasoline".

Now I feel that's a problem; because, very often, those discussions are those when you "win" an argument (especially in the eyes of colleagues or managers) or lose it.

When I approach again people that treated me harshly, they usually say "I thought that was already settled, wasn't it?" or something like that. I work as a software engineer, and I think this is preventing to step up in my career, despite the fact that most colleagues regard me as a really authoritative (and not authoritarian!) source and respect me a lot.

I know that some of you will tell me "find a better company". But I've changed some jobs already in my life, and ultimately some things don't change - I don't work in an horrible politics-only corporation - and I think it's high time to step up to what the game is.

Any kind of recommendation? Books, trainings, professionals that can help me?
> Sure, as long as the business gets to deduct the cost of the interviewers' time from that.

They can at tax time, whereas an employee can't. If an employer requests work from someone, they should pay them.
And please understand this is not investment advice, you must exercise your own discretion :)
Does the Prestop hook just leave the cluster instead of dying and waiting for reconciliation?
github's code search is notoriously bad, feels like a huge missed opportunity. Nice to see you guys reaching out to other people working in this area.
First look at the internals of containerd and runc
How have I never heard of chinaxiv? Thanks for bringing this to my attention.
Self-styled daredevil ‘Mad’ Mike Hughes dies in crash after rocket launch
I have no idea why we need to do this when we can just compute the strongest frequency components with a Fourier transform. Can anyone explain the advantages of this seemingly expensive method over simple (and more complex) Fourier analysis?
So, accessing shared mutable state from many threads at once is dangerous. It's hard to lay the blame for this on Go - it's true in most languages I know of.

I suppose one ought to guard such maps with a RW lock, or a `sync.Map` which is tailor-made for this kind of situation.
previously: https://news.ycombinator.com/item?id=9692408
You're assuming there will be anything left to buy once the storm has passed.
10x The Amount of Books You Read – Read App
I am not from US,but I think It deserves Anti-trust scrutiny.
Ask HN: Starting up with part-time co-founder?
Would you consider starting up with part-time co-founder who still works full-time at another company and will only join when we close our first sale? B2B space, early-stage and pre-launch, so lots of work required till then. They can spend around 8-10 hours per week on the venture.

What they bring is industry knowledge, but not irreplaceable.

They have no financial obligation (to support family) so the refusal to deep dive full-time is more of risk aversion than financial necessity.
>I wonder why they don't put effort into stopping this.

Because they make more money than they lose as a result while driving competitors into bankruptcy. Eventually they'll make a big public spectacle of getting it fixed (once the economics stop being in their favor) and everyone will forgive them.
Disclaimer: I don’t own amazon directly but do own funds where Amazon is a significant chunk.

I don’t agree with this kind of regulation. It’s simply not the governments role to decide. You as a seller are not forced to sell on Amazon. I say that as the spouse of a seller who owns a store on EBay that’s continued to be successful. We had a bad experience selling on Amazon and are better off without them. Of course that’s just our experience but I’m not convinced Amazon is a monopoly here.

I do think Amazon needs to be held liable for fake products and whatever damage they cause its customers. Amazon simply selling goods with no liability of fraudulent items is a disgrace, and I don’t think they will change until we ram some regulation down their throat.
Bitcoin's Mempool Visualization for the Terminal
“The Grid” AI website builder disappears with millions of dollars in member fees
Remember "The Grid"? It was a much-hyped website builder that supposedly used AI to automatically design websites. All that remains now is a landing page https://thegrid.io/

All of the websites people created are locked, the founders disappeared on social media, and no one who paid hundreds of dollars for "lifetime" memberships are being refunded. What a disaster!

Twitter Drama, conversations about people filing class action: https://twitter.com/search?q=%40thegrid%20%20&src=typed_query&f=live

Reddit Drama: https://www.reddit.com/r/theGrid_io/hot/

Summary of the saga: https://www.pagecloud.com/blog/what-happened-to-the-grid
Shopify joins Facebook’s Libra currency association