skysight-inc/HackerNews huggingface dataset:
Still similar things are available in other languages, e.g. https://docs.scala-lang.org/overviews/core/string-interpolat...
I've seen horrible inheritance/convoluted refactors done in pursuit of DRY.

I'm a bigger fan of WET(Write Everything Twice). Usually the first iteration of a component you don't understand enough of the domain space to get the abstractions right. So use that first attempt to explore the issues/problems/corner cases. Once well understood, rewrite it into something concise and well abstracted.

I've also find that if you try to re-write a third time you'll end up being to clever in trying to predict where a system will evolve and get you right back into the same situation as the first iteration.
Balancing 3 and 1 is damn impossible for me. I do a ton of 3 and can't focus on point 1.

Though that literally seems to be the point of the article...
What is that language?

edit: seems to be a custom language designed for the purpose. .agc file extension corresponds to apollo guidance computer.

https://en.wikipedia.org/wiki/Apollo_Guidance_Computer
Internet of Things Programming Projects
If nobody thought like this you wouldn't have people building sky scrapers and collecting garbage in the winter
Why do you want to abort when prio is in endidle or busy, and not in other cases?
They would have to rebuild (re-sign) and reinstall weekly. The opposite of Just Works.
Some languages like golang, doesn't priorities concise code, it often takes a few lines to do something trivial. Find the object in a list with the lowest lexicographical ranked value of some property.

The code to do this is simple, but not concise, leaving a comment so I can scan the function and skip 5-10 lines doing something trivial is nice.
My (poorly articulated) point is that all the non-class markers we use to oppress people - whether skin color, religion, accent, clothing style, music preferences, etc - just disguise class oppression. In the USA, I think we emphasize color in order to avoid the hard truth that society was created so that a few could fuck the many.

And I meant "white" literally, to point out the absurdity that poverty is a function of skin color as opposed to deep class organization. If light skin color is what made one rich and powerful, then Catholic Irish would be at the top. But...
Code shows how something happens (i.e., a string comes into a function and is parsed and only the date from it is returned), but it's so bad at showing WHY something needs to happen. My comments are almost always about why I'm doing it in the way I am, complete with examples of test cases where the users broke things in ways I wasn't originally expecting. Ten years from now, the code part will be rewritten using whatever crazy new stuff the language supports, but the underlying need for doing it at all will probably still be around.
The only way I know to get a good deal is to walk into a dealership, know exactly which car & options you want & say you're paying cash & are willing to pay $100 over the manufacturer's invoice. They'll cut the nonsense and take the deal.

90% of the games begin when you finance the vehicle at the dealership. Don't want to put $2000 down? Let's just add another year to the term. Or how about we add $50 / month to the payment? I watched in shock as salesmen would come back with increasingly worse offers in terms of total cost and customers would leave happy thinking they were great negotiators.

Americans are shockingly bad at math.
What's stopping existing car companies from doing direct sales like Tesla? Removing barriers to customers giving you money is generally a win. How many Tesla's were purchased in the last year that wouldn't have been if the stressful dealership was in the way?

How about a subscription / lease deal where they ship you the new model every year? Sell a cheaper tier for the 2nd year used vehicles. Do telemetry on driver safety and charge accident-prone drivers more! Replace/bundle/improve car insurance while you're at it. Are there regulatory hurdles preventing this for a company like Ford or Toyota? Is it just organizational momentum stalling these changes?
It’s not direct, but the result can be the same (and it’s not just about being poor, it’s about a low credit score meaning you get shitty loan terms or a landlord isn’t willing to rent to you). I won’t defend the social credit system, but I do think there are enough parallels with credit scores that it’s worth mentioning in the interest of getting some justice in that area.
All coffee has poison in it. Acrylamide is a known carcinogen. Caffeine is also poisonous: if you drink about 100 cups of coffee it will literally kill you.

You'll have to be more specific about the type and quantity of poison.
I think repeating the same concept in different ways just makes things harder to read, not easier. Comments also sometimes reference code outside of where they are placed. This leads to them becoming misleading and incorrect.

I find that comments can be a last ditch effort to make hacky convoluted code look better than it is. It can be an indication of lack of thought and planning and later obsessive documentation to make up for it.
My point was not really to mention a particular programming language, but rather to make the point that people seem to continuously reinvent the wheel rather than reading up on history and investigating other programming languages.
If you only know C/Java/Python/Go and you learn about <radically-different-language>, it will probably make you a better programmer even if you never write a single line of <radically-different-language>.
Looking thru my papers last night I noticed another forgotten cost, moving and parking tickets, traffic school, and fees that double every twenty days if not paid promptly. No other government service occurs within an order of magnitude as quickly.

