skysight-inc/HackerNews huggingface dataset:
It would help quite a bit if you were able to give a good example.

Lots of good tactics here, but ultimately I think everything boils down to understand the problem better.

Your solution will only come from superior understanding of the problem, if there is one. It probably won't come from testing different solutions.

Almost all software starts with "what is the intput and what is the output" and then understanding how the input leads to the output. If you don't know the input and the output to your system, then you don't have understanding.

Even in your text, you have a "solution" based frame to your statement. Subordinating the problem to the solution rather than the solution to the problem puts so much focus on the solution that the problem itself gets defined in terms of the solution. I have seen feature developers play this out time and time and time again. When the problem gets redefined in terms of the solution, often the original problem remains resulting in increased complexity at little additional value.

So I would start by understanding that not being sure a problem has a solution means you don't understand the problem and its context enough to even be asking if it has a solution which means you should be asking "how do you better understand problems?" or "when do you stop investing in understanding problems?" or "what is a good time trade off between 'understanding problems' and 'directly handling business concerns'"?

When you understand the problem, you'll probably come to the realization that you were asking the wrong question altogether. There are so many times someone came to me with a problem with a system I understood that they did not and it was clear they were asking the wrong question. Frequently, I could tell them what question they were trying to ask because I knew things they didn't know they didn't know.

You may find Bloom's taxonomy interesting as a frame for thinking about how to achieve better understanding: https://en.wikipedia.org/wiki/Bloom%27s_taxonomy
Fake journalism during COVID-19 killed so much trust in democracy that it seem to be an anti-thesis to what you just said. Bad journalism apparently can kill democracy as well.
BBC articles are not deleted, even if the subject was considered "wrong" it would still be on the site -- albeit in the archive for a very small number (<15) specific articles which were found to either be defamatory or broke editorial policy on misleading content.
Arm cuts back research ambition ahead of IPO
Its amazing the kind of reach Youtube can have for science, even if its in an entertainment-context.
In my experience they aren’t just static files. They are paying for an entire platform and integrated system that takes orders and payments. That’s expensive. But probably cheaper than a fully manual process.
> The bar dropped its coded menus in summer 2021, “the moment that it was OK for us to go back to a proper menu,” he said. His main objection to them? “A menu is a window to the soul of the restaurant, and a QR code has no soul.”

Nice intro phrase.

In the past 3 years of requesting 3-D menus, they were usually available. Otherwise, a Socratic menu emerged from conversation with staff or patrons.
Develop interests outside of your work.

If the only significant thing in your life is your job, then your identity will be inextricably tied to your work. So criticism of your work will be an attack on your identity.

Become a well rounded person and your ego will naturally shift its locus.
it seems under this view, the conclusion that can be drawn for the paper is “replacing parts of a C codebase with the conceptually equivalent Rust code without any thought as to the nuances of Rust ffi may lead to bugs if the C code is already contrived” which doesn’t seem too useful a conclusion to me.
Where does the figure that the human brain is 20 pflops come from?
Your attitude actively harms people with mental illness. Well done.
Yeah a widget is something that would be nice - I don't use them heavily myself so I guess that's a big reason for why they are not there right now. I do remember Materialistic having a OK widget.
Ouch. I knew someone who claimed to have dealt with that or a similar effect after their cleaning person had pulled the plug on their servers by putting the drive in an oven while connected and heating it slowly.

Personally my most nailbiting period was when I got my first (20MB!) drive as a kid and it was too big an investment to replace even when it refused to spin up without me opening up the drive(!) and nudging the platter with my finger to help the motor spin it up... I backed everything up (on floppies), and stored everything important straight to floppies, but it was still more convenient to hold on to the HD for the next 6 months or so until I'd saved up enough to replace it...

It's remarkable what drives can survive if you're lucky... Also remarkable how quickly that luck can run out, though.

> "hey, it already doesn't work, what have you got to lose?"

This attitude has saved me more than once. Recognising when you can afford to do things that seems ridiculous helps surprisingly often.
Yeah, it looks like a Firebird now. It confuses the hell out of me
funnily enough, the USA has much less protective laws against self incrimination than e.g. Denmark. In Denmark, you, as charged, may lie on the stand however much you please.
If it does actually work, I'd hardly call that an illusion. You're right that businesses (and the end users!) are typically not interested in implementation details though.
The first recursion I put into production is a good memory for me. I wore a big smile that day.

It was a routine to discover all the ancestors of a category, to create a breadcrumb navigation for a web directory.

