skysight-inc/HackerNews huggingface dataset:
I don't think you understand the value proposition of chatgpt today.

For context, I'm an expert too. And I had the same experience as you. When I asked it questions about my area of expertise, it gave me a lot of vague, mutually contradictory, nonsensical and wrong answers.

The way I see it, ChatGPT is currently a B+ student at basically everything. It has broad knowledge of everything, but its missing deep knowledge.

There are two aspects to that to think about: First, its only a B+ student. Its not an expert. It doesn't know as much about family law as a family lawyer. It doesn't know as much about cardiology as a cardiologist. It doesn't know as much about the rust borrow checker as I do.

So LLMs can't (yet) replace senior engineers, specialist doctors, lawyers or 5 star chefs. When I get sick, I go to the doctor.

But its also a B+ student at everything. It doesn't have depth, but it has more breadth of knowledge than any human who has ever lived. It knows more about cooking than I do. I asked it how to make crepes and the recipe it gave me was fantastic. It knows more about australian tax law than I do. It knows more about the american civil war than I do. It knows better than I do what kind of motor oil to buy for my car. Or the norms and taboos in posh british society.

For this kind of thing, I don't need an expert. And lots of questions I have in life - maybe most questions - are like that!

I brainstormed some software design with chatgpt voice mode the other day. I didn't need it to be an expert. I needed it to understand what I was saying and offer alternatives and make suggestions. It did great at that. The expert (me) was already in the room. But I don't have encyclopedic knowledge of every single popular library in cargo. ChatGPT can provide that. After talking for awhile, I asked it to write example code using some popular rust crates to solve the problem we'd been talking about. I didn't use any of its code directly, but that saved me a massive amount of time getting started with my project.

You're right in a way. If you're thinking of chatgpt as an all knowing expert, it certainly won't deliver that (at least not today). But the mistake is thinking its useless as a result of its lack of expertise. There's thousands and thousands of tasks where "broad knowledge, available in your pocket" is valuable already.

If you can't think of ways to take advantage of what it already delivers, well, pity for you.
I was not aware that I needed any code at all to edit emails...
Also if you use rerere you don't really spend much time doing repetitive rebases after the first rebase
The fears are legitimate. Both rebase and force-push can lose data in some circumstances, which merge and push cannot. Yes, there are strategies which, if followed perfectly, allow one to avoid losing data when doing rebase and/or force-push. But those strategies are not simple to describe, especially to newcomers, and in practice people make mistakes; all else being equal, an inherently safe workflow is better.
You're right that that is what gets built. And that's completely OK. Imagine one of those new big houses gets built. Someone buys it, they have the money to afford it. If you don't build that house, that person with their money still exists. But instead, they outbid you for one of the units that should be less expensive. That raises the price of existing housing and keeps you from buying something. That's the process that is the problem when you don't add new supply.
> I don't care about work because I'm not pathetic.

I honestly don't know who you're trying to convince. The lady doth protest overmuch me thinks. Perhaps you're hoping I'll collapse under the sheer weight of your tedious prose and say, actually, you're right, my work 'tis sound and fury signifying nothing after all, you're so right?

> Ultimately when you inevitably die you won't remember meetings, or cubicles, or water cooler talk. And that's really the big idea.

That's actually a small and pathetic idea because, unless you've made a groundbreaking discovery in neuroscience, I'm sure no one remembers anything after they die. People who mistake useless ideas for profound insights definitely need therapy. That's called delusion.

> Who do you want to be?

I want to be someone who does great work.

> What do you want to spend your care on? And, who will care? I can tell you right now - not a single person in your life who matters gives a single fuck about what you do at work.

I'm genuinely sorry no one in your life cares about what you spend most of your week doing. That's really tragic.

But even if I were in your shoes and no one cared, that's irrelevant. I care! and in the calculus of existence, my opinion of myself is what matters.

> So WHO are you performing for?

