skysight-inc/HackerNews huggingface dataset:
Thanks for this! I am looking forward to putting this together with the Zola CMS for some hobby applications.
Douglas Adams writings would give me doubt about this.
i use a metal detector. some of these trees can be a stash[cashe] and you may encounter things hidden long ago, most of them not good for your chain, some of them not good for you.
Let's talk about human colloboration
The Power of Collaboration: Why Humans Thrive in Teams

Humans are inherently social beings, and collaboration is one of our greatest strengths. This is especially evident in team activities like sports (there are many activities), where working together towards a shared goal often feels more exhilarating and rewarding than solo pursuits. But why is this the case?
The best way to learn a language is to build a project with it. Anything else is just exploring its feature. The trickier issues are always features integrations.
Hard to think anyone who can't solve a captcha is something other than a parasite.

Parasites can solve captchas, people with accessibility issues and the poorest of people are the one being locked out.
I'm based in the UK where we all have credit cards. I also did give them my ID - which is NOT typical for other hosting providers, actually, but I'm happy to provide it - but that still didn't satisfy them.
If you press it, "They will come!"
Techno-optimism assumptions in the wild:

Most interfaces in our world contain a blend of digital screens and analog inputs like switches and dials.
Honeycrisp apples went from marvel to mediocre
Absolutely. So if you made a body map and your user base starts asking for you to add chakras or reflexology areas or acupuncture locations and you think that's all a bunch of woo, how do you respond?
Yes, people often do unsavory things for money. Is the point you're making that they shouldn't do bad things. Like, what are we even talking about here?

The lesson here is that systems that rely on humans to do the 'moral' thing and fail otherwise are bad systems.
You can use GMail with any client with IMap. Youtube has several frontends. Libreoffice it's far more featureful than Docs and Spreadsheets. Google Maps? Organic Maps works offline and you can always use OSM maps with just GPS support to orient yourself in a disaster.

These people will get burned and want their computers and media back.
You could also imagine a linked list of header chunks. If the header is not large enough you could then add another chunk and make the previous chunk point to it.
Yes I learned that too a while ago. If you say anything slightly positive about Tesla, you'll be downvoted into oblivion. I can't wait for the day for this US/Western tribalism to cool down and we can have substantive discussions again.
I think “make it work, make it right, make it fast” is a solid approach.

It appears the startup in question just never even did step one. A financial system that is imprecise does not work.

Additionally that mantra is typically applied at the story/issue level in my experience as in:

1. Get the tests passing
2. Get the code clean
3. Identify scaling bottlenecks and remedy if necessary.
For some reason, I imagine most diamonds just store the same word over and over:

HOT HOT HOT HOT HOT HOT....
I am toying with spreadsheet backends these days and it's had me wondering - do spreadsheet query languages offer value that SQL is missing? Beyond "people are used to it" of course.

One thing i am wanting beyond SQL though is a more Object oriented language. Ie i want something SQL-like (or more specifically PRQL, which i find very nice), but without the being so tailored towards a flat data structure. I want to use it on JSON/etc.
I was supposed to do knowledge transfer at one job but I burned out and quit before it got done because my job was knowledge transfer, training new hires in C++ itself, putting out fires, fixing bugs, and shipping new features that had already been promised to customers I'd never heard of.

In terms of "Ars Longa, Vita Brevis" [1], I'm not as good of an indexer / teacher as I wish I was.

https://www.slatestarcodexabridged.com/Ars-Longa-Vita-Brevis
> I was looking at cats as an example of a species that sleeps in smaller chunks and splits activity all around night and day

Cats are crepuscular. The niche hypothesis predicts they'd sleep most of the day and night.

> not to a degree they can't move out from their niche

No animal I know of can't survive outside its time niche.
Say more. Are you wanting “Node-RED but for Python”? Or the non-UI parts that are accessible programmatically?

I’ve had similar interests and realized I essentially needed two things:

1. Something like “FastAPI without the HTTP parts”. Basically a request/response cycle with middleware functionality, where we run a registered Python callable in response to a JSON request, but where that JSON request can be from any source, like “pulled from a queue” or read from the command line, instead of “pushed from a web browser”. For that I essentially pieced together a basic task registration decorator class with pydantic’s `validate_call` decorator and let pydantic handle the serialization/deserialization. There are libraries like FastAPI, typer, Celery and others that do this, but they’re all tightly coupled with specific transports. I want to be able to delegate to a developer “build a function that takes this JSON and performs this task and returns JSON”, but not with HTTP (FastAPI), and I don’t want to be required to add Redis to run some small task (Celery), and I do want the task to be callable by CLI (typer), but not only CLI. It seems like there are all of these tools but none of them are loosely coupled enough to do this in a straightforward way.

2. Some way to run a directed acyclic graph (DAG) of those registered tasks. There are lots of tools that do this in varying degrees of heaviness (Airflow, Luigi, Dagster, etc), but for a lightweight solution this is built into Python with graphlib’s TopologicalSorter. But the point here would be, whichever one of these you pick, it helps to have #1 available in a way that allows for generic “running approved Python functions from JSON”.

So I sort of have those parts of it roughed out, but now I’d also like a better UI for it, for instance to allow for a more high level dashboard red/yellow/green status of things, or to enable a less technical user to adjust the schedule of a registered task, and so on. Django’s admin portal is a first step her but ultimately we’d need something more interactive to make it a team effort where more employees can contribute without needing to know Python.
Estimates of GPU/compute resources of large AI players
https://archive.today/rMdsQ
I gave a trick question. It went on right path and then gone bonkers!

how many r's are there in the word strawrrberrry

Thought for 173 seconds

1
problem understanding

The task is to count the number of 'R's in the word 'strawrrberrry'. This requires careful examination of each letter in the given word.

2
data gathering

Let's break down the word into individual letters: s, t, r, a, w, r, r, b, e, r, r, r, y

3
analysis

We need to count the occurrences of the letter 'R' in this sequence. Let's go through each letter and keep a count.

4
calculation

Counting 'R's: 1. First 'R' (t=1), 2. Second 'R' (t=2), 3. Third 'R' (t=3), 4. Fourth 'R' (t=4), 5. Fifth 'R' (t=5). Total count: 5

5
verification

Let's double-check our count by going through the word again: strawrrberrry. Confirmed, there are indeed 5 'R's.

6
error checking

Ensuring we haven't missed any 'R's or counted any extra. The count remains at 5, which appears to be correct.

7
conclusion drawing

Based on our careful count and verification, we can confidently state that there are 5 'R's in the word 'strawrrberrry'.

8
implementation

The final response should be a simple statement: 'There are 5 R's in the word strawrrberrry.'

There are 5 R's in the word strawrrberrry.
Civil contract disputes don't empower or obligate you to commit crimes in the process of trying to make things right.

The power inverters were *not their property*. Remotely accessing them, without authorization and with the intent of disabling them, is a textbook CFAA felony.
You're welcome, I'm sorry for what you're going through. You probably will eventually need to find a specialist who works with patients with dysautonomia or Long Covid but there's plenty of stuff you can do on your own or with a friendly PCP (or maybe more realistically, with a PCP who you can persuade to order the appropriate testing).

This does all sound like POTS and orthostatic hypotension though, maybe with other issues mixed in, but that's a good place to start.

Hopefully my other comment in this thread is helpful!
Thank you very much for the tip. I will try it out for a month, and let you know how it works.
Is there something more than prediction going on? I'd like to understand why there would be studies like this: https://arxiv.org/pdf/2307.02477 if it's all just prediction. Are there some algorithms that are called "reasoning", that are somewhere between prediction and full-blown reasoning?
"Looking cool" IS a component of UX. UX includes the user's emotional experience of using the product. It is 100% acceptable to do something for UX that is otherwise bad "UI". While you talk about UX here, you really mean UI, because the UX is arguably improved at least for some audiences, who are more positively affected by the dimensionality and light-conscious design the effect brings than negatively affected by the readability downside.

