skysight-inc/HackerNews huggingface dataset:
I feel like we'll be having the same arguments forever. Sure LLMs bring some issues but programmers will always find ways to write bad code no matter what tooling or techniques we have available. His critique is basically the same as 'calculators' will make us poorer at mathematics -- at lest in Europe PISA Maths skills have been steadily increasing since the introduction of calculators to school syllabi.
Very likely some table. Tail gating is one amount, running red light is an other, going over 20 km/h(Finland) is one and then you get more as the speed increases 40, 60, 80, 100 over limit...
> No. That's not true. It does not do that.

Windows 10 can 100% download and install an nVidia proprietary driver for hardware it finds.

Indeed I inadvertently trapped it in a boot loop by fitting 2 dissimilar nVidia Fire cards with different GPU generations. This works on Linux if you use Nouveau but not with nVidia drivers.

Win10 lacks an equivalent of nouveau. It booted, detected card #1, downloaded and installed a driver, rebooted, the card came up; then it detected card #2, which wasn't working, downloaded and installed a driver, and rebooted.

Now card #2 initialised but #1 didn't work. You can only have 1 nVidia driver installed at a time.

So, Windows downloads and installs the driver for card #1... reboots... #1 works, #2 doesn't... download driver, install, reboot...

The only way to interrupt this is to power off and remove one card.

When I replaced both cards with a single AMD card, it downloaded the driver and everything worked.

You are wrong. Source: my own personal direct experience.
Is this written by ChatGPT? Feels like it. I think now even genuine content might feel the same.
Nothing is always good at any cost.
Would google appsheet work?
What do you think about Gupta india
For speeding, we do have a fine based on your weekly income. It can be up to 175% of your weekly income (capped to £2,500), if doing >100 MPH on a motorway (or >76 MPH if speed restricted to 50 MPH).
Some of these points may be true, but as someone who just started using Copilot at a new job, on an unfamiliar code base and programming language, it's been a lifesaver.

Obviously you have to read the code to make sure it makes sense, and much of the work is deleting the main bit of functionality it attempted to implement, and re-implementing it correctly.

However, having it autocomplete entire function definitions, including all the {} () => | : `${x.y}` fiddly bits, sure saves a lot of time.

The one point I don't agree with at all is `Dependency on Proprietary Tools` there are already plenty of open source alternatives, and these will only improve with time.
Fun fact: part of the reason that this article is on HN, I believe, is because I linked it to someone on another site as a means of explaining stacked diffs.

> It looks like they reinvented commits as dependent PRs.

Sort of kind of. It really depends on what you mean by PR: if we're talking about "review this branch please," which is what I would argue most mean by PRs, then yes, in the context of "stacked PRs for GitHub" it's largely about tooling that makes dependent PRs easier.

But there are other, non-GitHub tools. With those tools, you don't say "here's a branch, review it please," you say "here is a stack of commits, review them please." There's no branch going on inside. It's just a sequence of commits. This matters because it centers the commit as the unit of code review, not a branch. This also means that you can merge parts of the stack in at different times: to use the example from the article, once "small refactor" is good to go, it can be landed while "new API" is awaiting review. etc.

I think it takes actually using some of these tools to really "get it." I never understood them either, until I actually messed around with them. I am currently on my project solo, so I don't really stack at the moment, I think it really helps more the larger of a team you're working with is.
Should some people be able to drive recklessly just because they can afford to pay speeding tickets?
> I write detailed git commit messages like a maniac

I do not think that helps much, in the general case

> The problem with comments is that they also pertain to a revision that existed around the time they were written, but they stick around,

Comments do require maintenance. It is part of professional practice
I have it available, but GitBash seems to work better with my workflow. BTW, when I checked to see how to donate, apparently my client pays for it; I thought it was OOS.
A private enterprise can charge whatever they like; you aren’t forced to visit and buy - go to a competitor that doesn’t charge as much! Or take your own alternative supply.

This is not even remotely an example of “gouging”.