Our city is particularly predatory in that regard so I can expect a couple every year even though I drive only once a week.
Regulation. Most states don't permit car sales without a dealership.
The comment claim that every branch is accounted for and yet few functions below you can see this is certainly not the case.
They should either have fixed it first and then make such comment or shouldn't make such comment at all.
Otherwise this looks a bit cringey.
What’s stopping them? Laws in pretty much every state. Laws that have been one of Tesla’s biggest pains. They’ve managed to overturn some of them, but most the time they just get special exceptions carved out for them.
The reason not to post a comment like this is not that it's false, but that it's an even worse exemplar of the same phenomenon.

https://news.ycombinator.com/newsguidelines.html
It's really only useful in areas of codebases that either a) are very complex, b) touched by many people or c) both. When that happens, everyone prefers that there is a lot of documentation, especially about the why. With older codebases the question is always whether this is an actual bug from the developer or is there a reason why it's doing this super-weird thing and if so is it still applicable. What's happened over the last 5 years is that automated testing has become so mainstream that places without tests are the exception AND the tests have replaced the need for comments.
def we_need_to_treat_all_transactions_on_february_29_as happening_on_February_28_see_customer_ticket_#4321_for rationale:

obviously
My bank and credit union both offer car buying services via TrueCar (which my bank actually owns around 10% of so they really encourage people to use it). In my case I paid around 5% less for my car than the "best" price I was able to get by visiting a dealer and going through the traditional song-and-dance routine. It seems like one of the big benefits is that they make it really easy to check the prices at a bunch of dealers. I don't remember if they actually offered any substantial saving at my local dealer compared to the price I "negotiated", but I was able to find a dealer that was willing to do a cheaper price around 70 miles away.
Is this something like

https://en.wikipedia.org/wiki/Boeing_X-37

just a suborbital variant that carries a warhead?
Now i'm squarely in frontend web-app development right now which definitely changes things (mainly the complexity is centered around enabling fast changes/additions to the codebase, and not the actual business logic for the most part), but while "deep functionality and small interfaces" sounds good on paper, most of the time giant files with a few functions exported aren't a good way to manage that.

Sure, it solves the problem when viewed from the outside. "users" of the software (users being other devs in this case) get a nice small interface and docs that explain how to use it, but internally it's much harder to work with. Having everything in one file like this without breaking it into "sub modules" for various parts of the module means that you need to almost have a complete understanding of the module before working on it.

In this case, I have a feeling that is a pro not a con. Because this file is so core to the system, and has so much complexity, that breaking it up into smaller parts could cause a dev to feel like they understand it only to find out they don't after it's released. And it means that any devs that truly do understand it top-to-bottom would just waste a lot of time switching around files if it were split up.

Putting it all in the same file here nudges you to really make sure you understand it top to bottom before making any big changes. It's intimidating and scary for a reason, because at its core it is a complex piece of code, and dressing it up in "simple code's clothing" won't help.
> Now if I _ever_ came across a useful Haskell product

There's at least git-annex and pandoc
A search for "Haiku Webkit" brings up...

https://github.com/haiku/webkit
> The failure of its designers to see that it would mostly be used as a platform for money laundering

Is there a source on this? I have a hard time believing that's what it's "mostly" used for.
Exactly. True, code could be self-explanatory, but sometimes you need to explain why code does what it does.
Running it in production is the point. An idea is pursued to validate the market for it, not to accomplish building a scalable, secure solution for which nobody wants.
The Precariat: A Disruptive Class for Disruptive Times
I think it's because point 1 has diminishing returns. You start having to invest more and more time to get deeper and deeper in one narrow thing. It's much more satisfying to develop breadth (imo) because you get about 80% deep and then stop before the diminishing returns kick in
I agree with the general sentiment of your post, but the idea that Kafka is somehow less painful to operate than Rabbit is ridiculous. I love Kafka, but I can't think of a more painful software to maintain in production.
That's not really a limitation of the "language" but more of an implementation detail of GHC and Prelude imo. There are very few escape hatches from the type system and you can run the compiler so that these cases are treated as a compile time error.
I actually was part of the CORE team. It's nice to see people actually reading it!

In my (biased) opinion, it is a very good introduction to the _economy_, though it is perhaps too light on _economics_ [0]. That is to say, it is much, much better than other introduction-to-economics textbook at presenting the relevant facts about the economy but is a bit light on analytical tools. If one wants to go beyond this textbook, they would have to learn them. If I were to offer a comparison, CORE econ is to traditional econ textbook what a natural history of the universe book might be to a physics textbook: many more topics covered including those that would not be addressed in an intro textbook but less studying of models.

Hopefully, if it catches on, we will hear fewer people arguing "Well, it is just basic economics that X" where X is something that it true in the toy model of econ 101 that is useful for learning but not really in real life.

