skysight-inc/HackerNews huggingface dataset:
In my opinion, it’s more about the local culture.

People in different countries/continents work differently, have different expectations around how much initiative non-managers should take, etc.

I’m not saying one is worse than the other. What I’m saying is that trying to mix these levels and hoping to exploit cheap labor to offshore doesn’t work well in my experience and what’s saved on paper is paid tenfold in customer attrition, employee turnover, high severity outages, that kind of thing.

For example, having had experience with Indian sweatshops, the people working there were paid a pitance compared to us, had to use their own equipment, no paid sick days, forced to commute several hours to work and back… imagine how interested they were in the work, being treated like subhumans by their employer. And whenever we’d talk about technical problems, they’d always say yes even if it turned out they had no clue what needed to be done or how to do it. I believe it was a factor of the tyrannical management there, but also a cultural thing. Same with asking for feedback, we had a culture (country, not corporate) where it’s common to ask for and receive honest feedback. The offshored staff could never wrap their heads around it. Or being asked to do something unclear/stupid: onshore would bring it up/challenge it/ask for clarifications, offshore would just go ahead and do… something, anything. Then we’d have to spend time redoing it and rethinking it losing weeks of work. But it was cheap, look how much were saving!!

I hope this doesn’t come as racist. I do t mean that the Indian offshores were worse people than onshore employees! What I mean is that there was a huge values gap between the two, very different ways of working, different expectations, different power dynamics and that they absolutely didn’t mesh together well at all.

We were appalled at the conditions offshore had to work under. One of the workers had cancer and couldn’t really afford the treatment because apparently health insurance isn’t really a thing in India and had to come work sick because they couldn’t afford the treatment otherwise… it was a disgrace and we tried to pressure management to face the human cost of their penny pinching.

It’s not impossible to have offshore and onshore working together and save money but I’ve never seen it done well so I’m very doubtful it can work.

And I think that’s our moat: we work differently, have different values, and different levels of initiative that local comapnies benefit from more than the marginal amount saved on exploiting offshore labor (in the context of sweatshops)
ORMs major selling point is solving the n+1 queries problem.
They can extract the tree of objects very well.
But for fast batch processing they have many drawbacks.
Nah in the US we only save businesses. The bigger they are the better.
Maybe https://open-meteo.com/en/docs/air-quality-api
not true, no idea where you got the idea that academics have such high standards, you might be referring to some long lost past that no longer exists. I have spent time in ML academia and standards are mostly a joke but things self select in the sense that often papers that are cited well and generate a buzz are those that are easily reproducible and show a significant improvement, (since researchers instantly try it and it works). But tuning baselines to look bad, creating your own benchmarks, modifying experiment conditions to make your method look good is par for the course for ML, this paper is simply far more egregious than average.

I think it’s honestly worse in other fields like cancer research where apparently >50% of the top cited papers don’t replicate. Read about the “Replication crisis”

EDIT: some more thoughts on issues. There really are 2 kinds of citations in research papers. One is the good kind of citation, that occurs when your method is so good that others use it and cite it. This unfortunately is very hard to do, even if your method is good it needs to be packaged well and researchers aren’t great SWEs. The second kind of citation is when, you get cited in related work of another paper that just states so and so method achieved so and so results on so and so benchmark. This kind of citation creates bad incentives, your goal is to be on top of some benchmark no matter what. So you start inventing benchmarks, tuning baselines to look bad etc. this citation is also easier to get so a majority of papers try to go for this instead. Maybe a solution is to just ban related works sections but who knows if that will work.
You've been lucky and haven't experienced a regular company that is not remote ready. I'm sure most tech companies are in a much better position then the ones where the only communication software is Skype. It's a serious uphill to convert such a company to a remote one.
I would entertain myself looking how someone uses a screwdriver with a nail. Novel engineering approaches are never late to study.
If you’re going to mix multiple queries with procedural logic — eg running query A vs B depending on whatever conditions based on query C, then a stored proc saves you the round trips versus doing it in your app code. That’s all he’s saying.
Cuckoo Filters with arbitrarily sized tables
I’ve noticed companies give special dispensation to their top workers to work however they like. So much for an egalitarian workplace.
This idea that everyone is going to move to SaaS / Serverless has ended.

With the growth in Kubernetes companies are much more willing to either (a) run platforms on-premise or (b) run them in their own cloud.

