skysight-inc/HackerNews huggingface dataset:
See for example the last version, which is marked as "GOOD". It directly inlines all operations on the vector. The more you use it, the bigger the compiled code becomes. Need to debug it and want to set a breakpoint to vector_append? You can't. You also can't use callgrind/kcachegrind to see how fast the functions are. Yes, it's still C, but very awkward and finicky C.
In order of precedence.

0. Meatspace.

1. IRC, mostly on rizon and a bit on libera.

2. Imageboards that don't require accounts.

3. General web, via some shell scripts I've written that give me pseudorandom content from various aggregators.

4. HN

5. Discord, but it I try to avoid as much as possible for ideological reasons.

6. Public unix system micro-blogs/gopher-holes.
That's a junior dev rate, and a low one. A good job for a new grad would be USD 30/hour.
background execution is a pretty normal one for e.g. smartwatches. Being able to reliably have interactions with accessory devices in both directions is kind of important to a good experience. For instance, the Find My Phone feature on fitbit devices breaks if you close out of the fitbit app on your iPhone.

nfc is more niche and Apple Wallet already covers a lot of use cases so idk what the use case is there.

documentation for private symbols is because the EU is also introducing a process to request access to private APIs.

> The Commission considers that developers may benefit from having access to a high-level description of iOS and iPadOS components to enable a broad understanding of available features and functionalities, which can then be useful and sufficient for clearly identifying the relevant components within a developer’s interoperability request.
> We put Japanese people in internment camps until 1946

And now they are economically ahead of the average American. Universities actually discriminate against them by their malevolent definition of "fairness" where success is a punishable offense. People are where they are because of what they do today, not what happened to their ancestors in the past.
And yet there are still many people, some who comment here, who think that they can and do write C/C++ carefully enough to avoid memory safety bugs. The hubris and arrogance is mind-boggling.
My dad used to be a Professor at a major State university, and he talked about how one of his older colleagues, who was a professor of Electrical Engineering, had his secretary (yes, he had a secretary) print out his emails for him every morning and put them in his physical inbox. He'd read them, type up his responses, print them out, and have her transcribe and send the responses later in the day.

Just sad really.
The market also depends on your wants. One house is not always equivalent to another. Location matters of course. However layout, color and other features matters (some of them are trivial to change some not).

Adam Smith observed that when people got more money they tended to spend it on better housing. That observation is mostly true today.
I don't think that's quite true. When I was working for a large/stable/boring company in Calgary, the lowest paid green devs made more than C$56k/year.
In my current job, I was hired based on my previous professional work as a DevOps engineer for a three month emergency job, in order to set up a basic CICD pipeline for a project. Two months in, once the basics were in place I pivoted to embedded software development in that same project and I'm still there nine months later.

I didn't have any professional experience in that particular area, but that pivot was possible thanks to my previous open-source work and general faffing about with low-level stuff. That part gave me an edge during the interview over the other candidates, to the point that they straight up selected me without even seeing the rest.

Open-source work is like professional work for a job: the experience is relevant if it's applicable for the job at hand. Writing boatloads of NPM modules will not help much if the job is about working with resource-constrained microcontrollers and real-time operating systems.
You simply don't understand economies of scale. If you produce 10,000kg of meat a month and decide to sell it off to private customers 0.5-3kg per sale on some farmer market, you need somebody spending whole day managing sales, delivering stuff to sales point, managing unsold meat and so on. If you don't manage to sell it and it goes bad, you tank and soon whole business is over, this ain't some pottery.

Then you have hypermarket chain coming in and telling you they will buy 5,000kg per month, regularly, for next 12 months at lower price, just show it into back of that truck in 1 hour. For much lower price. Still farmers sell to them, so even with their additional 20-50% on top of the cost its cheaper for end customers. Or they subsidize some meat for few days to lure you into shop and bus some other necessities to balance this smaller income.
I've been using it for the past hour or so.

I told it to make a TODO list (based on my instructions) and now I'm just repeatedly creating a new chat just saying 'work on the todo list'. The thing I'm giving it to do is pretty easy (fix some React components to add types and replace hardcoded strings with props). Doing the same thing in Cursor was annoying, due to the chatter, and the fact I had to click 'Accept all'.

For single file changes, it's nice. I haven't tried it with more complex things yet.
Hurray for this approach! I want most software that works with my personal data to work like that. And I'm actually working on a hobby project to make it possible: a local database + platform to run "local" apps on it.

I haven't gotten to implementing the data layer yet, but my idea was indeed to go for "simple files in folders". But I'm wondering, what format should I use for files containing structured data used by a specific app? For a photo app, using image formats is the obvious and easy choice. But what about, for example, a meal tracking app? What file format would you use to store nutrition facts about a certain food?

