For the best experience on desktop, install the Chrome extension to track your reading on news.ycombinator.com
Hacker Newsnew | past | comments | ask | show | jobs | submit | history | cvwright's commentsregister

The best early example of this is that Anthropic is already eating the lunch of all the new “AI security audit” companies. And they were only a few years old.

Those guys certainly thought they were being novel and creative, using AI to disrupt an expensive and labor intensive business model. But now with Claude Security, their own market share is going to be gobbled up before they can even get established.


Unfortunately even in the old days, a truly good programming book like you’re describing was depressingly rare.

Younger me really enjoyed some of the game programming books by Andre Lamothe.

Most “Learn Language X” books were terrible with over focus on syntax and very little thought into organization.


Apparently the guy who wrote the Camel book on Perl made less than $1000 from that book. I was shocked when I heard about that because back in the day when I was learning that book was incredibly popular and seemed to be everywhere.

EDIT: Edited, not wrote. My bad. That's a crucial distinction. Also, I meant the Llama book, not the Camel book.


That’s not true. I wrote the Panther book, Advanced Perl Programming, and easily made way more than 100k. Of the 25-30 or so dollars the books cost, I got 10% per copy, or $2 after taxes. The first print run of 35000 sold within the first three weeks.

The Camel book was already a huge bestseller, and was one of the anchor books of the early OReilly series. It made Larry a pretty penny


The 4th edition authors included brian d foy, who said "I think Tom [Christiansen] and I worked for about two years to produce the current edition. I certainly wouldn't want to spend that much time again to make less than $1,000... It's a huge effort from the editors and proofreaders and the book won't sell enough to make back the effort they put into it." https://www.reddit.com/r/perl/comments/1ns5r9n/comment/ngmvt...

I wasn't aware of this.

The first edition came out in 1991. The 4th ed came out in 2012, by which time Perl was no longer the duct tape of the internet. Perl 6 had muddied the waters, and Ruby and Rails had peaked.

Still, 1000 is painfully low, esp. for a high quality product.


Yes, you're right. That is the comment I was referring to.

If only Amiga assembler books hit those type of numbers.

Do you suggest any such books?

These are good ...

"Python for Data Analysis" by McKinney (2018)

"The Go Programming Language" by Donovan and Kernighan (2016)

"Hacker's Delight" by Warren (2013)

"Algorithm Design Manual" by Skiena (2008)

"Purely Functional Data Structures" by Okasaki (1998)

"Structure and Interpretation of Computer Programs" by Abelson and Sussman (1985)


> Unfortunately even in the old days, a truly good programming book like you’re describing was depressingly rare.

And when you got past the beginner stuff, non existent.

I've randomly tried to improve my $LANGUAGE_I_ALREADY_SHIPPED_SOMETHING_IN knowledge across the years, but if you look at books there's a plateau, and it's not too high.

With the internet, there are random posts here and there with pieces of info that will help you improve yourself. But no books.


You’re better off learning foundational knowledge. Languages are notations, not intent. What has been useful for me are Computation theory, Algorithms, Concurrency, Distributed Systems, Operating Systems theory, Practical system administration, Computer Organization, Networking,…

I do get language books, but only as a reference. For anything more advance, I usually read the sources.


You’d think someone would write about the tricks you learn breaking your teeth on the language though.

And they do, in random forum and blog posts though.


Agreed, Books on specific programming language were indeed tricky.

I found books on architecture, systems, or patterns, were more available. E.g. On relational database optimization principles, or Unix system administration, or graphics algorithms and rendering math, etc :)


LLMs are bringing us back to all the “proper” software engineering stuff that we’ve always known we should be doing, but until now we never had enough time/people/money to do it right.

Brainstorming and research before writing a design.

Writing a design or spec before writing the code.

Comprehensive unit tests.

Etc etc etc.

Like you, I get vastly better output from the tool when I create a detailed spec in markdown before I let it start coding. And bonus, the LLM is pretty good at helping with the spec too.