Try again?
There's no evidence of any of that, it's pure speculation. I bet people were saying the same thing about Intellisense, and Google, and documentation-on-hover, and live compiler errors, etc. etc.
This sounds like levels.fyi for companies? As long as they are selling aggregate data and not data specific to an individual (e.g. for determining an offer for a particular person) it seems reasonable.
7th grade shop class. We all held hands and teacher crank an old telephone generator
Trieve Secures $3.5M to Power AI Search and RAG
The analogy to calculators isn't particularly close. A calculator will help with the mechanics of arithmetic or even graphing but it won't help a student who doesn't understand when and why to multiply, add, or subtract. Copilot will generate working code (for some definition of "working") that the programmer might not understand at all.
I commented here: https://news.ycombinator.com/item?id=41514547, but tldr, its different code (a much more minimal implementation), and the PR isn't being prevented from merging, there is review that has feedback that hasn't been addressed yet. We have seen with other DB tables how when they grow significantly (and if you are logging every action this will happen) then performance is impacted. So there are suggestions on ways of addressing it in a way that wouldn't require manual intervention from users to resolve while waiting for additional PRs.
Carefully read through the points and tell me the author is wrong. Everything written is reasonable and logical.

At a basic level, which of these two practices are more likely to result in you retaining information and learning: reading, writing, and debugging your own code, or copy-pasting someone else’s?
jj (and sapling, in my understanding) uses git as a backend, so you can use it even if you're stuck with git. Not that I think git-branchless is bad, mind you, but just to be clear about it.
TypeScript: Don't be optional, be explicit
much easier just to use pg
Yes I was hopping for a scientific study.
Ubisoft Investors Are Done [video]
Many (most?) dealerships have a policy of not accepting more than a few thousand dollars on a credit card, they don't want to pay the fee
this article is just a rehashing of the same tired contrarian takes about AI-assisted coding that we've been hearing for years. 'Programmers will become lazy and reliant on AI' is not a new problem, and it's not like Copilot is somehow uniquely capable of eroding fundamental programming skills.

in reality, Copilot and other LLMs are just tools, and like any tool, they can be used well or poorly. If a programmer is relying on Copilot to do all their thinking for them, then yeah, they're probably not going to learn much. But if they're using it as a starting point to explore new ideas and learn from the code it generates, then that's a different story.

And let's not forget that AI-assisted coding is not a replacement for human judgment and critical thinking. If a programmer is not reviewing and understanding the code they're writing, then that's a problem with their workflow, not with the tool they're using.

I'd love to see some actual data on how Copilot is being used in the wild, rather than just anecdotal evidence and hand-wringing about the 'dangers' of AI-assisted coding. Until then, I'll remain skeptical of this article's claims.
I have an implant and MRIs or Xrays cause zero issues.
Milk Bar only ever worked when it was Christina Tosi's personal baking project. The second they tried to corporatize it, it was done.
Me too. For some reason, I have a soft spot for these displays, also eInk.

I've recently bought Hisense hibreak phone just because I am interested in these things.
1. I'm asking a question "Is this the new norm?" not drawing conclusions.

2. I'm asking it after 2 consecutive experiences with YC founders, after 15+ years of working in a software developer role in this city and having never been asked to work 7 days a week as baseline.
Given that you can use git with Gerrit, I am confident in placing the blame on GitHub here.
Cool to see new players entering this market. I'm hopeful for them. It's cool that they have a public roadmap and they seem to be talking to users and building something people want.
You have founders who are too young to be any sort of wise along with engineers who are too young to be any sort of wise. The two together will almost surely fail. This is why most startups are a waste of time and energy. It's the blind leading the blind over the edge of a cliff.
It's not even well thought-out speculation. It's basically "old man rants at clouds."

I'm pretty negative about the LLM hype, but this is just a low-effort, low-value "back in my day" rant.
> His critique is basically the same as 'calculators' will make us poorer at mathematics

Calculators did make us bad at arithmetic. It's just that people stopped caring.

