skysight-inc/HackerNews huggingface dataset:
Interesting. The building is repaired, new roof and windows and floor and ceiling, soon only the frame is 'original'. But the building is not the 'business'.

Every day, the product on the shelf is new. New customers go through the door. Even the product formula or process may change.

Generations pass, and entirely different people are standing in that building selling those (changed) products. The people may have some genetic similarity to those that stood there before. But any human would have substantially the same cell chemistry, which is many millions of times more in common than a particular strand of molecules. So won't any human be enough?

The definition of a 'business' is a human idea. Its not rooted in physics. So if we want to say a business is old or continuous, I guess go ahead.
Leopard also got rid of Classic, which meant I just couldn't use it if I had wanted to at the time. At that point there had been a long-time legacy of backwards compatibility for the Macintosh, and I was in a position where I frequently needed to retrieve data in oddball formats from older Mac software. Tiger for Intel already didn't have it, and from that point forward Apple's attitude to backwards compatibility has seemed to be to operate at the minimum acceptable level.
Undersea Expedition Planned to Retrieve Titanic’s Radio Gear
Complete ignorance is the conclusion of that line of thinking. The fact that this person hears "some" news is only an unfortunate consequence of existing in a world with other people. If they could they would remove that from their lives too so they could be even happier.

Complete ignorance was the premise of my remark so it doesn't really make sense to say it's far from complete ignorance.
This is how I learn mixed with understanding the tool / framework / language from a first principles point.
I don’t think reaper is open source. It is, however, pretty good, and cheap.
The possible origins of 2019-nCoV coronavirus include laboratory in Wuhan
I think time plays a role. Trying to learn complicated stuff fast usually leads to not learning them well enough, in my experience. If I do so, jumping to wrong conclusions or applying a method on the wrong place/in the wrong way is almost guaranteed. So just keep reading, studying, picture yourself explaining it to a classroom, talk about it to colleagues and friends, engage on discussions about it online. Eventually you'll master the craft before you know it, and the good part is that such things may be on constant evolution and there will always be something new to learn. Just avoid being that one trick pony that knows a lot about one specific topic and that's it.
> I'd argue that assuming everyone is just that good isn't too far off from assuming everyone is so good that you really don't need tests at all.

I'd argue unit tests aren't made to stop developers from pushing bad code, they're made to prevent future developers from breaking it even further.
The first wysiwyg editors (front page, golive, dreamweaver, etc..) were heavy abusers of tables.
If you were to donate $1000 to "open source", not much would actually get anywhere useful IMO.

On top of this, as a company, donating is… complicated. If you can do it, great, but it's often easier to find a project that has a support contract and pay for that. It gives you a real and justified expense and is in general more stable income for the devs.

Furthermore, a renewable contract gives the project predictable income, which is instrinsically worth more to the project.

If you have $1k and just want to give it away once, and want it to end up in open source, I think what's best is you pick your personal favourite project and double check they both need and can take the money (then move down the list if they don't). But if you can afford to give a recurring donation, go that route instead! Patreon is a good avenue for smaller projects that don't necessarily offer contracts of their own, but at that point there's a lot of money that goes into their fee.

Edit: Another potential avenue is donating directly to a developer for their open source work (Github Sponsors will let you do that), assuming there's a dev you like a lot for that.
Didn't downvote you and Im not denying that what you’re saying is to some extent true but want to point out that’s mostly the case for the old rich. The new rich get affected quite badly by this money bug. At some point money becomes second and power becomes #1, in other words there’s never enough of it because more is needed to feed the ego/power, worries never subside - worries of a different nature than poor people’s, such as maintain that status, comparing with others at that level, that others are to take advantage of their wealth, power games in the family, inheritance nightmares, false friends, trusting no one, not even the partner sometimes etc. These are demons of money. Sure, there are rich people that are truly illuminated which detach completely from that world to pursue other things but these are usually not first gen.

If you want to make a correct generalization, moderation is the key goes a long way.

Personally, my financial goal is to become self sufficient (decent but modest pension and such) and that’s about it. Amassing wealth and spending lots of money does not interest me in the least.
I bet on some level they know and don't care. If you're buying a cheapo key off of ebay then chances are you were never going to pay the full price. Meanwhile they're still using the software, learning how it works, and growing the Windows ecosystem further. Vaguely like a loss-leader that gets people in the door.
I've long been intrigued by pure FP, advanced type systems and proof assistants from an academic point of view but haven't yet been convinced that the effort involved in learning such systems/methods pays off in most cases (without taking into consideration the costs you still have when you already know the methods well). I will still try to learn more about this, but without any strong conviction that this needs to be immediately useful.