In the bigger picture, people use products to perform a function that often includes how they feel in and about themselves while using it. People buy cars to tell a story about who they are. People buy coffee and sit at a cafe in order to get a moment of peace or some internet access. People wear shoes that are a little less comfortable in order to get compliments on them. This is not bad UX. This is literally the meaning of good UX - paying attention to what people actually want versus the minutia of objective functionality.
I work in a prestigious group within my company. The solutions architects across the company aspire to this group. As such, the cream rises to the top, and I work with amazing engineers. Unfortunately the 6% yearly PIP quota must be met, even within this group. So, you end up with the best of the best in the company fighting to stay off the PIP list. Recently my company started forcing this 6% PIP quota to be met within each band. So now, at the principal solutions architect level, you have the best solutions architects in the company, at the highest level, working on the most prestigious accounts, who must be PIPed at 6%. On my account alone, with roughly 3 SAs, over 5 years, 3 have been PIPed. Each one would have been the top SA on a lower tier account. The management has their favorites, and bring in new SAs as backfill. Those SAs are now PIP fodder. Each time we get a new SA on the team, I have a one on one with them, and explain the history of our team. The wise ones understand the situation and jump elsewhere in the org. It’s become this revolving door of exceptional talent, who our customers adore, who keep getting PIPed. It’s not good for the customer, and not good for the company. The engineers who survive have taken an offense approach to the situation, setting other SAs up for failure. Ultimately the roles are filled with a collection of scheming back stabbers who are more skilled at politics than delivering results.

In my own role, I’ve realized that getting promoted is more likely to put me in competition with a more elite set of engineers, so I continue to decline the promotion offer. I happily perform at top of band in my current role, and avoid the PIP stress. I’m likely sacrificing $100k/year for this peace of mind, but also expect to work another 7 years in this role at this level, as opposed to maybe 3 years at the higher level before getting PIPed.
Can’t be more expensive than AWS
If you're doing tooling churn, that may be an issue. But in an organization, tooling updates are always slow.
https://archive.today/0H4VS

https://bsky.app/profile/rarohde.bsky.social/post/3lb7sxiomt...
Only one place I have worked at had the goal of writing code as if it were from just one person and it was pretty nice, honestly. The diff tool output was easy to understand (not a lot of noise). What made it work was everyone was pretty mature and understood that this was a group effort, and not everyone was going to get their personal itch scratched around brace style, etc.

We did have some outside contractors who didn't get it at first, but after several of their submissions were rejected (with potential financial penalties) they got onboard and followed the guidelines we had sent them. "These people mean it."
I totally agree on that, I was not saying that it is not important, I just found the paper lacking depth
> Worth noting: diesel definitely fulfills the "providing compile time guarantees" criteria.

Also sqlx.

I liked the article and I bookmarked the library but this statement from the author confused me a bit. At least two libraries give you pretty good compile-time guarantees. sqlx even gives you the option to specify a DB where it can check whether your queries will succeed at runtime.
I imagine there is and order of magnitude of difference between how much you can translate in software, with large memory and significant time budget to work with, compared to microcode.
I don't know about houses but I've camped a while in those temperatures and with heavy down sleeping bags, suits and insulated boots it's fine. I never really felt cold.
Agree. SQL libraries should aim to make any valid query possible to express (though semantic equivalents are fine) while integrating query building into the rest of the language as seamlessly as possible.
Mercantilism is an about face from US conservatives' insistence on free markets and market based solutions to everything. This article at least acknowledges that fact, although all the author does is cluck his tongue at the predestined to failure departure from Reaganism.