I would suggest completing this book with some econometrics - since it is those tools that allow us to (try to) see which theories may be right and which may be wrong. The books by Pischke & Angrist are good: "Mastering Metrics", and at a higher level, "Mostly Harmless Econometrics".

The Journal of Economic Perspectives [1] is a great resource to learn more about a topic in economics. As it says:
> The Journal of Economic Perspectives (JEP) fills the gap between the general interest press and academic economics journals.

The HN crowd would also most likely like the Quantitive Economics lectures [2] from Sargent & Stachurski.

[0] It is also a low density textbook, which seems to be common in American textbook

[1] https://www.aeaweb.org/journals/jep

[2] https://lectures.quantecon.org/
This is great! Very well done.
My favorite part from that: https://github.com/chrislgarry/Apollo-11/blob/27e2acf88a6345...
The only thing I want from Swift 5 is easier string handling. I just want an easy and concise way to do things like split a filename into parts, extract regex matches, etc. At the moment it's faster to write string handling code in Objective C...
I think it's usually a sign of a poorly understood domain or a poorly modeled problem. It's not a good sign; it's not necessarily a bad sign; it's (at best) an admission of one's limitations.

Comments become useful when behavior is implicitly tricky. Ideally you'd make the "trickiness" tangible and expressible in-whatever-language you're in, but that's not always easy to do.
I generally find that a high comment to code ratio, if the comments are of the form "Do this thing because of this reason", indicates quality. It indicates the programmer both knows what they wrote and why they wrote it, and it helps future maintainers figure out under what circumstances the code can be changed, refactored, or removed and under what circumstances the original behavior must be kept.

A high comment to code ratio, where the comments are of the form "Do this thing in this way," indicates a lack of quality - generally a sign that the programmer is not confident enough in the language that they're writing in, and is trying to solve language-level problems instead of business-level problems.

Uncommented code better come with some reference for why the code exists in the form it does. Sometimes commit logs and the VCS "annotate"/"blame" feature works. Sometimes commit logs link to bug trackers or feature requests. Sometimes there's a README. If you don't have any of those, I tend to find that it's generally low-quality code.