I don't think this is bad, though, anything to avoid typing repetitive boilerplate, which is pretty miserable regardless of your skill level.
I usually just point the target branch of MR 2 to MR 1. After merging MR 1 GitLab automatically change it to the default branch so it's more or less okay.

However this makes updating these MRs very rebase heavy and as said in OP it is hostile to reviewers.
The article's title is "Why I Prefer Exceptions to Error Values". It literally tells you that it's biased.
Seems like stretched reasons. Similar things could be said about using libraries or languages that abstract away low level complexities. Also pretty sure it's AI generated article which I guess could be stronger point about writing skills being eroded than the arguments itself.
The reason it's not a useful comparison is that unnamed, nonspecific "employer who has quotas" is assuming that many employers have quotas. Who? How much? And did they eat my cat?
> our community has generated over 12B images

They say it came out March 2023, so 1M images per hour.

Very active, this community.
But it does. The same holds for Google and stackoverflow: the majority of developers have trouble with sql.since the introduction of or mappers and plenty of other examples. Ask a junior dev about the difference between a stack allocated and a heap allocated object and be amazed.
From TFA: "Erosion of Core Programming Skills, Over-Reliance on Auto-Generated Code, Reduced Learning Opportunities, Narrowed Creative Thinking, Dependency on Proprietary Tools, False Sense of Expertise"

Personally, I've been making the same arguments against using even vanilla auto-complete. It's a distraction, erosion of the mind, encourages bad habits, etc.
> Everything written is reasonable and logical

So was Ptolemy's model of the solar system.

That doesn't make it right or valuable.
I think this is a sound analysis, if rather depressing!

I really just can't see how this ever changes. You are right that the Dems and Republicans are two cheeks of the same arse - but worse, they don't even play fair within their own rules; just look at the shenanigans they've been undertaking to keep Jill Stein's Green party underfunded and off the ballot!
I think you're misunderstanding the author's point. They're not saying that AI-assisted coding is inherently bad, but rather that it can lead to a lack of understanding and retention of knowledge if used as a crutch.

The analogy you're making between reading, writing, and debugging your own code versus copy-pasting someone else's is a good one, but it's not a direct comparison to AI-assisted coding. When you copy-paste someone else's code, you're still reading and understanding the code, even if you're not writing it yourself. You're still learning from it, even if it's not through the process of writing it.

With AI-assisted coding, the issue is that the AI is generating code that you may not fully understand, and you're not necessarily learning from it in the same way. You're not reading and understanding the code, you're just accepting it as a solution. And that's where the problem lies.

It's not about whether AI-assisted coding is good or bad, it's about how it's being used. If you're using it as a tool to help you learn and understand the code, then that's one thing. But if you're using it as a crutch to avoid learning and understanding the code, then that's a problem.

So, to answer your question, I think it's more likely that copy-pasting someone else's code would result in you retaining information and learning, simply because you're still reading and understanding the code, even if you're not writing it yourself. But that's not the same as AI-assisted coding, where the AI is generating code that you may not fully understand.
Fining 1% of income is no less principled than fining a flat $1000.
Have you come across `git rebase --update-refs`? This automatically moves your "intermediate" branches during a rebase and sounds like it could be useful in your situation.
I get his point, but let's be real here: 10, 20 years from now, how many will actually be programming - the we know programming today?

In 10 years time, we will have a generation of coders where the majority have never coded anything without the help of some LLM. If that's even the thing, when that time comes.

Some posters here are living in some luddite delusion, if they think the "AI hype" will somehow just blow over, and people will go back to sifting through stack exchange, or simply read the man pages for something.

Sorry, that's just not going to happen. In the past two years we already have junior devs that are dependent on LLMs to work efficiently.

