skysight-inc/HackerNews huggingface dataset:
I wouldn't discount something simply because the underlying technology has been around for decades. People said the same thing about Slack being nothing more than IRC. Didn't stop people from talking about how it was the future of work, or whatever.

For that reason, and many others, we really shouldn't ignore the amount of innovation in software and web that is largely design-oriented rather than engineering-oriented. A lot of venture-funded darlings out there are built on decades old technology, the key difference mostly being the design decisions that went into the product.
I thought one of the selling points was that everybody can check the contract...
> And if they didn't, they should've eaten those expenses or at least grandfathered old repos.

Why should they eat the expenses of abusive users? As well they clearly have and are finally taking action about preventing it. Your entire post seems extremely entitled to their money.
Does this mean any possible audio or video a real human can do, current ML can fake with enough quality of data? Like there's no possible test a real human can do which can't be faked, given the relevant data?
Oh I am not debating wether or not it is healthier. I am talking about Fast Food.
> Honestly just buying a Roomba is a pretty good signal that you have some money to burn but not so much that you can hire a maid.

Or you're a sucker for gadgets that are sold at high margins and ultimately don't really improve anything in your life.
Or you could just use APL, which already has a high information density.

Lot's of useful APL programs are very small, easily fitting on a single stone table and would not be much trouble to retype. In fact good APL programmers are even able to memorize them easily.
Related:

De-anonymizing programmers from executable binaries - https://news.ycombinator.com/item?id=16598962 - March 2018 (39 comments)

When coding style survives compilation: De-anonymizing programmers from binaries - https://news.ycombinator.com/item?id=10806956 - Dec 2015 (67 comments)
The way I read that report: NSO has a policy of only selling to governments for anti-terrorism and law enforcement purposes; the Mexican government is a customer; the cartels have insiders in the government and/or have obtained the software from the government.

Sort of a corollary to government-mandated encryption backdoors, any offensive software under the control of a government should be considered public knowledge and integrated into your threat model.
> What's the difference?

There is an idea of balance of interests between the individual and the society. This is why for example your employer has to report salary data directly to the government but there are laws in place that control who else they disclose that too and under what circumstances. See also, for example, sex-offender registries, census gathering, etc.

NB: I'm not offering comment on whether or not the balance on those cases (or others) has been made correctly, just pointing out that it is a generally accepted concept in modern "western democracies" at least, and seems to be held by the majority of citizens unless you get pretty deep into the tails.
The end of the US/NATO hegemony / The rise of a BRICS equilibrium

If this is true, what does it mean? China will invade Taiwan? What else?
WWIV started, WWIII was the global war on terror. WWIV will be between major powers again. Better bring a hat!
I'm fairly dubious that there's any useful data here. Square footage, bathroom, bedrooms, and other such stuff is public record. Getting the exact layout of my rooms and furniture doesn't seem to bring any obvious benefit. I guess maybe it can try and identify appliances and such but again not really seeing that as a hugely valuable trove of data.
This is kind of a misconception a lot of people have about law. Especially in crypto, you’ll hear people gape “oh what, the government is going to ban random numbers? oh, the government is gonna ban something they can’t shut down?” I guess they imagine something more dramatic like secret police doing sting operations against every crypto user out there. In reality, they’re making a new stick i.e. once they have already decided to prosecute you for something, if they can show you used a mixer, this will be just a new charge to throw at you or a multiplier on your sentence.

I’m finding it a little difficult to put into words succinctly but as an example, they’re still going to after e.g. Coinbase: the big guys. They’re not gonna track down every party interacting with any mixer and prosecute because that’s hugely resource intensive. But now when they go after e.g. Coinbase, they have a new tool in their belt. (IMO IANAL.)
Agreed, but most people going through a drive-thru are not there to order something healthy.
... well, it has to be the right people. Perhaps it's worth a try, but I'm not sure there would be a spark like that.

If you put Isaac Newton in the same room as George Washington, it'd be two brilliant people, but I'm not sure they'd have much to talk about. They think about different problems.

What might be interesting, come to think of it, would be a Chat Roulette, but populated with these sorts of folks.
I was going to throw my old encyclopedias away, but then there came this wave of increasing attempts to edit articles on wikipedia to:

1. rewrite history through the lens of a political point of view

2. conduct disinformation campaigns

3. create hoaxes for personal amusement

4. conduct marketing campaigns

5. clean up reputations

6. redefine words to justify past lying

I decided to keep the paper ones for the time being.
Some of the tools I create for work are about fighting my own procrastination, half of the rest are about fighting the procrastination of others.