In both cases you can't just force them to use your choice in database.
It's the New York Times. They're like the Cramer or Krugman of newspapers.
I reject this notion based on close to 20 years of consistent observation of and participation in the web development industry. In that time I can count on one finger the number of times I've seen credible AB tests even attempted, and even then the initiative was abandoned because none of the client's staff were interested in interpreting the results of their testing. All of that is to say in nearly two decades of building websites I've never even heard of a client attempting to make results-oriented decisions based on actual data about how their website looked or performed. 100% of the drivers of obnoxious website behavior that I have personally witnessed have been overeager marketing department heads and designers refusing to come to terms with the limitations of the medium.
Yeah, that seems completely fine to me, arguably even useful
Do I need to email you with more details about my usecase? I'm seriously considering having hacker News referers use some absolutely terrible Medium clone CSS with absolutely no soul just to stop the harassment that you are facilitating via moderation inaction.
I have always thought that ORM with overrides could be the answer. At the call site objects to be extracted/inserted are defined. The implementation checks whether there is DBA written query and executes that or tries to generate something. A fancy DAO with auto-generation if you will.

If you want any sort of database maintainability you just cannot have queries concatenated from strings scattered around code, especially in environments with code hot loading. Otherwise, database migrations quickly start requiring shims for old interface. So ORMs/DAOs are absolutely necessary in any larger application just to maintain (hehe) maintainability.

At this point why not have the abstraction layer auto generate queries? DBA time is much better spent optimizing those "few" queries that do matter for performance than writing thousands of straightforward CRUD queries.

> Another selling point which is "you don't need to know SQL", is also garbage

On one hand, programmers do not need to know SQL beyond basic data extraction techniques. DBA is going to be better than them at the job anyway, even if for the reason that DBAs have access to (and to look at) performance metrics. On the other hand, auto-generator is going to be worse than a DBA too, therefore "you don't need to know SQL" is garbage. We already have to fight SQL engine, now we have ORM layer to fight on top.
> I'm confused, how is it that the prices are being driven so low that the supply dries up despite continued demand?

The incremental cost of an additional dose is low, so as long as the production line is operating all is well.

But then the line shuts down for whatever reason - and reopening it (or a new company starting one) costs way way too much. i.e. it's not worth it for them to do that at current prices. They would have to charge far more than the existing companies charge, and no one would buy the drug.

It's basically a timing issue, long term contracts mean that prices can not rapidly adjust for market disruption, combined with very very long lead time for additional production, means that the market can stay disrupted for extended periods of time. Years even.

It will eventually adjust, but it will take so long that current patients are in trouble.

The solution is a buffer, keep production in a strategic reserve.
Intel Gaudi 2 MLPerf results
But that's because of the phishing aspect. If a search for "Chase mortgages" leads me to Bank of America mortgages through an ad, there's no deception going on.
New Avocado Ripeness Testing Method 3 Times More Accurate Than Standard Method
That's what RCS is but Apple doesn't want to join. https://en.wikipedia.org/wiki/Rich_Communication_Services?wp...

iMessage is apparently a differentiator for them.
Evaluating Superhuman Models With Consistency Checks
> 20 ur old intern get bullied by his superior for driving an old car/having bad facial hair.

It seems that, for whatever reason, covid has increased the intolerance of shitty behaviour like this. Possibly because remote working meant people could choose to have less contact with toxic co-workers, and so upon return to the office it was far more obviously toxic than before covid when it may have been somewhat normalised.

This is how it should be. Penalise the fouls.
>> catch a greasy squirrel at night

Challenging at the best of times.

You get better at it after the 20th try.
Do you still have invites? I'm interested too.
Logistically, how does this work? Do employees need to install trackers on their phones to catalog hours?

Not saying it wouldn’t be ideal to have that segment of the day paid for, but I’m just trying to get my head around how the tightwad money folk deal with such a nebulous target.
I feel like this is one of those cases where the differences between open source and free software become pretty important.
The one you build yourself I guess.
If this worked under MirBSD it could resurrect some 386 and 486's.

Also, there's is a pocketchip-like computer based on a 486 sx I think.

http://www.mirbsd.org/
Source: https://twitter.com/i/spaces/1mnGeRQBwZNJX

Always remember that Business Insider was co-founded and still run by Henry Blodget, a man kicked off lying and cheating Wall Street for lying and cheating too much. Also a lesson that the news media is even less trustworthy than Wall Street.
The burden isn't on us, you're the one making the weird and incorrect claims about our society.

It has also been shown that in secular liberal societies that instituted and implemented egalitarian policies, both genders separated instead of converged, so there you go.

And I didn't lie, not sure what prompted that accusation. I'm not going to explain all the faults, fallacies, and false claims in your post on this site (all of which are trivial to address), it's not the avenue for it. Your last paragraph comes off as very defensive as well. If you're interested, feel free to reach out to me in my email, it's in my profile.
> But no-one uses different databases.

I've never worked in a place that didn't use different database. Maybe we're not talking about the same thing, but how are you developing new things if you don't have separate databases? Are you making changes directly on your production database while you're creating new things? How do you test things?

