skysight-inc/HackerNews huggingface dataset:
It sounds like you are quite ignorant of how research happens - the situation is precisely the opposite of what you describe. The research money comes almost exclusively from external grants, and the universities take a large chunk, often > 50%, off the top.

The research subsidizes the university, not the other way around as you somehow think. Most professors would love to spend more time on undergrad education, but that's not what keeps the lights on - research grants do.
to your point, super interesting :

https://en.wikipedia.org/wiki/Bjarni_Herj%C3%B3lfsson
Are you old enough to remember "Star Trek: The Motion Picture"? Voyager is a major character. In 1979... way before the internet.
It would also be nice to extend IMAP to support UnifiedPush...

The use-case would be new mail notifications; it wouldn't be too hard to do, and would be quite useful, as I typically have multiple e-mail accounts.

You could however build a UnifiedPush-compliant SMTP-based or IMAP-based distributor.
We certainly do at my company. Most microservices are rather small and easy to spin up on smaller AWS instances, especially if they're Docker based. Our AWS bill isn't that high and our preview environments don't contribute much to our costs at all. We do have a process that nags developers if their environment has been up for a while and make them confirm they still need it.
It's not just lab work, I TA'd for physics and students would come to TA discussion sessions to get a more detailed lesson on the material covered that week since often the professor is just repeating the contents of a textbook. Also, many TAs would spend many additional hours in tutoring and office hours, giving individualized attention to students, and this workload adds up.

TAs also grade quizzes, final exams, create questions for problems, etc... The professor often does very little work and leaves it to the TA, at least in my experience as a TA for physics courses. It's a lot more than just maintaining a lab.
And universities need buildings.
I think the aws cli is a decent example. It isn’t perfect by any means but it demonstrates how to handle config files, environment variables, and command line arguments in a usable way: https://docs.aws.amazon.com/cli/latest/userguide/cli-configu...
makes you wonder if it's really that valuable to have all our infrastructure built on parsing text
I look at math the same way as at physics, where rigorous proofs are not possible. The difference only matters to the few people who do it professionally.

I know I can dig deeper all the way down to axioms if I choose so, but realistically there is not enough time for me to learn all of the underlying math. At most, I can occasionally check if the results are consistent and match reality.
We've been quite happy with Auth0 to solve this problem.
The rise of preview environments? They've been popular for years. We were using them casually 10 years ago and didn't feel like it was on the bleeding edge. Kind of a weird marketing post.
>Don’t listen to me, I am supposed to be accompanying you!

As a conductor and director in my experience this is the hardest one for many musicians to learn, and it even goes a bit against the “keep the time is #1“ rule.

As accompaniment, harmony, etc you need to understand who the lead is at any given moment and follow it. If you just keep the time robotically and don’t pay any attention you will destroy any possible magic. If you are homophonic harmony but you are out of time with the lead, it won’t be tight and may be bad (unless a loosely hinged style is what you want). The lead may be taking micro beats of time here and there with the line and you’ll want to follow this.

Even this has nuance though. Sometimes the lead might be taking time (or rushing time) and actually expect you to be keeping time, to stay in the pocket, to give him a landing zone to anchor back to once he’s decided he wants to come back in time on a cadence or a downbeat or something. And you need to know that too, as the lead goes in and out of the pocket what is his intention there?

In this way it’s beautiful how the really best music doesn’t require only experienced musicians, or even musicians experienced with each other (understand each others styles, tastes and intentions) but also requires a level of trust between them to be able to leverage those experiences in a special way. And that could be generalized to other areas of work and life
As far as I know, the standalones seem to work better with SDK and tool detection (I guess IntelliJ has to try to figure out which plugins to activate)

Some projects with mixed languages (like a Ruby backend, HTML/JS webapp) I've had to kick IntelliJ a bit to get it to cooperate and find tests correctly

Someone else mentioned CLion, I think Rider also has features you can't get via plugin (maybe there is no .NET plugin..?)
Many options exist, but in case you are building in python, this is an awesome library. Charm in goland is what I can think of that come as close to it, and in elisp of course you would do that with emacs. While emacs is awesome, not everything that can be done in emacs would be an optimal solutions for all use case. Always use the tool for the job.
Depends on the DBMS, but pt-config-diff works well for MySQL.

edit: This will only help for configuration, not procedures.

https://docs.percona.com/percona-toolkit/pt-config-diff.html
> Administration doesn't consist of the people at that lower level.

This isn't the way "administration" is calculated. Statistics showing "administrative bloat" point to growth in spending on "staff"/"non-teaching employees"/etc. The job I describe above would have fit this definition of bloat.
I'm gonna be the contrarian and say this is mostly fine. We can research the proper way to do things, or use code review to teach about the proper ways. But this can lead to code shaming and a fearful environment where people second guess themselves and spend a lot of time chasing a perfection that doesn't move the business metrics.