I believe it's still in production, although the site has been re-skinned so it's hard to say for sure.
I think there are several ways to handle that. Assuming you are using templates for the docs:

1. A simple link like this: https://docs.k3s.io/installation/configuration#:~:text=For%2....

2. An aside at the top that informs the person where to get more information with a link.

3. An example showing the structure of the file.

4. A link to examples/tests in the repo showing how it can be used.

I would think that a simple aside in your template would work wonders. Maybe saying something like:

> See our page on [directives](link) to learn how to best use this in your configuration.
All of that takes 10% of the time it takes for a waiter to arrive at your table and take an order.

It’s also way faster for on iPhones which most restaurant customers have. You just lift your phone, tap the camera icon on the Lock Screen and it scans the code right away.

Then you just double tap the power button and it’s paid and ordered.
Thank you very much! I actually made the logo with matplotlib by just plotting a bunch of sines with integer frequencies and put it together in Photoshop and feel like it's held up OK
last time I encountered this, I had my phone on me, but had no cell signal in the area and the restaurant had no public wifi. I asked my server for a physical menu and they brought me a goddamn iPad with the brightness locked to max in a dimly lit restaurant. Absolutely awful.
Maybe, but the product is called Thunderbird not Firebird
“Lego won because they never stopped building”
So, if they didn't intervene, and the caller did indeed commit suicide the next day, you're all good with that lack of intervention?
Imagine you wrote a decoder program with the key embedded in it. From looking at the program you can't work out what the key is, but you can use it to decode a secret message. You can have a secret encoder program too. Effectively blackbox obfuscation among other things allows you to turn symmetric encryption into asymmetric encryption.

Another possible use is in cloud computing. You could prepare a program with private information in it and still safely submit it to a third party to execute. This would also be very useful with smartcontracts. Since the smart contract code is public it can't contain any secrets unless it's safely obfuscated.

As I understand it we are still quite a way off from any of these techniques being feasible, since the overhead at the moment is huge.
My comment was not meant to imply that PyPI admins would be OK with this, but the sad situation in the U.S. (and Australia, and other places) is that they'd probably face jail time if they refused to comply. You can't avoid complying with a court order by saying, "sorry, I quit." (And even if "sorry, I quit" was a valid response, you'd be facing tens of thousands of dollars in legal fees to justify it, with a gag order in place that meant you couldn't raise a legal defense fund.)

If you're looking for examples of what the NSL process is like, Nicholas Merrill's story[0] comes to mind.

Further, the fact that admins have this power—even if they'd never use it—makes them an attractive target for black hats. If backdooring packages was easier to detect, it'd be a less attractive option for those that might want to do so.

I'm still hopeful that they'll re-implement some sort of end-to-end signing mechanism, sooner rather than later. I trust PyPI and the people behind it, but I'd like to be able to verify.

[0]: https://en.wikipedia.org/wiki/Nicholas_Merrill
It would not go over well if PyPI started charging people to host packages.
More than better, people doesn't know how to use GNU Info correctly.
A100s have a much worse performance per dollar than 3090s/4090s (which are the direct competitors to the 7900x)
That's also a highly effective mitigation against legitimate users, especially those already disadvantaged everywhere else by a lack of disposable income.
Sounds exactly like a software engineering hiring committee :)
> (Ankle monitor?)

I'm aware of a guy who was in house arrest for a while. Apparently ankle monitors false alarm so very, very, very frequently. And every time they do, the officer (whether of the court of of the law) who's in charge of monitoring you needs to get involved to ascertain that yes, you are still at your house, and yes, it is the shitass lowest-bidder carcerial-system trash that's faulting _again_ and wasting everyone's time and energy, and no, you are not getting cute or clever and wasting everyone's time by running away, or tampering with your shitass anklet.