Do you keep everything in the same database, or do you have multiple and then collect data from different APIs?

Not that you need an ORM to have several or indeed different databases. I'd argue that it doesn't even make it that much easier.
So if someone went in city, dug hole in middle of road. Filled it with water. And someone came said, oh there is water this must now be wetland. And then stop everything? Would that be fine?
You should be able to do XXXV and I to get 35, I think it needs two roman numerals to multiply (that worked for me at least)
Her actions seem exactly consonant with what she was quoted as saying in the article I linked. She seems more interested in the existence of rogue human Special Access Programs than that of space aliens.

Why do you think her actions imply anything else?
I'm very happy Shopify is doing this, but at the same time I'm mildly confused by the rationale.

Is it literally just goodwill, or does Shopify stand to have other potential advantages out of this?

Either way, cool.
One problem with cooking is that your pans and heat transfer do not scale. So you cannot just arbitrarily scale up/down recipes, even if you take precise measurements. The result may be way too watery or dry, for example.

(I guess this would also apply to baking anyway.)
Nushell is also quite powerful for this. For example:

> open people.csv | where status == 'customer' | unique-by email | select surname forename email | sort-by email | save customers.json

https://www.nushell.sh/
I like stored procedures, or I guess to be more specific functions in postgres, but they have to be done in a really specific way:

1) It's all or nothing. If there's functions then they better feel like a complete high level API, enforcing the consistency of data, perfectly handling locking, etc. If there's tons of complex SQL in the app and then also a some functions then it's better to have no functions at all.

2) They need to have a consistent interface, such as always returning an error flag, error message if applicable. Functions must never surprise the caller. It either succeeds and the caller commits, or fail and the caller rolls back and knows why.

3) No monkey business with triggers. They can maintain updated_at columns, or maybe create some audit trails, but anything beyond that will make behavior surprising to callers and that is the worst.

As for version control it needs to be maintained as a separate application, which the server depends on having certain versions of. Even if you don't use functions you have to worry about schema versions and you can't always run two versions at the same time or roll back schema changes easily as a practical matter.
That's great! How did you get that?
I’ve unfortunately not found an open source model that can perform at the this level for anything beyond madlibs-style text generation. Most of my prompts are a combination of sequential tasks and one-shot prompting, typically between 1K-2K tokens and everything I’ve tried falls down at this. Granted, I haven’t gone beyond 30B models, but the gulf still seems quite wide (and even wider compared to GPT-4). Really hope it does close in the next year!
That was fascinating, thank you!
Stasis causes memory to meld together. Even an office job will become a stasis at some point.

If you really want to undercut that effect, inject new experiences into your life as often as possible.
The increase in number and specificity of building codes has come in-part due to foreign-made building materials and poor QC.

I agree, due to your uae of "in-part".

Foreign parts are indeed very low quality, comparatively. What's worse are bog box stores importing, creating their own brand, and selling this junk.

I honestly believe we should pass a law, if a big box retailer does this, they assume full liabilty and responsibility for QC and all damages. This includes if they have any ownership in any corporation, no matter how many shells or distance orml country, and the CFO, CxO should be criminally liable for compliance.

EG no hiding.

The big box guys like to import off brands by setting up a shell company, then in a few years axe the brand and close the corp, evading liabily. It needs to end!

That said, I think many building codes exist because too many people take shortcuts.
I’m all for efficiency.

How much energy is used on AC?

How much would a 10% improvement in efficiency save?
The demand for these kind of drugs is quite predictable. It would be trivial for the government (assuming it has the political will to do it) to make mid or long term contracts with suppliers to provide these drugs so that the risk of shortages is drastically reduced. I.e. many governments store enough anti-radiation drugs to supply their population in case of a major fallout event. Governments were also the main customers for the various COVID-vaccines and where the political will was available to make it work, this system worked quite well.
If we really wish to dig deeper, you only need an general purpose languages to host HTTP Server and perhaps HTTP client to connect to other external services.

Everything else including business logic can be done in RDBMS.
How it is petty theft when I did not consent to be advertised to in the first place?
Google Maps directions from home to office printed out and emailed to payroll.
Good example of content marketing
Part of the madness is domain modeling. One imagines their software’s domain model includes things like accounts and persons and try to build those as objects.

This is a lie. The domain has been modeled in the database already with constraints. The domain of the backend is not to manipulate persons or accounts but rather to do things requiring secrets, like call the database.

As such the actual meaningful structures are things like SQL clients, transactions, JSON decoders, situation specific POCOs and secrets.
moving into biologics
It's the "all other binaries" part that will catch you. You've completely overlooked that part.