In this case, doing the join manually isn't a huge deal, chunking isn't a huge deal, parallel requests isn't a huge deal. But "concurrent limit reached" is the point in this story where Bob should have put on the thinking cap and reasoned that "this shouldn't be hard, other people do things like this with bigger datasets all the time, I wonder how". Before that point it's literally just a matter of changing a couple lines to solve the issue. So what? After that point however, it's starting to affect the overall design around it in harmful ways, and turning the issue into a bigger one.
That's what I meant by "soft money." By administration, I am talking about more stereotypical bureaucracy, such as the ever-expanding number of various kinds of deans. I worked with soft-money people, who were called "research professors" in my department. They worked hard and brought in much more money for the university than they cost.
Interesting read. Quite depressing though in the context of countries where there used to be a healthy youth dance culture for decades in big clubs, which now appears to be dead.

Dancing and respect for dance etiquette seems to now be sidelined to niche events and nostalgic people reliving their youth.

While popular "dance" events still exist, standing in a packed crowd holding your phone up to film the DJ is not dancing.
There are all sorts of subtle ways you need to "break the law" while driving though. Right now, one sees tons of delivery vehicles pulled over to make deliveries and you have to carefully go over the double yellow line in the middle to get around.
Hotels are certainly charging the guests for cleaning up; it is just not broken out as a separate charge. Of course, Airbnb’s do not have the economies of scale that a hotel has and in some cases for short term rentals charge more for the cleaning than the rented space. I stay with the pros and avoid Airbnb’s for both cost and convenience reasons.
Yeah, I wish this was more standard. SQL is not so much a standard as a skeleton of a standard. Better than nothing, maybe, but still every database I walk up I pretty quickly hit issues like this.

I'm not trying to promise that every database will stream a petabyte without a problem; I'm more trying to help people get out of an early 2000s mindset and if nothing else, check what their DB will do. A lot of old programmer's tales about how to baby old databases along are actively pessimal and unnecessary in 2022/almost 2023. Don't spend days writing code to correctly slice and dice a query into tiny pieces when you could just send it in one shot and get better performance in every way.
Yes, sure. But let's not understate how unusually bad the disaster really was; a 9.0 earthquake and equally severe tsunami. That's not exactly a common event, and it probably won't be one even in a world with much more volatile weather conditions.

And yet, despite that, it is in fact possible to make nuclear fission power plants survive this kind of disaster, and especially possible to prevent the meltdown that eventually occurred; Fukushima Daiichi is not the only fission plant in Japan, and not the closest to the epicenter of the disaster either. I think it's fair to say given the evidence that the problems that need to be solved with regards to Fukushima Daiichi are the systemic issues that led to the inadequate safety measures and the unfortunate decisions made leading up to the meltdown. Whether the issues be operational complacency, corruption, etc.

It'd be nice to have a way to simply be robust to those issues, but in the end it's always going to be dangerous to human life if the people in charge of decisions that could endanger human life are not adequately responsible. That would still be the case in absence of nuclear power, natural disasters, evacuations, etc.
If you have a tornado coming straight at your house with your family inside you will be praying I guarantee you.

If you lived in a sparse, lonely place, with a bad economy, maybe joining a church starts sounding like a good idea.

Instead of judging people consider yourself lucky.
In my opinion, the fact that procfs is the only API for so many things is one of the biggest problems with Linux. BSDs have sysctl(), macOS has mach_* functions and, of course, Windows has a real API too.

Plain text interfaces lead to complicated, potentially insecure code (especially in C!), they're prone to race conditions and slow.

I wish it was possible to retrieve that information using real syscalls. I think it's a better approach than, for example, inventing a faster way to read procfs: https://lwn.net/Articles/813827/
A solution I've been using and really enjoy is Hellō [0]. Basically I can integrate Hellō as the OIDC provider on my site (doing it on WordPress and Discourse for now but it can work for other sites) and then people login to their Hellō wallet and then that logs into my site.

Hellō manages the social logins so I don't have to worry about adding a bunch of them (and update when new ones come out).

It's also run as a cooperative, so I appreciate the business model behind it.

[0]: https://www.hello.coop
Eight-car Thanksgiving pileup blamed on Tesla “Full Self-Driving” software
> rapidly declining human fellowship, companionship and participation

What is the evidence for this?

This just reads like the eternal conservative lament that society is going down the tubes.
Meanwhile I'm writing a compiler for the 6502....
Also IIRC you can design the reactors to support a degree of output scaling, if not shutdown. IIRC French reactors are designed to do that - they have some issues right now with premature fatigue but I'm not sure it is related.
I think this makes sense with what I'm saying.