It's actually you who is performing, or rather affecting, a rather tired brand of cynicism. Incidentally, cynical people tend to perform worse than average in cognitive tests so …

But seriously, your talking to a man who was trained by Opus Dei. We believe that any work whatsoever is a sacrament which we offer to God, and so that imbues even the most trivial janitorial work (which I have done in the past) with deep significance. And that's even before I go on a long spiel about how I love my work and what I'm doing is literally what I dreamt of doing as a boy.

But good luck to you, friend. To each his own. It's your life, you're living, not mine. I wish you well.
https://us.v2ex.com/ This is the HN of China.
Yeah I totally agree with you. Lots of goalpost moving, and it is absolutely insane what it can do today and it will only improve.

It just can't translate the kinds of programs I write between languages on its own. Today.
Better hope the defense attorney doesn't ask who the caller was. Parallel construction is actually not legal and can result in evidence being inadmissible.
It sounds like you aren't very clear on what a "runtime error" is yourself, or what role they play in software development, which I guess is why you didn't see anything wrong with the ostensible definition in the SWEBOK. You could probably learn a lot from reading my longer comment carefully enough to understand it.

The audience of the SWEBOK is not only, or even primarily, learners. This is explained in the preface.

Thinking my comments are pompous—because they're written in a more formal register than you're accustomed to reading, I suppose—is no excuse for your invective.

I didn't read the whole document, but, as you can see from https://news.ycombinator.com/item?id=41916612, I did generate a fair random sample of 10 half-pages of it and read and summarize them. All of them were similarly incoherent and full of serious errors of fact that can only be attributed to profound incompetence. That's an adequate basis on which to conclude that the whole thing is bad. Moreover, everyone else in this thread commenting on specific parts of the document that they've read has similarly damning comments. (Except you, but at this point I have, I think, ample reason to discount your opinion.)
Im more worried about the question title turning into a statement of fact.
Tell me more about this massive switch to single income no kids! I haven't heard about this, I thought it was always a generational change and tends to work itself out.
Rebase can result in a long chain of commits that don't compile, which makes it impossible (or at least harder) to use automated bisect, or even semi-manual approaches like running a test case manually on each bisect step.
>How do you reconcile his "bullshit" with the fact his spaceships are saving astronauts from space?

Easy - they aren't "his spaceships". He funded a bunch of other really smart people doing incredible things with rockets. That doesn't really exonerate him from continually spewing bullshit. If you want to go with Space-X bullshit - in 2016 he said there would be manned missions to Mars in 2024. He did it again in 2017, and multiple times after that. If there's one thing you can be sure of, whatever date Elon tells you something is going to happen, you should promptly throw into the trash where it belongs and try to find someone else at the company in question that isn't a pathological liar to give you a realistic timeline.
I have. It was a complete fucking shitshow. In a kernel tree, doing a git bisect with the messy merge history will take you on a wild goose chase, where you land in some branch developed by an entirely different team somewhere, working on totally different hardware from you, with a different kernel version, which you have no hope of building and booting.
The work demonstrating the Frankfurtian Bullshit nature of generated prose would suggest as much, given the architecture is the same for code outputs it seems like a fair assumption until it is demonstrated otherwise.
Very nicely written article. Personally, I find RAG (and more abstractly, vector search) the only mildly interesting development in the latest LLM fad, and have always felt that LLMs sit way too far down the diminishing returns curve to be interesting. However, I can’t believe tokenization and embeddings in general, are not broadly considered the absolutely most paramount aspect of all deep learning. The latent space your model captures is the most important aspect of the whole pipeline, or else what is any deep learning model even doing?
I do something similar, and I've come to appreciate the manual work. It lets me take a moment and reflect on what's important before I copy it over to/from the endless list.
In https://news.ycombinator.com/item?id=41918401 you admit that you only skimmed my comment; that's why you mistook it for nitpicking. Consequently, your response is wholly incorrect.
A personal project or small company, no. At small scale the only advantage is has is the concurrency primitives and for that I'd use a BEAM language.