No "why" in this essay, no examination of who wins from mercantilism. Seems like a failure on the author's part.
I don't think this actually is a parody like the author claims. It's more of a pastiche, but a pretty bad one since the core conceit of Story of Mel was that it was real, while this is just made up nonsense.
Algorithmic feeds are useful. Algorithmic feeds that promote primarily people who pay the platform, downrank links, and are likely manipulated for political reasons are far less desirable. On X it meant that I was discovering far less quality content because many intelligent and interesting people didn't want to pay for the platform, often due to Musks's behavior.

BlueSky's algorithmic feeds are less good so far, but they're far more neutral and there's more transparency into how they work. Over time people have the ability to create new types of algorithmic feeds.
I'd actually leave it up to the owner. Some want their work removed, some don't care.
I gave up on Ubiquiti because of the cloud nonsense. Altium is pushing cloud hard (and pushing me to KiCAD). I'm a weirdo for using a mac w/ only a local account (no apple id). I can't buy any new or electric vehicles because they're all 'smart'.

The cloud is artificial, so it must be chemtrails, which explains why modern software feels like its giving me cancer. Wake up sheeple. /s
I said killed, not murdered. It is killing plain and simple, and if we cannot face up to that fact as a society then we are surely not ready to make the decision.
The first two of these are weird cases for reading the standard and arguing with your compiler vendor because regardless of the legality they’re stupid code. Reference lifetime extension is useful for generic code where the function may return either a reference or a value, and is just bad code in nearly any other circumstance. The array initialization example is something that never actually worked, and a newer compiler version exposing some code that appeared to work but didn’t is sort of routine?
> IMHO, the root cause of this is the advertising + subscription business model

What is your alternative?
Russia ditches Windows and move to Linux
Can't throw someone out a Linux
https://archive.today/EYyvA

Previous:

https://news.ycombinator.com/item?id=42231922 - Nov 2024

https://news.ycombinator.com/item?id=42218893 - Nov 2024
>My opinion is that SQL should be for computers to write. This would put it firmly in the same category as LLVM IR.

This is nuts.

SQL is a high level language. It's higher level than python or rust. It's basically a declarative statement that's almost english-like and it's specifically DESIGNED to be more readable and easier to use by humans. It compiles down into many procedures that don't easily map to the SQL statement itself. You can't get any higher level than SQL.

The issue here is that the database exists at the bottleneck of web dev. It's where state mutation happens and it's essentially usually the slowest part of the pipeline in a computer. Yet instead of having fine grained low level control over this part of the pipeline, we have a high level language on top of it. So if we want to optimize this part of the pipeline we have to HACK the query. We have to make the abstraction layer leaky in the API itself with EXPLAIN. We can't do direct optimizations because SQL is so high level. It is a bit of a problem but the industry is so entrenched in SQL that it's actually 10x more efficient to just use it then to develop an API that's more appropriate for this level. SQL is tech debt we are sort of stuck with. The ideal API would be one that is both high level but allows fine grained control... but we don't have one yet.

To use machine learning analogies. SQL is a local optima. There's a much more optimal language somewhere in this space but we are stuck in the local optima and it's likely we will never end up finding the actual optimal api.

In short SQL is the furthest thing from LLVM IR. It's crazy. You cannot treat it as the same thing. If you do there are huge problems.

The problem with rust query and the problem with ORMs in general is that the API for these libraries are in itself high level. They are HIGH level abstractions ON TOP of high level abstractions. You want to optimize a query now? Well you need to hack the first high level abstraction in such a way that it hacks the second high level abstraction such that it produces optimized compiled procedures. That's the problem here.

All this ORM stuff is just programmer OCD. We don't want to do meta programming where we have another language living as a string in our web app. We want everything fully integrated so we create an abstraction in attempt to get rid of an abstraction that was intended to be an abstraction in itself. It's aesthetics and the aesthetics actually makes life harder.
Ask HN: Anyone using Yandex YDB in prod?
Looking mainly at YDB, Scylla, and Yuga for a massively horizontally scalable, read-centric workload.
The diamond with information you're hypothesizing would have been dug up and modified by that prehistoric civilization, only to be put back under ground. Otherwise, it wouldn't have been found in a diamond mine.