Laborers get more of the profits of companies and in turn get wealthier. However, the costs of services in turn go up (due to rising cost of labor), so those laborers (society) cannot actually afford more services (provided by people). Workers can more easily purchase goods which benefit from increasing automation and technology.

So, these workers which are capturing more of the profit can afford to buy fancier kitchen appliances and cook themselves better meals. But, can they all then afford to go out to eat more -- when going out to eat is primarily an endeavor dependent on the labor of others (and thus it becomes more expensive)?
Sounds like you pay a lot of money for a very specific, niche type of politics and social justice, because I guarantee it is present at a Catholic school!

"Can we talk about birth control and the effect on women's opportunities?"

"No."
I worked at a company that had built a tool for basically this. You can deploy your service changes into prod, get a special cookie and url that you could share with other users, and see prod with your changes. It was super helpful, but it did bias toward manual QA in a conference room rather than FE automated testing.
These details seem to make the idea unworkable to me.
Congrats! It's always surprised me that Amazon or one of the other Android vendors didn't do this themselves to make porting to FireOS or other services-included Android distributions easier, but I hope you get funding from them for doing their job for them.
that sounds like a really good idea, you shouldnt have to sign in more than once in a session, if you do have to, something is amiss!

ubiquitous sign-in demands create what amounts to a smokescreen for eviltwin popups, allowing hats to phish for google sign-in creds...at scale
It's the m68k target -- to a first degree approximation, no one uses this.
I didn't see it as a joke. Happy to be wrong though.
Here's a state employee working on the taxpayer's dime who didn't want to work too hard because doing so would further white supremacy: https://reason.com/2022/07/02/urgency-is-a-white-supremacy-v...

That's one example, but step into any nonprofit's office these days and you'll find plenty.
It may surprise technical users but a _lot_ of people who have used Macs and iPhones for more than a decade don't know what an application is, much less what that application might be called. They just click an icon and things appear - when they don't, or the icon is not where they expect it, they are totally stuck.

On the one hand, Apple deserves credit for creating an experience where the tool seems to get out of the way.

On the other, it's depressing that so many users are steered away from understanding things that could increase their facility with these devices they rely on so much.
But wouldn’t Google with super powers produce correct answers to basic questions, though? I mean, really. It’s clear very helpful at surface things for which there is a large corpus of examples, to some extent. I don’t really know if it’s “good” or if it is just surprising.
This is partially explained in the blog post.

I'm personally using UnifiedPush HTTP endpoints as-if they were Web Push, and it just works. I handle decryption manually on the receiving end.
End-to-end testing for Stripe integration
> In the example the author gives the query cost is very likely dominated by finding matching rows in A. Where there is no index, then we can expect a full scan of A (or the index of A.id) for every batch of B.

Why would you expect that there's no index? I have never seen a single database system where the most basic primary key A.id wasn't indexed. Instead, I would expect that you're correct below that cost of the query is dominated by fetching the rows from disk and serializing them—this is a linear cost that increases with the number of rows returned, so fetching 50,000 rows should be about 50x as slow as fetching 1,000 rows (especially as long as you're fetching them in some sort of block-cache-amenable order, such as in increasing ID order, so that you're seeking to sequential places on the disk most of the time instead of fetching just random blocks)

> In addition, and probably more to the point, the round trip database costs (serialisation, parsing, planning, scheduling, network comms) are going to dominate the actual query costs for something like this (unless A is exceptionally large).

Aside from a small overhead, serialization, parsing and network comms will all increasing linearly with the amount of data returned. 50,000 rows of data will be about 50x the serialization and network cost of 1,000 rows.

> Furthermore, the memory cost to the DB of the serialisation and parsing is likely to be much larger than just storing all those ids in their native format - and there would be no client memory footprint in a join. For the final result set the client can reduce their memory footprint by using a streaming result which every BigData DB supports, and most others too

Sure, I can absolutely agree that using a streaming result set would be the best of all possible worlds here. However, it does require you to keep a client connection open for 50x longer than batching would, which on many databases (e.g. Postgres), would lead to more memory usage and CPU contention then batching the result in a background job queueing system. This comes down to what % of your total pipeline is spent in the database in question compared to data processing or other databases—if only 20% of your job's runtime is fetching the rows from this database, then it's a bad idea to monopolize that DB memory for the much larger amount of time it takes you to process the entire result set, when instead you could be yielding that memory back to the system for other transactions to use. But if 80%+ of your time is spent in the database, then the small amount of time that other transactions would be able to reclaim wouldn't be worth the amount of fixed overhead from re-planning, re-executing, re-fetching the index from cache, etc. And obviously these—as you may have been able to guess, my experience here is rooted in OLTP workloads using Postgres, and I'm sure there are plenty of differences with BigQuery's architecture.
Already happening in the humanities. Many major programs in my field when I was applying (as an international student, so there already were some "quotas" in place on how many international students a program would take) were signaling that they were reducing the recruitment number simply because they could no longer insure TT placement afterwards. It's too little too late tbh, but at least they are starting to do it. I know they are starting to do it in non-humanities programs as well.