But the verbosity and "one way to do it" is a plus for large enough teams. There's no need to decipher someone else's code when you come in to it. The way they did it is the way you'd do it, because there's just one way to do it.

Verbosity is less important for reading code than writing it, and on big projects you do a lot of reading.
:-D The styling is adapted from https://edwardtufte.github.io/tufte-css/
It's also custom logic to embed the code snippets within the article, they're all working code that gets pulled in from rust files. Really stellar stuff.
> In the lawsuit, Garcia also claims Character.AI intentionally designed their product to be hyper-sexualized, and knowingly marketed it to minors.

A company built technology that fully automates the act of sexually abusing children and the comments here are all just people quibbling about the presense of weapons in a home.
claude-to-sql parser is particularly useful in LLM implementation
if there is only one valid translation of the type constraints into executable code then what you have is a slow, expensive, and occasionally argumentative compiler

it merely remains to build a debugger for your Turing-complete type system, and the toolchain will be ready for production
Node also struggles with Node.js, and that's including its shortcuts that kill reproducibility. A node.js sync from an empty cache is by far the longest part of any build process I maintain. It's still a long step with a full cache and without doing anything.
Right. I understand that. I agree it’s a good functional choice. It was my original point that functionality largely drives the design.

This comment you are responding to was me digging deep and wondering what design flexibility existed and thinking through it out loud.

Some parts aren’t white. The shoes are blue. The knees are grey. I want them to talk about that design process that led to those colors in those places and how they balanced aesthetics with functionality.
bisect works much better with merge than it does with rebase (with rebase it's easy to end up with a long chain of commits that don't compile, so your automated bisect script doesn't work).
Vimeo for Apple Vision Pro
Personally, it seems obvious to me that this is the desired end state of AVP-related development, but somewhere along the line they decided that pure AR tech just wasn't good enough yet for the display quality and UX stability they wanted, and so they ended up with the headset as a clunky hardware compromise built around an OS mostly designed for the glasses use case.
Great idea. I’ve used that tactic in the past for non-code related prompts; not sure why I didn’t think of trying it with my code-generation prompting. I’ll give it a shot.
I am definitely going to have to check that out for my own site!
It's there for my AirPods Max in the current 18.2 beta.
The main reason they should not accept merges is that they don't care about you and your repo. In order for an upstream repo to accept your work as a git merge, they would have to fetch all your objects so that they have enough of your repo in order to represent your original branch, where the parent pointers of the merge are aimed. Nobody who is anywhere near sane wants that kind of cruft.
This is cool.

I mirror a lot of OSS projects I care about and searching through all of them at once will be fun.
The man may exaggerate pace of progress but he has more than proved him self with TESLA, SpaceX, Neuralink. that's 3 bleeding edge companies in 3 different industries.

p.s) For those misinformed about state of Neuralink.
Currently in beta with quadriplegic patients.

https://www.youtube.com/watch?v=gVcMpjIY52Q
> A linear commit history is objectively better.

Disagree. You can always flatten a commit graph into a linear history if you want, but you can't restore the original commit graph from a linear history. So preserving the original history is objectively better.
I literally said I do use it, often.

But just now had a fairly frequent failure mode: I asked it a question and it gave me a super detailed and complicated solution that a) didn’t work, and b) required serious refactoring and rewriting.

Went to Google, found a stack overflow answer and turns out I needed to change a single line of code, which was my suspicion all along.

Claude was the same, confidentially telling me to rewrite a huge chunk of code when a single line was all that was needed.

In general Claude wants you to write a ton of unnecessary code, ChatGPT isn’t as bad, but neither writes great code.

The moral of the story is I knew the gpt/claude solutions didn’t smell right which is why I tried Google. If I didn’t have a nose for bad code smells I’d have done a lot of utterly stupid things, screwed up my code base, and still not have solved my oroblwm.