By contrast, I've only more recently started hearing more and more about model checkers such as TLA+. The case studies in this blog post serve to give a good motivation for why such systems might be useful (as well as honestly presenting drawbacks; something that advocates of e.g. PFP rarely do). I would love to use something like that one day.

As an aside, I still think it's a disgrace how irrelevant empirical research is to most aspects of today's software development. Another blog post by the author cites a paper claiming that very simple testing, especially of error conditions, would be able to prevent a huge chunk of production bugs, but things like that are rarely talked about. The whole profession is unfortunately amateurish and always obsessed with fads and trends instead of taking a more analytic and empirical approach which makes me sad.
Or just run `shuf -n 6 /usr/share/dict/words`
Show HN: Business Structure Calculator
I'm reasonably sure that fission was discovered by Otto Hahn and Lise Meitner sometime in the late 1930s, few years after Fermi accidentally split the atom without realizing it.
If you are interested in foobar-like players for Linux, DeaDBeeF may be worth looking into.
ZFS program: Lua interface for administrative scripting
I find that my brain sort of automatically uses connections. The really interesting thing about SRS is that you don't have to consciously think about how you're going to remember the cards. Like, you don't consciously think, "Ok, what's the pattern here, how can I turn it into a mnemonic..." Rather, your brain subconsciously does that for you.
Your tests are there to prove that every situation you can think of still works correctly after change. They should be on specific data not random because you are creating specific tests of situations you are afraid could break. As my mentor told me years ago "Keep writing tests until boredom overtakes fear" - in other words if you are afraid of random data pick some specific random data and write the specific tests for that.

The problem with random data is they don't fail often. Instead of random data in a unit test which can go years before it finds the bad input you should turn your random test into something either a fuzzer or theorem prover (the tools solve slightly different problems so both are good) can use and let the tool run for the hours it takes to get results.
That would be "Musician", not "Muscian". The actual link spells it correctly.
I am fairly sure this is not the optimal way, but I've been learning complex information/structures in passes.

For example:

- 1st pass - I consume the materials as well as possible, and apply my knowledge. Typically, I have to look things up, some things are unclear, I can't remember much. Applying the knowledge is quite difficult. That's ok.

- 2nd pass - I return to the materials, re-read much less thoroughly. I realize some things that I missed, or got wrong. I apply my knowledge, without looking information up again. This is, from my experience, when I get most of deeper understanding, but also where I learn most things that I remember long term.

- 3rd pass - if necessary, I can go through the materials again, just like in the 2nd pass. Diminishing returns start to kick in.

- (3+n) pass - diminishing returns start to manifest even in form of being bored with the materials, and starting to build up mental dislike for the materials/topics.

The passes are effective if and only if they are some time apart. Ideally, they are spaced in increasing time, i.e. 2nd pass is a day after 1st pass, but 3rd pass might be 3 weeks after 2nd pass.

The above has been useful for me, for example, when learning math or when I started to learn development way back. Note that in all passes, knowledge is applied. Without applying the knowledge, I learn much much less (though not nothing).

It also assumes that you have quite good theoretical source of information (e.g. a math textbook) and practical problems (e.g. math problems with correct solutions). If you're missing one or the other, e.g. if you're memorizing history lessons for your history 101 test, I'm not sure how effective the passes are.
I believe so (speaking as a React developer for the last few years). I'm sure a few people at Apple have looked longingly at React Native and the concepts there.
life has a lot of parts, major is in the eye of the beholder
Seriously very nice design for 2000.
It’s truly mind blowing how intelligent comments can be here, but the circle jerk of engineers vs non engineers rings so loud.

Good PMs know how to gatekeeper from other departments and leadership, identify engineers strengths and defer to their expertise, and remember answers to the same technical questions so they can at least build upon their knowledge of the craft. I have no clue how rare they are, but those are what I try to do on a regular basis on top of disseminating information as it changes from product stakeholders to engineering.

I can list a whole host of reasons why engineers can flounder without a mediator between product and marketing leadership to make sense of requests. I’m also acutely aware that great engineers can make things work in lieu of someone who owns that process.

I’m not going to bash engineers as a whole though. I’m not ignorant.
Personally, I am a big anti-fan of the Spaced Repetition.

IMHO it is a wonderful solution to a wrong problem (i.e. memorizing random things). Sure, there are use cases: learning words in a language one is not exposed to on a daily basis or cramming for a medical school exam.

When one actively uses something, there is a natural spaced repetition of the things that matter. With the frequencies as these things are used in practice. Everything else can be looked up later.