Long story short, some entity who actually gave a shit (and also wasn't gunning for you to replace it with a new model every three years) would need to build any such device.
You can’t. I imagine when you get a replacement or additional device you manually reconfirm your email and get issued another keypair, so all subsequent logins to that website just use your face or finger or whatever.
I think this is a very good answer and trying a similar approach and similar methods has helped me a lot in my life. Few years ago I was very easy to get angry over work and code (especially other peoples code!) and I could stay in this state for several hours. I would also often be not very nice when responding to PR comments.

Also wanted to specifically comment on

> When you feel bad, stop to think. Observe your own reaction and calmly try to realise why you’re feeling that way and what’s your goal. The introspection alone can make you see [...]

That sounds very close to mindfulness meditation - or any kind of meditation really. In my opinion that is also a great way yo get better understanding of oneself and it can help improve quality of life overall a lot.
Your work is not you. Of course your decisions shape the way your work comes out, and of course you used a considerable amount of time to create the work, so as a result you are involved with it.

But the key understand is if someone criticises your work, they don't usually target you — why would you even think they know who you are?

When they criticise your work they take time to tell you why they feel or think your work could be better. Instead of taking that at face value ("shit I am bad at making good decisions") a good strategy is to take the causal root of the critic seriously, while taking the suggestions they make with a grain of salt. The former comes from a true place most of the time, the latter can stand and fall with the subjective interests and knowledge of the critic.

So think about that causal root ("user had problems to understand X") and see it as a cause to think about the state of that project.

See how it is not about you at all? It is about the project. Of course your decisions shaped that project, but isn't it possible that there are parts within that project where your decisions could have been better? Sometimes we all take decisions automatically without giving it a second thought, so a critic can be a way to provide another perspective, one that we might not have considered before — that is a value in itself.
> This is just irrational. The client is open source. You can build it and run it from source.

Something I don’t understand is if the client is open source, why is it not in the fedora repos? Why do I need to add a new repo to dnf?
Keyval (YC W23) Is Hiring Founding Back End Engineer
Ironically I've seen people take a snap of the paper menu so that they can zoom in on their handheld screens. Which works much better than zooming in on a mobile website or in an app, so another point for the paper menu.

(not as often as seeing people snap the paper menu so that they can get it through their translation service of choice or share a copy without banging their heads together, apparently paper menus only get better through technology)
I think I'm usually decent taking feedback but recently I realised I get really annoyed when someone I don't respect gives me feedback. Doubly so if the feedback is bad or nitpicky. It must be ego, plus my belief that one ought to do minimum due dilligence before giving feedback.

I try not to express this annoyance, so other people haven’t picked it up (though I'm sure it shows sometimes). It's something I'm trying to work on as suppressing that annoyance cannot be healthy for me.
The race between Delta Lake and Apache Iceberg is a throwback to VHS/Betamax days.

Microsoft is betting on the former while for example Snowflake is now allowing you to back tables with the latter, making it possible to integrate your data directly with other systems.

I talked to a Microsoft rep who said that they would support Iceberg if there was a Rust-based client for it.
And its discussion from 3 years ago:

https://news.ycombinator.com/item?id=25046738
TBH I think in both your examples the problem is the word "stupid" and not the structure of the sentence. Also just deciding whether some statement is a personal attack on the usage of you vs it seems a bit shallow. I would wager that most people writing these comments don't even think much about the difference.

As others have written: always assume best intentions first and try to read the comments in the most favorable way.
One of my favorite man pages is openbsd's scan_ffs. mainly because it contains this pearl of wisdom

The basic operation of this program is as follows:

1. Panic. You usually do so anyways, so you might as well get it over with. Just don't do anything stupid. Panic away from your machine. Then relax, and see if the steps below won't help you out.

http://man.openbsd.org/scan_ffs
Glad that you like it! It is a BottomSheet (https://m2.material.io/components/sheets-bottom) which is a Material design component from Google and they handle a lot of the complexity (although the implementation in the app has a few bugs) which is nice
The precise mathematical definition of obfuscation and what is considered obfuscation for an average software engineer are two very different things.

In fact, the article is only about indistinguishability obfuscation. What is mostly discussed in this thread is the notion of virtual black box obfuscation (VBB).
VBB has been proven to be impossible in the general case (see https://www.wisdom.weizmann.ac.il/~oded/PS/obf4.pdf). There are a few special programs where VBB is feasible, such as point functions, but in general in cannot be achieved.

Indistinguishability obfuscation (iO) means that if you obfuscate two programs that compute the same function, then you cannot distinguish them. Or put in different words, if you get two obfuscated programs, then there is no better way than random guessing (except for a factor that is negligible in some security parameter) to find out if they stem from the same original program.
Not being female helps a lot in this regard. I have no other tip for you.
Windows Terminal can autodetect Powershell and WSL. Other shells can be manually added or removed. [1] I presume some config editing would be needed as and when you move Terminal (Portable) to a new system.

[1] https://learn.microsoft.com/en-us/windows/terminal/dynamic-p...
I think they're trying to "scale" out order-taking to sell more. But interestingly it seems like they screw up the order more than if they took it from you in person.
geohot wrote tinygrad. This is not about believing his skills to translate to other domains. It is his domain.

You definitely shouldn't trust what geohot says about infinitary mathematics or (god forbids) quantum mechanics. On the other hand, you generally should trust what he says about machine learning software stack.
"If she doesn't like it, she should learn to type."
>f you do have to reply, don’t do so immediately. Let it marinate and respond when your initial feeling has subsided. That allows you to get some emotional distance between yourself and your work, thus seeing (and fixing) the problem in the thing not yourself. Waiting has the secondary effect that another person may reply in the interim, shifting the burden away.

>When you feel bad, stop to think. Observe your own reaction and calmly try to realise why you’re feeling that way and what’s your goal. The introspection alone can make you see that the situation is unimportant and thus taking it personally is disproportionate.

I think those two are the core of the good advice. I'm also quite bad at not getting emotional by criticism and this is what I usually do too.

I would add that it's better to throw away the idea that "after some training, eventually you won't react badly to criticism" is something you'll achieve. Some people (like me) didn't really stop reacting badly to criticism, but just found a system/coping mechanism to channel that emotional reaction in a healthy way.

Another practical advice is to write down the criticism you got when you got it. Even if you got the criticism over text, the practice of writing (summarizing) the criticism received when you're under your emotional reaction will slow down your thought-process (you write slower than you think) and you'll also have material (something you wrote) later when you're more calm. Re-reading the criticism later from the person that gave it to you, might stir the negative emotions again and start a vicious cycle, so something written by you is a good intermediate to stop that, and detach the message from the person.
> HTML and other web formats are only readable by the virtue of being constantly evolved while keeping the backwards compatibility, which is nowhere near complete and is hardware-dependent (e.g. aspect ratios, colors, pixel densities).

HTML itself is relatively safe, by virtue of it being based on SGML. Though it's not ideal either because those who think it's their job to evolve HTML don't bother to maintain SGML DTDs or use other long established formal methods to keep HTML readable, but believe a hard-coded and (hence necessarily) erroneous and incomplete parsing description the size of a phone book is the right tool for the job.

Let me quote the late Yuri Rubinski's foreword to The SGML Handbook outlining the purpose of markup languages (from 1990):

> The next five years will see a revolution in computing. Users will no longer have to work at every computer task as if they had no need to share data with all their other computer tasks, they will not need to act as if the computer is simply a replacement for paper, nor will they have to appease computers or software programs that seem to be at war with one another.

However, exactly because evolving markup vocabularies requires organizing consensus, a task which W3C et al seemingly weren't up to (busy with XML, XHTML, WS-Star, and RDF-Star instead for over a decade), CSS and JS was invented and extended for the absurd purpose of basically redefining what's in the markup which itself didn't need to change, with absolute disastrous results for long-term readability or even readability on browsers other than from the browser cartel today.
From the newsletter: "There was no existing panel that satisfied all of these needs, so we instead developed a semi-custom LCD display module with BOE, the same panel maker we use for the Framework Laptop 13. The “semi” part is that we customized the backlight for higher brightness and liquid crystal chemistry for better contrast and color gamut while leveraging an existing TFT mask set to avoid needing to pay a few million dollars in tooling fees."
Looks like they had to make some compromise.
P.S.: I personally like what they did and especially the resolution of 2k, for me the best compromise between work, video and gaming. I will for sure get one (when they support enough memory for my needs).
The website does not communicate solid, trustworthy service. Also calling yourself sonic bank when you are not a bank seems edgy.
It’s not exactly that either but it’s close to sealioning.

https://en.m.wikipedia.org/wiki/Sealioning
It sucks that when you scan these you can't choose to open the website.

Apps are an attack on the open web and I don't want them being able to do things like access location or other app-related things.
Two key points that helped my team through a rough patch were:

- one of my co-workers setup CI automated formatting/style checks (i.e. PEP8, mypy, isort, etc.)

- much more extensive guides on how to contribute good code with many generalized examples as well as do's/don'ts. When new nitpick comments come out in the PRs - the guides were updated to avoid future nitpick PR comments

After some initial pain - we really haven't had issues with PRs anymore whereas before it was pretty painful. That said we've been working together for quite a while now.

I think a lot of times the original author may have something in mind w.r.t. the codebase/architecture/formatting/schools of thought and expect the others will pick up those ideas naturally and they get frustrated when other team members don't.

The other team members being code commented to oblivion get frustrated with what seems obscure, snarky nitpicks.

By making stuff explicit upfront - people can self help/self correct/self edit before the PR is even generated.
Think about it step by step. There are people not able to count. We still say they can reason. A low ability to count does not disprove reasoning.