At the end of the day I do use LLM, but I’m experienced so it’s a lot safer than a non-experienced person. That’s the underlying problem.
You really think those laws are coming? That the US and Chinese governments will force AI companies to put the genie back in the bottle?

I think you're going to be very disappointed.
Yeah! I have a whole laundry list of things I want to improve on my site now
> The point of rebasing is to do it often, like every day at the very least for an active integration branch. This hopefully means you'll resolve any conflicts as soon as they happen, while it's still fresh in everyone's heads.

You can do that with merge just as easily though - just merge master into your branch.
Also, there is at least one synth (Serum) where the developer declined to document the file format of the presets:

"I reached out to Steve through Xfer's forum and he was prompt and helpful. Unfortunately, the .fxp file format is completely dependent on the source code, and he can't release a spec for it without making the code open source. Which probably isn't happening any time soon."

https://www.reddit.com/r/edmproduction/comments/69hxa7/rever...
That is the problem for the narco-state and its corrupt policies, and shitty corrupt border patrol/customs.

Our border is open to human trafficking, domestic infiltration, and massive practically a neo-chemical weapon.
> All military strategy is actually the cunning deployment of wasted resources to wrong-foot an enemy.[0]

[0] https://www.youtube.com/watch?v=ZtCG-Jo51d4&t=2419

https://en.wikipedia.org/wiki/Rory_Sutherland_(advertising_e...

It's a repeat of the Cold War space race, with moonshots like SDI designed to waste time and resources of the enemy more than it wastes your own resources, and you might even produce a product or outcome that is better than the status quo. Along the while, you get to impose sanctions on those who assist the enemy to do what you already are doing.

You do this, because your enemy is also already doing this.

https://en.wikipedia.org/wiki/Strategic_Defense_Initiative

https://www.reuters.com/world/russia-has-secret-war-drones-p...

https://archive.is/eCSmw
Makes the history less useful for bisection - you'll always land on a squash merge rather than the specific commit that caused the problem.
In the last year, I've driven almost every new EV available for under $100,000.

Tesla has more range per dollar than almost any others. Many have antiquated, unusable infotainment systems designed for legacy cars. Some get marked up by $10,000 or more by dealers. None have the simplicity of charging.