If your partner won't go to the gym, you can't make them, but you can make sure their gym clothes got washed. If your coworker won't do things, you can't make them, but their boss can, and that's easier if you've made the task more straightforward.
Living simply and for the better of others?
I thought to get a bridge loan, you had to find mismatched Indonesian sesame seed futures prices due to impending cicada hatchings.
This is crazy big news and no one is talking about it.
The criteria I tend to prefer is "expected" versus "unexpected" errors. I/O errors, especially network errors, are things that are going to be expected under reasonable operation, therefore it make sense that code should handle them. Similarly, user input resulting in incorrectly formatted code should be reasonably expected and therefore handled.

But the same kinds of failures might not be reasonably expected in other circumstances--I wouldn't expect that the internal configuration files of an application should occur in reasonable operation, and therefore it makes sense to panic if they're corrupted... even if the cause is an I/O operation on a local disk, or parsing some JSON or TOML or INI or whatnot file.

One implication of this is that it needs to be easy for any error system to promote an "expected error" into an "unexpected error"--which is what unwrap/expect does. The recoverable/unrecoverable error suggests that there ought to be no reason to do this, but there is absolutely a reason to do so: what category an error falls into is ultimately decided by the context of the error, not the generation of the error itself.
By 1995, it'll be evident that the Internet means as little as fax (1998)
Show HN: Image Manipulation via Triangulation
This project is a first principles approach to image representation and manipulation. I got interested in alternatives to the pixel grid, intrigued by the in some respect even simpler division of 2D space by the simplicial complex, i.e., the triangulation. The main concrete contribution here is a triangulation algorithm which is specifically retains contour.
I think we have compatible views. Each layer of the software must decide it's requirements and handle errors appropriately per requirements. You're right I didn't articulate when to handle an issue locally vs. pass it up. I think that's where requirements (and also explicit API guarantees) come into play.

I do think that APIs that "overpromise" by not returning the errors they do not handle to the caller, and instead halt or throw an exception, do their users a disservice in the long-run. These just become undocumented cases that bite you later on. Better libraries have all these conditions baked into the API itself.
I'm curious what other OSS firmware is using the G4 series?
I think people are seduced by some of the modern language features (like pattern matching, etc) by some of the third party libraries, by async [careful!], and primarily also by the WASM story that seems to be kind of going along with Rust. And by the novelty. And by promise of vaguely defined "performance."

But none of this is unique to Rust. And I'm not convinced on the WASM stuff at all for writing web front ends, though I'm enamoured of it as a generic backend managed VM, but that's another story.

And I think adopting Rust in many shops with a mix of developer seniority levels will be a productivity killer. I think most places doing this kind of thing would probably be better off with TypeScript, or Kotlin. Or if they want to go more functional and exotic, F#, Scala, OCaml, or Erlang/Elixir, etc.