My first thought is JSON, but that's not really user-friendly. For a non-technical user a JSON file is basically useless without the app that generated it. YAML is maybe a bit less cryptic for a non-technical user, but still mostly useless. A TXT with a specific, more user-friendly format? Then you risk the app breaking because the user changed its content. And still, as a user what would I do with a bunch of TXT files containing nutrition facts? Without the app that generated them, there's a high chance they become useless.

My project also wants to solve that issue actually, ensuring that you always retain access to the apps that generated those files. But I would love to find a way to store data so that it keeps being useful and accessible even "app-less".
You know, this was one of those article titles I was really expecting to not be literal.
From a safety perspective they aren't very close, there is a reason that all these CVE bugs are C code.
Use claude 3.5 if you have detailed instructions that you want it to follow. I've found over many hours of using these models that 3.7 loves to go off-script no matter how many rules you provide.
I also don't see a detailed run down in the paper of zoning laws and other local regulations and how that contributes to cost. They looked at a lot of top level numbers (from what I could tell) without diving into the specifics.

Zoning laws while not completely uniform, do seem to follow patterns across the country. The long and short of it is, the more desirable some place is to live, the more restrictive zoning laws and harder it is to get approval for builds and it depresses housing inventory over time.
>offering development resources based on race, an immutable characteristic, is deeply unsettling to a lot of people.