Tesla is still selling most of the EVs on the road. Slowdowns attributed to Musk's shit behavior are never compared with their peers, who are having even worse slowdowns. Having driven nearly all of them, I understand why.
iOS actually offers quite a few customization options hidden in the accessibility settings (I say hidden because most people won't think to look there, or at least not first). It's worth exploring, even as an able-bodied person (other than terrible, but correctable, eyesight) there are a number of useful settings I've found. Plus it helps when I am working with family members who do need those options since I've seen and played with them myself so can help them more.
Here's one I built with Claude last week: https://news.ycombinator.com/item?id=41855594
But using old 90s ux is so satisfying
It helps to think of these people as essentially Mao's Red Guards. They are (I hope) still very young and as a result very absolutist in their thinking. They are fanatical about their country being the best because they haven't seen or experienced much else. And they get a sense of power from belonging to what they think is the group of the People Who Are Always Right.

Mao's Red Guards. Because these ducks quack like those ones did.
Insufficient definition.
The linear part of the history is objectively better than if that same change were collapsed into a single patch bomb.

Git rebase does not destroy history, it just does not link it together. That might be a bad thing. But the individual commits all making an appearance on the destination branch is a good thing.

From those who favor merge, what is bad is that there are no second parent pointers tracking where those changes came from.

This coulid be obtained by reimplementing git rebase as a sequence of merges. Git rebase is a sequence of zero or more cherry picks, not merges. If git rebase merged each commit instead of cherry picking, each commit would have a parent pointing to its original.

In a git bisect, there would be no need to chase those second parents; you would be looking for which merged commit introduced the breakage, and not care about its original, except in some rare situations where you want to analyze more deeply what went wrong (and then that parent pointer would be a bit handy).
More importantly IMO he wrote the github-flow post, the best dose of sanity in git workflows I've seen.
The 2005 Federal Protection of Lawful Commerce in Arms Act broadly protects firearm manufacturers from liability. It does not prevent settlements as in the Sandy Hook/Remington case. It does not prevent civil suits or suits in state courts. But it makes those suits much more likely to ultimately fail in court.
Thanks for making this public. What's the ballpark BOM cost?

Could a directional antenna help with locating RF sources? There's some older work ("WokFi") on parabolic antennas for WiFi, https://web.archive.org/web/20140802123553/http://www.usbwif...

Here's another circuit design for AD8317, https://g8rwg.uk/articles/noise-meter-ad8317/

> The AD8317 module I’m using has the logarithmic slope set to 22mV/dB. I used the output of a Viavi JD785 at different frequencies to check the slope and dynamic range of the device. Linearity and dynamic range at 1GHz and 3.5GHz is good and as expected drops off at 144MHz and 6GHz.
This argument seems weird to me because even without rerere I found myself doing a lot more work managing merge conflicts with git merge instead of git rebase

As a git merge fan, are there any tips or tricks you suggest beyond the stock git experience when doing git merge to minimize the amount of merge conflicts you get?

I found it was especially bad when doing a git merge on a refactor, but I admit it could just be that I abandoned git merge earlier in my career before switching to rebase and never properly learned it

My most common use cases are feature or bug branches with a lifespan between less than one day and up to one month (although I absolutely have some features on pause for even over a year, in which case interactive git rebase and partially squashing WIP commits is my current method of updating)

All this is for repos from literally just me, to a few changes a month between 3 devs, to 5-2 devs doing multiple commits per day, to some open source projects with commits landing every few minutes from multiple devs if it's like a release day

My current biggest issue with rebase is verified commits with GitHub and a bit of guilt for rewriting committed feedback from other authors on my PRs

The only time I really use git merge is when I want to see how my work interplays with more than one feature branch at once, or if the feature branch I want to integrate hasn't rebases themselves in a bit and conflicts occur
The UX itself is an iPhone-vs-Blackberry style leap compared to every other AR or VR device out there. It's just a fundamentally better paradigm for basic tasks and for mixing a headset (or future iGlasses) with non-VR activities.
"Nordic Army" was the favourite of No-Nato leftists and pro-russian vatniks. Along with Nukular-Free North (all others except Russia).

So very much dead concept now.
Noted! I'll make sure to edit that. Thank you for the feedback.
Honestly, a lot of the critics would have bought the device for $500. It’s just that the price doesn’t have a selling point that justifies the current pricing
Sure, but this is all happening over HTTPS (Etcha only listens on HTTPS), it's just an added form of protection/expiration.
> there is a correlation.

I don't see it.
Removing all the old contributions is probably impossible.

IIUC in case they want to contribute, they must send the patch to the new maintainer of that part of Linux, instead of sending it directly to Linus.
Mandatory salute to JIR => https://web.archive.org/web/20190901210011/http://jir.com/
Common C implementations (clang, gcc) have static destructors as an extension, though C codebases probably use this a lot less than C++ ones with static objects and destructor methods.
There’s actually some nuance to this. One of Apple’s big requirements was to have quite lax acceptance criteria. They didn’t want lots of their customers being denied for cards and creating a negative brand association.

Apparently GS was up for that. Possibly because they didn’t actually know what they are doing. My understanding is the loss rate was way too high for them to be profitable.

It was well covered at the time, here’s the first example to come up in a quick search:
https://www.cnbc.com/2022/09/12/goldmans-gs-apple-card-busin...
Waymo has limited service in one of the smallest “big” cities by geographic area in the United States. You can’t even get a Waymo in Mountain View.

Fact is Google will never break even on the investment and it’s more or less a white elephant. I don’t think it’s even accurate to call it a Beta product, at best it’s Alpha.