I'll add as well: the standards expected for present day PhD students is insane compared to PhD students a generation ago. When I speak to some of the tenured professors I know, they readily admit that they would not meet the standards for TT positions today. Add to that the insane number of applicants, and the tendency for hiring committees to default to applicants from top-tier programs for hiring (regardless of the quality of their research), and you end up with an increasingly bubbled and desperate profession that is extremely unwilling to break from party line and disrupt whatever sliver of a living they ended up in.
Minisaga
> Some still insist on old-school germanium diodes and transistors for things like clones of the classic guitar effects pedals. Those are also ~0.3 V, but their proponents argue that the shape of the "knee" and other parameters are different to silicon

This is true. The important feature of germanium diodes, wrt this application, isn't their lower forward voltage as Schottky diodes are even better at that , but rather their characteristic V/I curve which is softer than silicon (0) and produces less odd harmonics which would otherwise contribute to a harsher sound.

Regarding germanium transistors, they're mostly used to replicate old school fuzz guitar pedals. In that application, aside the above characteristic, the particular configuration in which they're employed contributes to the sound: old fuzz pedal produce a very pleasant asymmetric distortion in which one half wave is much less distorted than the other, so that the output can contain a blend of clean and distorted sound.
R.G. Keen at Geofex (.com) wrote a thoroughly informative article about how that circuit works which anyone interested in building guitar pedals will find very informative (1).

(0) https://commons.wikimedia.org/wiki/File:V-a_characteristic_d...

(1) http://www.geofex.com/article_folders/fuzzface/fffram.htm
"Not exporting and consuming gas domestically at lower prices incurs an opportunity cost as the same gas could have been sold for more aboard. So net-net the people will pay for such a policy choice."

I don't think it's so simple. Cheap energy can make entire industrial sectors viable that otherwise wouldn't be. You could easily end up ahead by putting that energy into production of goods that are higher up on the value chain rather than exporting it directly.
I think there's a very limited edition available for free.
This technique doesn't seem especially relevant for many kinds of backend work.
Even the enforcement of rules and the expectation on that are location dependent. Someone I know walked on a crosswalk in a southern european country, expecting that this will be honored like it is here. Ended up in hospital for two weeks. No driver there expected it.
The older 9x and 89s do, yeah. The new ones just run ARM and emulate the older chips.
> It looks like the submission side of UnifiedPush could indeed have been Web Push-compatible but isn’t, though.

Exactly. It was discussed a bit early on whether to mandate encryption, but simplicity was chosen instead.

Adjusting the server protocol to make it compatible with WebPush is also being discussed: https://github.com/UnifiedPush/wishlist/issues/15

That would be useful for supporting Telegram, for instance. I don't really see it becoming mandatory, however.
No one making $9/hr with a kid or two is going to be dishing out for a Costco membership and getting a volunteer to drive them around everywhere they need to go. There is no long-term savings and “financial sense”, it’s hand-to-mouth, sometimes shoplifting to survive. Have you executed this plan yourself? If not, I’d suggest appreciating the fact that it isn’t this easy or many people in poverty would have done it.
Totally agreed. Any time I’ve found myself parsing proc, I’ve felt like I was doing something foolish and unsafe in lieu of a “real” api.
> Are we going to give ta’s $2/hour and expect their students to tip them?

That would be interesting, because TAs do the grading. ;-)
A few steps

1. Meet people smarter than you, could be through meetups or discord etc. The more people you meet, the higher chance of someone you'd meet someone you'd want as a mentor

2. Being active as a mentee. Most people love mentoring but it's a two way street. If you don't make yourself available to be mentored you waste everyone's time

3. Show initiative as a mentee. Ask good questions and problems your solving related to your mentors expertise

Having had a lot of great amazing mentors in my life, and mentored just as many.

In my experience if you don't put yourself out there to be mentored you won't get anywhere. Most of my mentors have been through city slack channels, work, and meetup. Alot of my original mentors actually ask me advice having seen my career progression over time

I've had people ask me to mentor them but they expected me to magically transfer all my knowledge to them, suffice to say I didn't waste any time with them . When I found an amazing mentee I went out of my way to help them, and I got to see their progress and growth overtime. That was super rewarding
It's kinda funny that we'll try to invent advanced ai that can perform a near miracle of technological advancement before investing in proper public transit.