I’ve found the opposite. It’s making people lazy. We used to plan stuff and now it’s just dump this LLM created spec to an LLM and ship the code.

Yes that too but performing detailed planning is a minority viewpoint from what I've seen till now. Many Devs jump straight to code after briefly skimming the jira record.

yep and a side effect it is bringing back waterfall.

You’re arguing that we have too many PhD students in CS, not too few.

I agree with you fwiw.


A research professor typically graduates dozens of PhD students. Perhaps there was a post-war bootstrapping period where every one of those students got a tenured position somewhere, and in turn also trained dozens of PhD students; but it's pretty obvious it's not realistic to expect this to continue indefinitely. We're way past saturation right now. Certainly very few are going to get their own tenured positions, and as for the rest, it depends on the winds of funding availability in industry.


re: incentives, my proposal was always to let schools pay their football and basketball players, but require that grad research assistants are paid the same.


Football and other sports are marketing and their wages should be paid for by that department. Along with proof the marketing return on investment is there.

Grad students should be paid for their work as well.


I worked a ton in grad school, and it definitely sucked at the time.

But it’s crazy to complain about getting paid to go to school. A grad stipend is there to minimally support you so you don’t have to get another job and can focus on your research. It’s not supposed to be a career!


It’s not crazy… the wages are below food prep. What would be crazy is paying to help someone else’s career. That’s why a well known rule of thumb for graduate program evaluation is whether or not they pay their grad students.

If they pay their grad students, then at least the time the grad students spend creates enough value to offset the cost of paying them.

If not, stay far away from the program.

Also, regarding the career comment: If graduate school is not at least the first step in a given career (it should the second, undergrad being the first), how/why do you expect gifted intellectuals to spend their prime wage earning years doing it?

Most people do not have access to enough wealth to spend prime wage earning years toiling to help someone else’s career with no return on investment.


I was working retail in Eugene, Oregon during the 2014 University of Oregon grad student strike. I had a little bit of a chip on my shoulder because I was working retail with a master's degree in physics (because I did not have the endurance to complete a PhD, but had not yet accepted that fact).

My then-partner was part of the strike. One of the strike demands was higher wages as teaching assistants. And while I worked 40 hours a week, for $11/hr, I made considerably more and worked fewer hours than her. She put in probably 30 hours a week just on her teaching load, plus an additional 30 hours split between explicit course work and dissertation work.

It's crazy that a job that requires excellent marks while completing a 4-year degree pays worse, has worse working conditions, and is considerably more competitive to get into than a job selling office supplies.

One of the other things the grad students were demanding (which they only sort of got) was paid parental leave, because they did not fail to notice that most of their professors were in their late 30s or early 40s before they could afford to stop work long enough to start a family. It was very rare for two academics to have children together, because of the heinous, career ending financial cost to having children when you were young enough that their high school graduation date was before your expected mortality.


It would be crazy if the university were getting nothing out of it, but your work as a PhD student benefits not only you but the university as a whole. I think it would be reasonable to give students a living wage. I don't think anyone is expecting to make 100k.


I think the key difference is that: "going to school", sure you need a living stipend, but the actual research phase has serious WLB and working condition issues


Even that press release never claimed that Mythos was better than Opus at finding bugs.

They claim the huge advance is in exploiting the bugs.


The word “exploit” may be doing a lot of work here. In my experience Opus 4.6 is perfectly happy to provide test cases that trigger ASAN, even without the super secret squirrel security access.

But if you ask it to get you a shell it’ll probably tell you to get lost.


It’s been said that the British executed about 1% of their population each year for a few hundred years, and that a similar number died in prison.

The claim is that this made Britain a much safer country in later centuries.


One would be trading a chance of being murdered by psychopaths on the street for a chance of being murdered by psychopaths in the government.


New section, like pre-crime but for history. Pre-history.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search:

HN For You