For programming, maths, physics, etc - "I forgot" means more or less "it is more time-efficient to google it once a few years than put effort in storing in in my memory". In programming, it is even more the case: libraries, their APIs, and good practices keep changing. Rote memorization may be highly counterproductive in this case.
I use a process I made up based on how suspension bridges are built: 1) literally an arrow is shot from one side to the other over the span the bridge is to occupy, and that arrow has a kite string attached; 2) the kite string is used to pull a thicker piece of twine; 3) the twine is used to pull rope and the rope is used to pull steel cable; 4) with the steel cable in place, the large scale bridge construction can begin.

In a software context, first just get anything operating in the target space you are trying to learn and develop. Then expand that minor nothing piece of software to be just slightly more capable, and observe what adjustments were necessary in your thinking to get that minor adjustment working. Repeat this process of small iterative changes with a formal review of what you're learning, and at some point you'll realize you have developed both a body of knowledge and a small framework for further work, and probably several ideas how to "fix" your mini-framework. Now spend some time trying to fix the mini-framework and use that to solidify what you've learned. And throughout this entire process: take notes, review the notes, and observe the scientific method in your notes: meaning write down a hypothesis, test it, write down the test results, write down you thoughts on the test results, and repeat. The writing down portion is important, as the act of writing it into notes forces fragment sentences to be formalized, completed and that can catch incomplete thought processes, which are critical, as they are the edge cases that also need to be handled.
Wiki data has decided "no" to your question, all contributions are under CC0
I traveled to Cuba in 2012 as part of a research trip and seeing all the ways people have managed to hack together fixes for everything was perhaps the most incredible part of the experience. The embargo makes it difficult for Cubans to get a lot of things we take for granted but the Cuban people are perhaps the most inventive I've ever met. Living under the sanctions for decades has made creative problem solving a part of their culture.
This is a bit off topic maybe, but I have heard SAP works with tens of thousands of tables. Is that correct?
These simple sites show us something profound: If you want something to last, don't base it on something that won't last. There are a some technologies that will never allow somebody to build a site and leave it unchanged for 20 or 25 years. Cold Fusion comes to mind. Almost nobody hosts it anymore for one. Can you imagine running the same WordPress version for 25 years? The version of PHP it runs on will be EOL long before.

I guess what I'm saying is that if you want to build a site to last 25 years without numerous redesigns, build a static HTML page.

Looks like Web 1.0 got something right after all :)
Why do incompetent managers get promoted?
Surge isn't a replacement for Serum, but the original developer cofounded BitWig. It's probably the best sound you'll get out of a Linux-native synth. You can even use Serum wavetables with it.
PS Happy to answers any questions about Tokyo life as an engineer/entrepreneur, just reply to my comment.

I get where you're coming from, but you can make the same one-sided joke post about Americans.

Having done both...

- started YC backed startup while in SF and worked at Uber for 4 years
- in Tokyo for the past 2 years

I honestly think that the outcomes here in Tokyo are much better than in SF. Yes, incomes are lower, but your QAPP (quality-adjusted purchasing power) is significantly higher, at all income levels - https://www.japantimes.co.jp/opinion/2017/08/21/commentary/j...
The credibility of news articles plummeted before and during the Iowa caucus
Show HN: Remotehh – Virtual hangouts for remote workers
If you are going to auto generate an api for a database, just use SQL. Adding extra steps between you and a database with no encapsulation is just adding extra steps for no reason.

One of the key things you need to do in good database design is to map business verbs to API endpoints in something like a 1-1 way. Having an api endpoint that is essentially "insert this row to the database" is just cargo culting. There is already an API for that, it's called SQL.
The article starts with this sentence:

"Whether you have an iPhone ( $699 at Apple ) or Android phone, Google Maps logs everywhere you go, the route you take to get there, when you arrive and what time you leave -- even if you never open the app."

Where iPhone link actually is an affilate link to Apple Store which (I assume) pays money to CNet for advertising it.