For example: Per its own README, systemd requires Linux 3.15 at absolute minimum, recommends Linux 4.15 for baseline functionality to at least work, and specifies Linux 5.7 for full BPF functionality.
It’s mind boggling that with close to 20% of GDP poured into the medical industrial complex, the government can’t subsidize or straight up take over the production of some life saving drugs.
Apple first party devices have proprietary H1/H2 chips that supplement the Bluetooth stack and enable easier pairing, audio sharing, spatial positioning, etc.

https://www.soundguys.com/how-does-apple-h1-chip-work-21049/

That only works if you use two Apple devices together. You don't get those functions with other Bluetooth on a Mac, or using Airpods with an Android. It doesn't really make that big of a difference IMO but it's there.
> The way that regular bluetooth headsets work fine, but AirPods work even better

bluetooth headphones work to the best of their ability on Apple devices. Apple invented a better technology for their own headphones to improve problems inherent with bluetooth. I’m struggling to understand how improving upon a flawed technology is anti-consumer? Apple devices still support bluetooth, and Apple headphones work with non-Apple devices over bluetooth.
I don't think most did so successfully. A lot of companies did it without any sort of software or procedures to support remote working and never managed to implement it during the time. They still rely on Skype.

Tech companies are not representative.
what is rule 5 idk how
I love the Django ORM. It's concise, generates good queries and just works.

However, there's a danger - for complex applications, you want neatly separated domain objects and data layer. Django makes it really easy to make your model your domain object, and at some point that starts to hurt.

But a large part of any app is just objects backed 1-on-1 by a database table, and CRUD actions on them. It's fine.

Just watch out for those parts where the separation is needed, and separate them.
how is rule 5
Competency is a function of the human and not the tools.

People who create piles of garbage will do so regardless of what you give them.

Let's not pretend ORM made poor behavior more manageable. It was just a different style mess to clean up.

You give them TDD, they'll create bad broken tests. You give them linters, they'll put in arcane and asinine rules. You give them git and they'll have branching that looks like the Hapsburg family tree with commit comments like "fix".

You aren't going to fix behavior with tools. It takes time, discipline, probably a bunch of therapy...
I think exactly the opposite. Having all those fake calls is the harm. Not having this service is the default, so unless it provides a lot of accuracy it should not be implemented.

Worst case is real human calls start getting ignored or the response is delayed because of the noise of all these fake calls. This is a serious public safety issue, and it should not be up to a company to decide if they collapse it to sell more phones.
> But after some meditation on the matter, we’ve reasoned that ORMs do not suck. They are simply an abstraction with a quintessential pro and con—they abstract away some visibility and occasionally incur some performance hits. That’s about it.

This isn't an insight. Yes, everything is a tradeoff, but that doesn't mean all tradeoffs are equal.

The higher the ratio of abstracted away complexity to the simplicity of an interface, the better the abstraction. For ORMs, this ratio is low. They abstract away very little and present a huge interface.
- Patients can only buy cancer medication from their healthcare providers, and expect it to be covered by health insurance.

- Healthcare providers will only buy cancer medication whose prices are low enough to be covered by insurance.

- Insurance scours the market for the lowest cost providers and states it will only cover that cost, no higher.

- If the cost of drugs goes up, insurance does not immediately renegotiate prices. Healthcare providers stop buying the drugs while waiting for low cost capacity to re-appear so they don't take a loss on the care.

- Drug companies go out of business because they can't sell their inventory, driving up prices further while reducing supply.

We really ought to have a government funded drug manufacturer...
I don’t get how people jump from “it doesn’t work sometimes” to “never use it”.
You can write raw sql when the ORM fails. But for many queries the ORM does work, so why not use it?
Google could probably get into antitrust trouble if they were too aggressive about this.
Product page:
https://www.bareiss-testing.com/product/fruit-firmness-teste...
Bob Lazar Told The Truth.
It’s unlikely that you would be using different db vendors.. not different databases for different environments, that you absolutely should be doing … but pgsql in one and mssql in another is super unlikely
I was expecting a different direction: systems we had before are made of static rules, and today's ML can use reason to move beyond that. Being occasionally unreasonable may be ML's principle deficit, but its ability to reason at all guarantees its seat on the train of progress.
I agree with you that it's not realistic, but you understand the point I'm trying to make. In the end of the day you are taking a pay cut with this. With a one way 1h commute and 8h of work it's a 20% pay cut. I'm not surprised that smart people treat it accordingly.
The future of the Belgian electronic ID card (eID) on RHEL
citation please.

I did take the max recently downtown to Jury duty, it was fine. Lots of extra security that wasn't there when I rode daily years ago.
Sounds neat but wouldn't using DRM be better than fbdev nowadays? AFAIK (from having played around with DRM recently-ish and with fbdev years ago) it should be possible to abstract the "get a framebuffer" part (IIRC fbdev didn't have much of an API and all of it can be mapped to DRM).