Our purpose is to deliver business value. (Or non-business value, as the case may be; if you're writing a free video game for fun, you want people to successfully have fun.) Our purpose is not to generate lines of code. All code is, to some extent, legacy code; comments can help it be manageable legacy code, or make it even more unmanageable.
I might have misused the word expressive, I don't mean bloated code with more than necessary logic.

I just meant simple to understand variable, function, and class names. That combined with small classes and functions, makes following the logic of your program extremely easy.

Following concepts like DRY (don't repeat yourself) and the single responsibility principle ensure that you're making more easily testable code, and I'm sure less overall LOC.
I get mine at one of the myriad of online retailers, who seem to be outside the clutches of that corporation. There's no restrictions duties or tariffs on importing eyewear in the US and the prescription sheets are technical and specific enough to be fairly language independent.

The internet disrupts consumer by consumer and product by product, not industry by industry.

Going to a brick and mortar certainly appears cost prohibitive once you get used to paying $10 for stylish fitted pairs of prescription glasses.
You probably don't want to hear this, but don't mess with your brain biochemistry. The brain is a delicate system and introducing artificial changes will probably harm you in the long term.

Your question is also very broadly phrased. What do you mean by "win/lose" ratio? For what purpose would you take Nootropics?
There's no negligence in giving software away for free. No one is stopping users from doing their own security audits, or hiring experts to do it for them. Beggars can't be choosers, and if users are upset at anyone it should be the thief.

Cryptocurrencies are speculative trading vehicles, not money. No one actually lost anything of real value. A fool and his coins are soon parted.
Designing for flow
For those that haven't had the Tesla experience, it's a refreshing change of pace. They don't have dealerships, only showrooms and service centers. You can schedule a test drive at a showroom (or online), and your rep will be happy to help you configure your car right there if you decide to buy, but you can also go home and leisurely plan your configuration over the internet. You can see the price of every option before you add it, and when you're through, you get an exact total that you can pay through the website. No pressure, no haggling, no upgrades. When your car is ready, you pick it up at the service center. That's it. The cars aren't cheap, but the buying process is the most pleasant I've ever experienced.
You will hit these problems when you deal with salespeople on the floor and not salespeople in an office. That being said, here's hoping you never have to own a car. I'm stuck burning dinosaurs and it sucks.
This code would probably a lot shorter if every function call was not followed by a ‘if err != nil’ statement. This reminds me of Win32 programming.
Sure use whatever metric you like. That one is also still significantly below the peak set in 1999. They're highly correlated.
As a completely unverified anecdote perhaps related to the Social Credit System (and more so the amount of information being collected and distributed in China), my SO recently told me about her Dad's attempt to order pizza. It went something like:

SO Dad: Hi, I'd like to get a large supreme pizza

Pizza Op: Hello, SO Dad. I can help you with your order. Is the food being delivered to 123 Main St?

SO Dad: Yes.

Pizza Op: And can I call you at 123-4567 when the food is delivered?

SO Dad: Yes.

Pizza Op: Ok. I see that you are reported to have high cholesterol. Can I perhaps interest you in a vegetarian pizza?

SO Dad: Okay. That's fine.

Pizza Op: And I see that you have a family of 5 people. Should I add another pizza to the order?

SO Dad: Sure.

Pizza Op: Alright, that will be $30. Will you be using the payment information we have on file?

SO Dad: Yes, please.

Pizza Op: One moment ... Sir, the payment information we have is not working.

SO Dad: I can't see why that is. I drive a nice car. Can you try again?

Pizza Op: I tried again and it did not work. I see you are 100m away from our store. Can you just come down and pay in cash?

SO Dad: Ok. I can do that.

Pizza Op: Great! The pizza will be ready in 20 minutes. Please pick it up then. Good bye.

Again, this is unverified and I don't know if she embellished parts of the story, but the idea that a pizza clerk can pull up your location, family information, and brief health record so easily is shocking. I suppose customers talking to clerks at restaurants they frequent will be able to glean some of this information over time, but the impression I got was that this was a "first time" order and the clerk was able to just look all of this up.
The most useful product in Haskell for me personally is pandoc the universal document converter.

https://pandoc.org
...flip it around and talk about how ignorant westerners are of their own history.

However, researching, blogging, or talking about such lesser known dark/embarrassing events will not get you or your family barred from travel, public schools, and such.
I'm not sure why this is being downvoted. I know sociology was meant to be a placeholder for any one of seemingly worthless degrees, but the commenter has made a convincing case for how sociological analysis could have helped silicon valley social media firms (at the very least) recognize the kind of impact they have on society and be more responsive those impacts.
>The example of the judge is an instructive one, although a little extreme. Due to the immense power vested in judges, even the tiniest perception of bias must be avoided.

You can avoid being subject to a judge by not violating the law.

You cannot avoid being subject to the law.

If you think the "tiniest perception of bias must be avoided"for judges (who interpret the law), then the same extends to those who write it.
Good luck finding people who are 2 of these, and it is not possible to judge people with existing limited interview processes. This list is impossible.
PUBG definitely took a lot of inspiration from Arma's gunplay, although for whatever reason the glitchy jankiness in Arma annoys me less than it does in PUBG. Maybe because the bugs in PUBG tend to have a greater impact on the outcome of fights.
But what if comments pertain to unexpected states the system as a whole can be in?

Kind of the whole problem is when there are weird corner cases going on that straddle function boundaries.

I'm not saying that's a good thing; mind you - but nor is it always trivially avoidable, especially if code needs to be concurrency and/or exception safe -- or in general whenever the statements your function consists of have surprising and opaque behavior based on system state, particularly if said state is hard to grasp due to being implicit or dynamic, or simply large and complex.
I'm so impressed it can just be launched with the Clojure cli tools (not sure if I'm phrasing that correctly). Very cool project. I've recently admitted to myself I don't actually like modal editing (but love keeping my hands on the keyboard) so I'm happy with default emacs (caps-lock to control always!) but I hope this project gains some appreciation.

Clojure has been so fun to learn and I really like the community. The various projects and tools coming out seem to really jibe with my wanted approach to learning this whole software game.
Yes, this is the engine behind Haiku's built-in WebPositive.
If you care to understand the code I pasted, here's the full listing:

https://github.com/chrislgarry/Apollo-11/blob/master/Comanch...
.. that said, Kafka is written in Scala.
> For you to center the conversation around those arguments shows you're not very informed on the topic.

I've been following Bitcoin for almost its entire life and am probably vastly more informed than most of the shysters who show up on sites like HN to shill their coin.

> A lot of developmental progress in the ecosystem with models/architectures, tools, and infrastructure hasn't happened until recently (past year, give or take).

I've heard this line forever. Lightning network, for example, has been "just around around the corner" since forever. So far, it is still just as "just around the corner" as it was 5 or 6 years ago and ranks among the top all-time vaporware software projects out there.

The attempt to refocus on "The Blockchain" is only done to distract from the fact that Bitcoin, poster child of "The Blockchain" has no lawful use. It doesn't scale, it isn't free, it isn't trustless, it isn't censorship resistant, it isn't a good store of value, it isn't instant and it isn't anonymous. It isn't even deflationary (as if that is a good thing) because it has been forked and cloned thousands of times. Oh yeah, it also requires more energy than small nations to secure. (And don't feed me the line about it being "green energy" or "less than conventional banking"–we both know that is a laugably horseshit argument)

The whole space is a joke. Aside from self-driving cars, Bitcoin will be the biggest overhyped pile of complete nonsense this decade.