And would you trust (very) future civilizations to come across a small diamond and think: hey, I'm going to fire a laser through this thing in a particular sequence and interpret the outcome as UTF-8? I think anyone who wants their data saved for posterity would give that some thought and not leave it to chance.
Same, but waking up is very painful, I just want to go back to wherever.
I had to implement fork on the first Posix implementation, under CTOS back in the 90's?

It is a terrible thing. Inefficient doesn't begin to cover it. Duplicating an entire process state, page tables and code bindings and allocations and on and on. What does the child do next? Usually, it exec()s which means "exit and run this other thing).

Literally double the overhead that you wanted.

spawn() is probably what most people should do, instead of fork().
I do have one newer Toyota Tacoma for the purpose of "just working" and it does a great job of fulfilling that role, but includes a host of features and such that I really have no interest in. But if you have project cars, you really just need a very stable "normal" vehicle for day to day.
Problem with that is it’s too easy to effectively have 0 taxes.
They’re fighting a calcified perception in the corporate IT market that the standard “unit of scale” should be a dual-socket system, because they have a differentiated product in EPYC that shines single-socket.

This likely still remains a major market barrier for them: Outside of the always-be-optimizing hyperscalers, “ordinary” datacenter buyers tend to follow old patterns and rules of thumb from generation to generation.
Data.olllo No Code Data Assistant
Data.olllo is an innovative data manipulation and analysis tool designed to empower users with a powerful interface for exploring, processing, and visualizing data without requiring any coding knowledge. The application provides a user-friendly environment that simplifies complex data tasks, making data analysis accessible to everyone.
I did a lot of sleep hacking in college, trying to sleep as little as possible so that I could spend time with friends, play video games, and (ostensibly) study.

Now that I'm working a job where I do overnight deployments, often work 12-14 hours days, and have a couple of kids who don't sleep well, I hate my past self for not sleeping while he could. You never know when circumstances will drive you into unplanned sleep deprivation. Doing it to yourself for low-to-mid-level time gains isn't worth it.
Funny :) I was thinking about the old story noted at the end of the article while reading this article.

Cool little story.
> it sounds like she did not exercise sufficient due diligence, just assuming it was okay because PWC said so

Agreed. There was a time when having a big five certified accounting firm explicitly sign off on a practice was generally considered sufficient due diligence. That's no longer always true.

> I think it's a great illustration

I meant Michelle's prior company but wasn't clear enough. What made the prior company not a great example was being a mix of not ethically guilty on the options dating but (probably) also doing some other stuff that was worse (going beyond 'not careful' to sloppy and maybe actually shady).

> Can you cite some specific laws that you think are too easy to run afoul of by accident?

Not off the top of my head. I'm not in finance. My understanding of this is from some "shop talk over beers" type conversations I had a few years ago with senior finance execs and the chief legal officer of a large publicly-held tech company. Among this group the consensus was that some better regs had been needed but that the pendulum was swinging too far the other direction to the extent it was starting to make some parts of their jobs combinatorially complex to stay in compliance. To be clear, I never got the sense they felt the chances were high that ethically innocent finance people could be prosecuted over honest mistakes but more like it was going from as rare as being struck by lightning to being something real to worry about.
I'm inhabitant of a country Germans tried to anihilate in 1939. Germany of 1939 is usually called Nazi Germany here, still- it's Germany. Same as Soviet Russia who attacked 17 days later- it was Russia, not some misterious nation called Soviets. These are language cover-ups. I do acknowledge there had been many Germans who chose death rather than to join their countrymen in horrible crimes, and I admire those who did not join. Unfortunately orders of magnitude more volunteered and were actively taking part in German death machinery.
If required, The upgrades will come when FSD is at a point they know what is required.

It’s hard to determine if upgrades are needed before they have FSD working.