But for places where we've been doing C++ for years and setting off footguns all over the place? Rust is great! Love it.
Heh, GP (I assume) and I initially parsed it as "don't just-use" (don't simply use) rather than "don't-just use" (don't only use).
Latest models have front facing cameras for object detection/recognition.
Maybe that says something about the quality of his words. He is a kingpin of insight porn.
Striveworks | Austin, TX | Remote, hybrid, or onsite (must be located in USA) | Senior DevOps Engineer | $175-200k + bonus, equity, benefits | Full-Time

Tech used: Kubernetes, Docker, Ansible, Go

Striveworks is building a low-code/no-code platform for data scientists to do impactful work at scale without a software background. Founded in 2018, we're profitable with stable footing in both the public and private sector, and we're looking for someone to bring our devops culture to the next level.

You will ensure that high quality and performant CI/CD pipelines are place, that deployment infrastructure (including cloud and cluster resources) has high uptime, that monitoring is in place, and otherwise help in all things containerization/cloud/k8s. This can be done directly or via self-service tooling to enable our development teams.

More details + application: https://boards.greenhouse.io/striveworks/jobs/5146743003

Send me your resume and get in touch: c.brim@striveworks.com
Feels to me like you have an Imposter syndrome, which can really take a tool upon a mental health. It is really common within the IT people. Regarding to motivation. People are built of habits. Once you start rolling out anything consistently, it will turn into a habit and you wont even feel it.
In my experience it usually is actually bad. The bad parts are most often not tradeoffs, but rather over-engineered complexity that could have been simple and improved development speed at the time too. Usually the issue is developers thinking of a bunch of things they might want to add in the future and implementing abstractions to make adding those things easy. But, of course, 1 out of 10 of those things ever actually end up getting built, and another 9 that were never planned for do, so the whole thing is a disaster since it was designed for X, but ends up being Y. This is entirely avoidable and can't be described as the traditional speed for ugliness tradeoff.
You can obfuscate source code also--see what people do with JavaScript on websites--so the answer is "no" under any case. (In specific, though, contracts are implemented in a bytecode, so by more basic definitions of "open source" the answer is still "no".)
Patriot Response Group – Full stack developer – Full time
Happy Monday.

My friend in startup space is looking for a Full stack Developer. If you know anyone skilled in Web, Mobile application, and API development, has SQL experience, is willing to learn new frameworks, has excellent debugging skills, and is looking for a new challenge, we would love to hear from you. Send your references and resume to DJ Ursal @ https://www.linkedin.com/in/djursal/. Feel free to forward this post to anyone who is interested and let me know if you need an introduction.

Required:
• Bachelor’s degree in C. S., Mathematics, Electrical Engineering, or equivalent experience.
• Minimum combined five years of programming experience in web and mobile-based applications.
• Experience building and maintaining APIs
• Experience with SQL, SQL Server, or PostgreSQL is a plus.

The person can be virtual but has to be here, LOCATED in the United States, and willing to travel 10% throughout the year.

About the Company
Patriot Response Group is looking for a full-time software developers passionate about creating a cutting-edge platform. Patriot Response Group is a full-service Emergency Management firm offering more than 60 years of combined leadership experience in disaster response, recovery, and construction services. Operating in the U.S. and its territories, we focus on regions with limited resources and communities devastated by hurricanes, tornados, and severe flooding.

Our values: Passion, Integrity, and Loyalty.

This is an excellent opportunity to work on a friendly team of dedicated professionals in a culture that values teamwork, continuous learning, and service.
TSMC killed 450mm wafers for fear of Intel, Samsung
and surely it's not about the robotics in use all across Amazon's warehouses. why the heck does Amazon want to be involved in "mapping your home"?
You are one of the people that seem not to understand statistics, how can you answer if FSD is safe if the only data is when FSD is baby-sited by a human with a high score?

Go to Tesla subbreddit are all hard core fans are and read about this topic, you will see many example of users having issues with this feature, the FSD is not safe, it will kill you if you don't pay attention, it might kill some innocent person because some random dude is alpha testing updates and maybe is also live streaming it for fun.

I REPEAT, Tesla is not sharing the data so if someone is telling you that the AI alone is better then a human then he is lying, there is no data to show this.

I would bet Autopilot/FSD is unsafe alone(without the human ) and the issue then raises because of marketing where someone say rents a Tesla, he believes Elon and does not pay attention and kills someone. I seen even Tesla fanbos acknowledging that FSD is not safe and just read a comment where one such fanboy had to explain his relative that FSD is a scam and not to buy it. Also there is a post ATM on Tesla reddit about someone that does not trust his relative driving his car with the autopilot because this person is failing to pay attention when using the AI, the dude was asking how could he make it impossible for this relative that shares the car with to use the AI.
...and Russia would just have sat there and accepted it? We'd be on the cusp of a much bigger and earlier war.

For that reason, the international community wouldn't have accepted it either, because it would open the door for everyone else to start developing them. Kazakhstan had nukes and voluntarily disarmed for this reason.
or use simplelogin.io
I created a new email for every month and then disable it after couple of weeks.
> That would allow my older S1 Sonos gear (which I spent thousands on) to have basically unlimited life

2 years ago, I bought some used Yamaha (not "smart") speakers and AVR. They are 8 years old now and work flawlessly. My solution to making them "smart" was to just Cast to my Android TV that's plugged into the AVR.

That entire set up cost me <$200 and has no end in sight with a very clean upgrade path. It's unfortunate that so much modern hardware is paperweight in a few years just because the company can't be bothered to maintain the software.
> Github had a repo size limit of 100GB

The source you link is 2 years old.
Except it wouldn't work with a gRPC agnostic proxy. HTTP/2 can be split up by, say, nginx and requests can be handled separately. Any custom protocol probably won't have that level of support.
Combine two emojis, and magic happen!

It's a simple and fun magic, just select two emojis and merge them with one click, and Magic Emoji will make a stunning, funny new emoji for you.

at the same time, we also offer an Magic Emoji plugin for Messages, which helps you create fun emojis and share with your friends on Messages.
Please drink a verification can to continue, caller.
One of the craziest stories I am familiar with when talking about an AK is from a 'Nam veteran who they stumbled upon a body that had been decaying in the jungle for two weeks or so, when they turned it over they found an AK underneath. They cleared the action, and the thing still worked flawlessly.

There is something to be said about that level of engineering.
I agree with you, the heated seat thing is definitely more aggravating
Sort of, but mostly yes. I inherited a code base and some team members for a video management system (security-VMS). It was a fantastic code base for the feature set it provided. However, the product strategy also changed with this inheritance, and that change in context of requirements made it less than optimal.

In no way am I faulting the original authors. They designed a system for precisely what was requested and it worked beautifully. My point is that "well done" can change meaning based on the environment. There were spots in the architecture/organization that made valid assumptions that turned out to no longer be valid and had to be re-worked to accommodate the changes. They were correct in not laying out that flexibility in the first place, but it still represented an in congruence between the problem domain and the solution.
This is why I'm not a big fan of "Things that any [insert career] should know" or "things I wish I'd known" type of articles. The path to mastering something is always unique, messy, and unstructured. It's impossible to replicate your journey by telling someone to read X, read Y, and do Z. All of that needs to be internalized as part of a slow journey that can't be accelerated too much. Your brain needs to learn how to filter noise, find patterns and get used to thinking a certain way. You might lose a year learning something that became obsolete; guess what? You still learned tons from that. We don't need to babysit junior people too much. They can find their way into becoming great SWE just like any great SWE who complains they learned something too late in their careers or that nobody told them something before did.
Hm, I never experienced this. The links I usually visit link to the github page.
In the US, backup cameras became mandatory in May 2018.

In the EU, drowsiness/distraction detection becomes mandatory this year.
There is also Filecoin: https://filecoin.io/
The article is speculative in nature, despite an obviously unreachable conclusion being the title. As a result I think it's good to be cautious in relying on it for claims, particularly wide ones
I've not gone through several inherited codebases. At first I called them awful --- however, as I've gotten older, I realize that code is harder to read than most people think. We are trained to follow a particular set of styles, linters, testing strategies, etc.

When we sit down to an inherited code base, we don't know what they were doing, so it looks terrible. There might be a very simple key that you'll never figure out until you've spent a lot of time reading the code. If you go adding code that doesn't jive with the hidden premises, there will be conflicts that you create, which you'll blame on the old code, even though it was your lack of understanding that created it.
Smart contract’s binary code is visible to anyone once it’s deployed. (And it’s pretty simple to disassemble).

For most contracts they link actual source code to make inspection even easier - large part of trust in the system comes from the fact that contracts are inspectable.
My take is that a single trait - that is, capacity for delayed gratification - is responsible for the majority of wealth accumulated and probably majority of individuals who get rich in life. It doesn't take much else really. As long as you are not severely disadvantaged (have congenital disabilities, very low IQ etc), and live in a more or less stable country (no civil wars every 20 years), and you are good at delayed gratification, you will almost inevitably make it. It's only terribly bad luck (cancer, accidents, crime) that could stop you.

Most people think this is not the case only because media is not telling about it, because there is little to tell about really. Except extreme cases like https://www.cnbc.com/2016/08/29/janitor-secretly-amassed-an-...
Solving and explaining university math problems with Deep Learning
New method exploits few shot learning and program synthesis to automatically solve university math problems and produce explanations with 10x the accuracy of previous methods.
eBay and etc all ban these. It's not a "supported" issue.
I always thought that we are getting paid this good precisely because (among other things) we have to maintain not-so-good inherited codebases.
What a great interview question!
Just because contracts can exist whose code you don't have doesn't mean you don't know how anything works: not only can you build something on Ethereum that is open source and with verifiable behavior, that is currently the norm and obfuscated contracts are not taken seriously.
> were factory workers in socialist eastern block

That's a rough start. Did they retire? What do they do now?
Un-paywalled: https://archive.ph/Wkrkg
When I started learning Clojure, I often found it helpful to look at the solutions in Clojure for coding puzzles which I already knew mostly how I’d tackle in a c-family language.

The quality varies a lot: someone as new as I was would write a 30-line function using (for), then a few answers down I’d find a 3-line answer that used (frequencies), (juxt), or some other useful standard library function that I hadn’t discovered yet.

Clojure differs from other lisps (from what I can see; haven’t spent much time with the others) with its emphasis on immutability-first, and by building a ton of functionality around the seq abstraction. Judging by the comments here, other lisps place more emphasis on meta programming. While “code is data” remains true and powerful in Clojure, I have not yet had to write a macro for myself. The homoiconicity is still quite nice.

The chunk of lisp enlightenment I have a more sound claim to after learning Clojure is the power of the REPL. The ability to access any function, at any level of a running system, feed it any data to see how it responds, then change the function and see it immediately reflected without restarting anything, results in a very tight feedback loop that you won’t realize you missed elsewhere.
But the problem you point to is not the method: it is in the regulators.