Am I the only one that considers this a bit suspect? Especially in an article that's talking about Apple's competitor?
Yes, ArtGem (https://rlvision.com/artgem_about.php). We were a couple of guys that tried at making shareware, but sadly failed. I continued running the site to host my own utilities, some of which eventually turned into shareware. I don't earn much money from it, but I enjoy making software and it makes me happy when other people find them useful as well!
Romans used to do adult adoptions. Off the top of my hat, I clearly remember that Cesar adopted Brutus, his killer, as an adult.
Amish communities vary wildly on what is acceptable from community to community which can include trivial things like colors and cuts of garments, phone usage/location, type of carriage/buggy features, and what level of mechanization is tolerated. It rarely has a logical reason beyond "this is the way" and is generally dictated by the elders of that specific community. The differences also extend to things like the conditions they'll let a member formerly in good standing return and courtship customs.

If you read Ira Wagler's book Growing Up Amish, he covers some of this as his family (and him alone) moved around various Amish communities in North America.
> a mix of two ends of the visible spectrum

Wasn't that about magenta/fuchsia? ( #FF00FF )
plus with some of the low star reviews you can compare what they stated was wrong with your own expectations of what could go wrong with the product.

the only two considerations for me are the number of reviews and the quality of the low star reviews for the same. the dates of reviews is very useful as well, if a product doesn't have many recent good reviews it can offset the number of reviews in my view
The mass of the Alps cause a dilation in space time
Wiki data has decided "no" to your question, all contributions are under CC0 (functionally WikiData only stores raw 'facts')
Which isn't really different then churches, which may be older than the church building. "The church was founded in 1890. The present building was opened in 1950, and the old building is now used as a hall." Sometimes you might even see "The church was built in 1890. A new building was opened in 1950, but they burned down in 1984. The present building was finished in 1986."
Perhaps they could limit refunded products to 3 star or below? Really there isn't a good reason to positively review something and take it back, if it was your fault eg if it didn't fit, then you could just not review it.
Re installing Linux: I did that many years ago already ;) I used to enjoy an alternative Unix laptop provider and hate to see Apple fade away as an option. Regarding searching reddit and co, I briefly did, but then thought if I have to go to forums etc., I can just as well run Linux on a well-supported notebook in the first place.
Wait, how do the rest of you test if a field accepts or rejects html?
When I was in grad school, I fell into a habit of going over everything up to 3 times.

The first time was a real quick read-through - really more of a skim - just to get a sense of the overall shape of the subject.

Then I'd go back and actually read the bits that I needed to understand more thoroughly. While I was doing that one, I'd take some notes, because I find that helps a lot with retention. I wouldn't be trying to memorize everything here, more just trying to get a thorough enough understanding that I could quickly re-find information when necessary.

Finally, for anything I absolutely had to have in my head, I'd make flashcards. This part can be indispensable, but I tend to be pretty conservative about it. I'm fond of that (apocryphal, I think) Einstein quote about not memorizing such information as can be readily found in books.
I use the 1st, 2nd, 3rd pass methods but use SRS.

1st pass is high level concepts, 2nd pass is more details, and third pass is anything I still dont know.
The myth of EDS' Ross Perot's Iran rescue: Daring raid – or just a good book?
Whenever I need to update the site.
That applies to any platform though. It being open source doesn't mean it won't be abandoned or become poorly maintained. Look at the massive churn web frameworks have seen.

Cloud tooling definitely has the problem that vendor financial troubles = a sudden "our incredible journey" and poof, your app is gone. That's something client side apps don't have to worry about.
I wonder what the average account age and purchase total is of genuine amazon accounts. Seems like setting some sort of age and purchase threshold to reviews could make the fake review game a lot more difficult.
Moths are outside you don't need to buy them. Crikey not everything needs to be bought via Amazon.
That sounds extremely icky, to say the least. "Synthetic memories"?
Slavery is not a crime in almost half the countries of the world – new research
Yes - the killing is done arbitrarily without warning. Just like on iOS. It is the recommended behavior.
>Unfortunately, the donation for one project will be quite small as it is just a fraction of the donation of 1000$.

>Do you know any platforms or good solutions to distribute the 1000$

Well every project will get a part of it regardless of how you do it :D

>very time consuming and cumbersome

If you really care and want to donate this should not stop you.
I do this in reverse. First blaze through reading with very little comprehension, then go back thoroughly.

My reasoning is "I don't know what I don't know" on the first pass and my first goal is to understand that all of the things "exist", then how things individually work.
How to fix the way calculus is taught: make it exciting again
This is the exact curve that is described by an academic in a recent episode of planet money https://pca.st/episode/d1397f9e-49f0-425c-8b10-3c4adb039f3f
I suspect solving it is hard to impossible. You can heuristic anything as suspicious at a glance but moderation at scale fails. You personally can decide "this review is bullshit" and block without issue but start flagging in a false positive or even true positive by a manipulator looking to start shit could cause considerable backlash as a futile attempt at pleasing everyone is made. Transparent and consistent rules invite gaming and opaque ones invite accusations of malfeasance and the uncertainty promotes bad feelings and bad behavior.

Worse still is that even taking a stance to not take a stance because you know it cannot be done will bring backlash as there are many who demand you take their stance, even allowing easy distribution of self chosen block and filter lists are not enough. There are many who demand the appliance experience.
Delphi was pretty notorious for having some sort of tick/tock quality problem, for unclear reasons. Presumably some kind of botched project management inside Borland.

Delphi 1 was a mess. Delphi 2 was rock solid. Delphi 3 was a buggy mess. Delphi 4 kind of recovered things but was never as good as Delphi 2. By this point we'd figured out the pattern and skipped Delphi 5, if I recall correctly.