I understand, but I'm trying to provide a point of view that might make it less unsettling. Otherwise, we're just kind of saying that people find it unsettling, so it must be wrong (BTW, we also can't overlook that there are people who want to make it more unsettling, for reasons).

Anyway, it really comes down to backing up a little to consider why race became a factor. Else, if we simply start the clock at the inception of these groups, then I suppose it should be unsettling.

Interestingly, there are other immutable characteristics that do not trigger that unsettledness. If nothing else, this gives us reason to question why this particular characteristic became so charged.
The key point is that places they want to go are close by because of their (IMO very sensible) approach to urban planning:

> This level of urban development isn’t just unusual in almost all of the United States. It’s illegal. Utrecht, the city in the first photo above, has approximately the same metro-area population as Wichita. But because most of its central city was built before the passage of laws that required minimum lot sizes, maximum numbers of homes per lot and lots of on-site car storage everywhere, everything in Utrecht is much closer to everything else than anything is in Wichita.
Free polite speech has rarely been enough to have meaningful results. In the USA, you can thank the Boston Tea Party, heck the American Revolution, for political change, and lots of civil violence in order to get a 2-day weekend and a more-or-less 40-hour work week. The Tea Partiers that the Koch brothers funded that disrupted orderly speech became Maga and run Biden campaign buses off the road, that's been effective too.
>dandelion flowers are eddable and good with fish fist soaked in vinegar water

Is it still a fish if it has fists?
Jews and Muslims don't eat pork because their holy books tell them they cannot eat it.

This article is really making up a fancy explaination to very simple subject, Jews and Muslims believe Torah and Quran are devine.

Alcohol consumption was widespread among Arabs and early Muslims before it was discouraged and later prohibited in Quran, you should not play clever to try to explain that differently.
> I'm interested to know if anyone is using fine-tuning to train a model on proprietary or in-house codebases and documentation.

I've done it, 1/2 the team though it was great 20% of the time, 1/2 the team hated it from day 0. I used roughly 500K lines of code.

> How much effort is required to turn code into something one can use for fine-tuning?

Very little to moderate, less than 200 lines of python, QWEM FIM, HF, LLAMA.CPP, LLAMA.CPP code extension.

> RAG solutions seem to have their limitations, and fine-tuning might be a more effective approach.

The only problem either way is keeping the information up to date, RAG just adds more cost to the inference process (which at my dev speed is pretty important).

> How much effort is required to turn code into something one can use for fine-tuning?

Fine tuning "fill in the middle" process is the process of taking a file, cutting out a some text in the middle and asking AI to guess what was there - there is a hugging face example that will have you doing it in an hour or less - your OPs team saying "No you cant litreally copy all code to a single folder" is probably the biggest hurdle (advise them you'll do it in CI and then they can stand up a FIM training endpoint that accepts a csv, pretty easy)
Nice, I was very close to that area (maybe 50km over the woods and mountains to the east). There were tons of sculpins in that river, too. Such a beautiful area.

I've never seen blue robotics before. I almost wish I hadn't, haha. This is going to soak up some time.

Their low light USB camera looks awesome for stream monitoring. You could probably even get decent footage in the shady areas (where I find a lot of fish prefer to be). Maybe under some rocks on an overcast day with lots of diffused light? Could be awesome!

Its peak draw is only 220mA so you could actually record a ton of footage on a raspberry pi 5 without a massive power source (10,000mAh should get you somewhere around 2.5 hours, I think?)
Colored pencils don’t move themselves around the paper, and they’re not full of uncompensated training based on untold numbers of other artists’ work. They require full agency and imposition of your will. That’s why you get credit.

A photocopier is also a tool, but you won’t get credit for Xeroxing the Mona Lisa.
Yes, compartmentalization is an important skill for being a functional, mature adult.

But you aren't supposed to put those feelings in the box forever, just until there's a better time to take them out and process them.
This is what I've been saying for years. The valuable part is the desirable land, which can't be built like a house. Also the rent and value are pretty disconnected.
I've tried this and the temptation to remove the block is too much. I think a better way would be to deal with the underlying reasons why we get distracted in the first place.
Assuming full-time work (40 hour per week, 52 weeks a year with paid leave and holidays), that's about $27/hour CAD or $19/hour USD. If they work more than 40/week then that effective hourly rate drops quickly.
> Preparatory Refactoring says that you should first refactor to make a change easy, and then make the change. The refactor change can be quite involved, but because it is semantics preserving, it is easier to evaluate than the change itself.

> In human software engineering, a common antipattern when trying to figure out what to do is to jump straight to proposing solutions, without forcing everyone to clearly articulate what all the requirements are. Often, your problem space is constrained enough that once you write down all of the requirements, the solution is uniquely determined; without the requirements, it’s easy to devolve into a haze of arguing over particular solutions.

> When you’re learning to use a new framework or library, simple uses of the software can be done just by copy pasting code from tutorials and tweaking them as necessary. But at some point, it’s a good idea to just slog through reading the docs from top-to-bottom, to get a full understanding of what is and is not possible in the software.

> The Walking Skeleton is the minimum, crappy implementation of an end-to-end system that has all of the pieces you need. The point is to get the end-to-end system working first, and only then start improving the various pieces.

> When there is a bug, there are broadly two ways you can try to fix it. One way is to randomly try things based on vibes and hope you get lucky. The other is to systematically examine your assumptions about how the system works and figure out where reality mismatches your expectations.

> The Rule of Three in software says that you should be willing to duplicate a piece of code once, but on the third copy you should refactor. This is a refinement on DRY (Don’t Repeat Yourself) accounting for the fact that it might not necessarily be obvious how to eliminate a duplication, and waiting until the third occurrence might clarify.

These are lessons that I've learned the hard way (for some definition of "learned", these things are simple but not easy), but I've never seen them phrased to succinctly and accurately before. Well done OP!
> We're making more and more luxury cars, why is the price not coming down?

Because supply and demand are carefully watched. Manufactures are not just making more and more luxury cars, they carefully study the market and adjust supply so that their price makes sense. Remember all the materials, labor, engineering, management and other overhead sets a floor to price of a car, they carefully watch the numbers to make them work. They might be making more cars, but they are not making infinitely more.
Can also use a different variable name for the success case and null out any successfully consumed temporaries.

void* p1 = malloc();
if (!p1) return failure;
defer { free(p1); }
...
someOther->pointer = p1;
p1 = NULL;
return success;
You're right; the guideline to not submit most stories about politics was not present from the beginning, but rather newly added in May 02008: https://web.archive.org/web/20080527112502/http://ycombinato...

But that greatly predates the changes in moderation strategies or hiring dang and sctb.

Surely the understanding of the site's social dynamics has evolved over time, though, and so the reasons for the same guideline are different now.
> there are other immutable characteristics that do not trigger that unsettledness

Like what?

> this gives us reason to question why this particular characteristic became so charged

Because it's been a tool of social division. As a result, we've been attuned to it culturally from both sides (separation and integration).
> If you get big enough, they swoop in and make you turn everything you've invented into an open standard?

If Apple is the low bar, then MPEG-LA should be counting their days. The technology to read (legally) a whole slew of formats is stuck behind patent encumberment, but these formats make up the de facto standard for their industries -- see also Qualcomm (who owns 95% or so of the 5G standard) and Broadcom (who for a long time was The Name in 802.11 since they owned so many patents).

Yes, IMO when you hit some amount of market saturation your patents should be invalidated and your work made open.

But each of these is just "Apple's Implementation" of stuff that has been around elsewhere: AirPlay (Miracast/Google Cast), Airdrop (Bluetooth OBEX transfer + BTLE peer discovery), notifications/smartwatch integrations (Android had it first with Pebble and such), headphone handoff (BTLE multidevice hand off), Proximity Pairing (BTLE, again), NFC emulation (Windows Mobile 10 had support before Android/iOS), background execution (this isn't even special, it's just something only Apple gets but others don't).

> Anyone who's maintained a private vs. a public API knows that one is orders of magnitude more expensive than the other.

And yet Microsoft manages to do it for the most part. Apple doesn't release the documentation for a large amount of their API. Think of it less like forcing Apple to open things up but making sure Apple and everyone else has to play by the same rules.
>Why he would toss out years of brand-related goodwill is beyond me.

I suspect that Wolfram is the bigger name ever since Wolfram Alpha has been a thing. I'm sure way more people interact with that than Mathematica. Besides, as far as I can tell, it's still named and marketed as Wolfram Mathematica, not really sure where you got the idea it was renamed.
Not for contributions only, but developing ExtFUSE [1] got me a lot of offers and consulting work.

1. https://github.com/extfuse/extfuse optimizes FUSE with eBPF
My personal experience, essentially is that we smell like pork, our bodies, our flesh. So a taboo makes innate sense.

I had surgery, and I was allowed to handle the part of my body that was resected. It was a bone and there was still some of my muscle.

I smelled like the best piece of pork. Like if you had a piece of pork from a pig, which that pig clearly was loved so caringly before it was slaughtered: it was worshipped, and massaged, and fed all the best food. That's what my growth suggested, odoriuosly.

(Cue the Mike Meyers joke about loving the smell of your own farts, from The Goldmember movie series..?)

My conclusion is, humans smell like pork so it's just kind of yucky to lust after the taste of another person.

There are still people who are cannibals, tribes. At least back in the '80s I understand there were active tribes in North Asia, according to a college professor's (of mine) direct experience.
Your source does not support the claim of the EU having announced a fine. It's an anonymous source saying that the EU will fine Apple and Meta later this month.

You'd expect any fines to be announced along with the corrective measures. Here we only got the corrective measures, which implies that (at least for the domains that these decisions are scoped to, i.e. wearables and the process for handling interop requests) that's all we're getting.
Lost City: A recreation of Runescape as it was on May 18, 2004
Github: https://github.com/2004Scape

FAQ: https://lostcity.rs/t/faq-what-is-lost-city/16
The complex history of reburying Mungo Man and Australia's oldest skeletons
We were talking about a potential new non profit platform not facebook. (Well, I was until one child comment had to bring up fucking Facebook again.) That was the whole point of the discussion and now everyone and their mom ignores it because you all seem to love condescending rage comments. Eh… not worth the keystrokes.
No surprises here. Consecutive apparently identical failures should obviously be throwing up red flags, but moving fast and breaking things was always about iterating. Admittedly, the line between moving fast and breaking things and throwing money into a flame trench is rather thin, but it's only a problem if they ignore their data. Data sure seems to indicate a new design is needed.
> more often unions start as non-bargaining unions

Source? I'd guess most unions start as collective-bargaining unions because if they can't colletively bargain I'm struggling to see their point over, like, a conference or subreddit.
> and (b) have verification your documentation's code samples are actually correct.

I find a lot of libraries don't go through the effort to actually use doctests, and just stick `no_run` everywhere, which defeats a lot of the purpose.
With the added "benefit" of not having to use GPL. Likely the main goal.
Yet there are more successful companies than Amazon or as successful that don’t use this approach.

That clearly shows it’s a cultural or quirky thing, otherwise there would be a clear correlation between a company’s success and the doc culture
Amazing how much more fluid Atlas has become.
Pretty much every device these days decodes VP9 in hardware.

It's been a long time since I've seen a VP8 video on YT, so I'd assume it's not even used anymore due to worse compression.
> you just can't read while doing the dishes or morning cardio or running unit tests

this is literally what audiobooks are for. And I concentrate significantly better on audio if I'm multitasking with a mindless activity
Look, they had a whiskey drinkers ERG when I was there. For people that like to meet to drink whiskey.

I'm not sure what OP actually proposed, but I'm reasonably sure he's not telling the whole story.
Taxes are suppose to keep this from going out of control. but the only way to appeal a tax appraisal increase (here in Washington) is to use OTHER home values in the area that are similar, but less.
Depends on what you mean by "it". :)

If you mean writing the book, then I'm glad I worked on it while going through all that stuff. And, in many ways, adding the book on top of that stress actually helped because it was a thing I could control and feel mastery over while surrounded by other things I had no control over me.

If you mean all of the other bad stuff that happened, well, no I would prefer it if none of that had happened but the universe doesn't seem to care.

If you mean how I psychologically compartmentalized things and the long-term consequences of that... I think I probably did about the best I could have in the situation. There are definitely psychological tools I wish I had had before that stuff happened to me that would have helped (like giving myself actual time to process feelings when I could). But given what I had going in, I think I did OK.
Pretty cool, I like how it moves around, and the mechanic for guessing your way to something you don't know.

I did a lot of sporcle grinding back in the day to learn all the countries of the world. Memories unlocked!
Someone makes concrete allegations of massive fraud and then uses those allegations as justification for huge funding cuts. Folks ask for evidence of the fraud justifying these cuts. They are instead given evidence of the existence of some different fraud that occurred some point in the past.

If you don't see how problematic that is, then why not just avoid the discussion in the first place?