These posts remind me of how older folks (25-30 years ago) warned about search engines, and how they'd make the youngins lazy and uncritical.
This just means job security for me. We will be the next "Fortran/COBOL Cowboy's"
My experience with Uber/Taxi in Sweden. Got out of ferry, need to go to the airport, 40 minutes drive. There are a lot of taxies at the ferry terminal, sure, I talked to them, asked how much is to Airport, they all replied "by meter". Well I know you can set any rate to your meter. And all of them drove that route a lot of times, nobody gave me an estimate. So I have ordered Uber. Uber driver asked me how much Uber is going to charge me, and offered that he would cancel the ride, and I will pay him directly. I declined, just because I want to support Uber. I understand, that maybe some rides are not as beneficial as others, but give me a reasonable estimate, and I will agree to it.

But this behavior of taxi drivers that would rather do one drive in 2 hours instead of 2 rides, and they make approximately the same amount of money - that is what created Uber/Lyft. Passengers frustration with the taxis.

And I had bad experiences with Uber/Lyft and with Taxi. Cars can be filthy. But what I need: easy way to order a car, know exactly how much I am going to pay (estimate is fine with adjustment to changing traffic/time), what I don't want - not knowing if they will decide to charge me between 50-300 EUR/USD. That is not an estimate.
The people I know who prefer stacked diffs argue that it makes it easier to integrate changes faster, no matter the size. Part of this is because unlike a PR on GitHub, you can land parts of a stack: to use the example from the article, if the "small refactor" diff is good to go, it can be landed without landing the "new api" and "migrate API users" diffs. Centering commits rather than branches has the effect of making for smaller overall commits rather than long-lived branches.
The author may be right, or wrong, we don't know. It may look reasonable and logical, but it needs to come with data.
West's missile go-ahead to Ukraine would hold no shortage of risks
"Why C is making assembly programmers worse at programming"

"Its going to make you reliant on the [compiler], and you will never be able to do anything that the [compiler] cant already do."

LLMs are here to stay, even if they don't write perfect code -- they are clearly very useful to an increasing number of existing developers and, more importantly, bringing new developers into the art of software creation.
A sure sign of a really bad argument is when the protagonist uses “not dying” as a justification for horrible actions.

Particularly entertaining is when apologists for the British Empire justify starvation events in Ireland and India. Particularly in Ireland when one of the peak famine years was a year of record exports of meat and wheat. The British government was of course, helpless to do much - they were concerned about the moral hazard of handing out food to dying people.
If your premise is that the world is a better place when programmers all have regex syntax committed to memory, then sure, I guess AI tools are bad.

Personally, I don't think the aspects of writing code that AI tools help with the most are the important parts. I think AI tools are great at taking out the rote aspects and the glue code so that programmers can concentrate on the core issues and broader structure.
Forget the sources, but I recall people saying the same about syntax highlighting even.
Putting too much emphasis on na,Ed leads to looooong names

I've seen 64 character variable names

Names should be mnemonic. Reminding, not describing
I don't understand the purpose of the hyperbole (that I'm asumming it is). Is it simply that 'news' writers can't turn that off anymore or is there a point?

I certainly don't think this has much impact on anything. The best way to reduce piracy is to reduce the friction of watching what we want without all the multiplicity of exclusivity and bundled services.
NASA's Voyager Mission [video]
This article 100% read like it was written by AI.

I will personally never use Copilot, or any other AI code generation tool, for the simple reason that I enjoy writing code.

Even if I were unfamiliar with a new language, I'll still never use it. Instead, I'll consult the documentation and follow examples. I like coding, and I neither need nor want a machine to do it for me.

It's exactly the same as writing English. There is great pleasure to be found in writing, it's worth your time. Just be careful when doing so to not end up sounding exactly like ChatGPT.
> Yeah it's really difficult, but that doesn't mean you should just give up and take the average.

Presumably the rational approach would be mild skepticism about confidence, not specifically accepting or rejecting any claim. Which leaves this well within the grounds of "plausible".
Uber is not seen as synonymous to taxi, its seen as better; more convenient (one app for any city), less fraudulent, and more safe. Uber more readily kicks drivers off the platform (for better or for worse)
Pass. This article could have been published as "Why Internet Message Boards Are Making Programmers Worse at Programming" 30 years ago, "Why Google Is Making Programmers Worse at Programming" 20 years ago or "Why StackOverflow Is Making Programmers Worse at Programming" 10 years ago. Its the same-old-same-old. Has it been true in the past? Maybe, if your criteria for "good programmer" is "someone who went through the same struggle I did". But the industry grows and adapts. The next generation of programmers is going to be good at different things than we are. As long as they can get the same job done, who are we to say that they are wrong?
They were absolutely. I recall when Stack Overflow was the great evil. Luddites should get over it. We are moving forward. There is no putting the LLM back in the box, and even if there was a way to do that, it would be dumb.
A Great Fog over the Past
showdead is essential for Orange Reddit but it will show downvoted comments in unreadable light grey on light grey. So you probably want a user CSS (e.g., with Stylus) like this (italic and the particular color are to taste, of course):

.c5a, .c73, .c82, .c88, .c9c, .cae, .cbe, .cce, .cdd { color: #222; font-style: italic; }
Mistral releases Pixtral 12B, its first multimodal model
While this raises valid concerns, Copilot and friends can actually enhance learning by exposing devs to new patterns and approaches.
They still require problem-solving and critical evaluation skills. By handling routine tasks, they free up time for higher-level thinking.

It's just another abstraction layer, like high-level languages were. Responsible use combined with continuous learning can boost productivity without sacrificing knowledge.

The impact differs between experienced devs and beginners. As these tools evolve, we'll likely develop new meta-skills around AI collaboration. Like any tool, it's about how we use it.
If there's an existential threat to Russia, it's not military, and for the same reason. They have over 5,000 nuclear warheads too. Nobody is invading them. They know that. They are still showing off bigger, scarier missiles.

They won't go pay an exponentially higher price by invading a nuclear state, which, thanks to NATO, is what they'd be doing invading Poland. It's strange to think there's not a substantial difference between invading a non-NATO, non-nuclear state and one that is.
At this point you’re just making stuff up.

https://www.upwork.com/hire/laravel-developer/us/
His rice vinegar, which apparently is "restaurant tested" and has taken "years of research" to create the "vinegar of their dreams" is even worse in terms of pricing. But "you've never tasted anything like this before" as it comes from their "proprietary blend of rice".

Professional marketing copy like this costs money. When Chef Chang says "Buy it!" the only response is "YES CHEF!".
Roll back a bit.

It's the CEOs who enable and managers who want to micromanage that are wanting the return to the office. Threating to fire people if they don't comply.

That is, by definition, control.

Oh I agree wholeheartedly with your second paragraph.
That was a lesson learned in the 90s - people would show up to put in face time, but they weren't getting productive work done. It was all about politics and appearances, not good engineering.

My advice? Don't work for a startup without Eff-You money.

There's a reason they want young, inexperienced engineers - and it isn't because they know the "latest and greatest" tools and technologies.
I can't seem to find licensing info on the textures. Where can I use them legally?
"Once guests are finished with that, we bring out a soup made from the carcass."

Soup from the carcass is delicious, but there isn't time to do that during the meal. Even with a pressure cooker it's going to take at least an hour. (And if several tables order the same dish, you're gonna have a bunch of pressure cookers in your kitchen.)

So... the idea is sound, but I'm doubtful that they actually do it the way they claim. Which would make sense with the "hero chicken" story they admit to.
Sure! sqrt(-1) is actually (-1/12), as proved by Ramanujan summation.
Ultimately it's not worth it, which is why I left. Sucks though because I have to find another startup in town and hope it's not basically the same thing.
In essence, you are agreeing that this is the root cause, you just seem to believe it's unrealistic to fix it.

I actually think it's viable to fix, I am simply not sure if anyone would pay for it — basically, old LTS model from Linux distributions where a set of packages gets 5 or 10 years of guaranteed security updates (backported, maintaining backwards compatibility otherwise).

If one was to start a business of "give me a list of your FLOSS dependencies and I'll backport security fixes for you for X", what's X for you?