HN user

QuantumNoodle

604 karma
Posts2
Comments170
View on HN

Your TB stories made me recall my (fond) TB stories. I came from a country that requires tuberculosis vaccines as a school-entry requirement. I have the vaccine and antibodies. Then moved to a country that didn't have this requirement but I had to be tested to make sure I didn't have TB for things like camps, college, etc. The test is something like a vaccine that injects only dead TB cells, if the injection site welts up from anti-bodies then you had to get another whole panel of tests (like X-ray of lungs). Thankfully I've never had it but TB is apparently no joke. Though blasting my chest with radiation is no healthier :p

Anyway, thanks for sharing!

Good point. I've (even with agents) never made more than like 5 PRs in one day internal to a company and if I have they typically included accompanying proto or submodule changes. Heck give a factor of safety of 2x and cap at 10 daily PRs per account for repos that youre "untrusted"

I get a lot of nostalgia and initial interest in these types of phones. But I always talk myself out of it because, with self control, my current phone is just as good plus it's one I already have. Perhaps when my current phone loses support then I'll consider these alternatives. But for the price... Eek. Rather just buy a "real" flip phone that can give out a hotspot.

lmao excellent reference! While this is poking fun at the block chain hype a bit, a shocking amount of (good) software engs don't know good security practices. I'd be interested to hear arguments for and against being licensed to write software for particular applications (e.g J.Doe can work on this application but any auth code has to be signed off by someone licensed). AI tools are great but screwing up an implementation (for a well thought out spec) does happen, esp. in security applications and someone needs to be liable for life-ruining data breaches.

Given how many critical systems software touches these days, I am surprised that there they are not licensed. Imagine if civil engineers can just go building shit as minimum viable products? Sure prototype quickly but someone should be found liable for final product.

Do you have any resources on hardware necessary for running models and tweaks? I see you mention 2x 3090 and I wanted to do more search on what hardware is satisfactory for what models.

I am in no way supportive of monopolies though taking "the need to compete" out of the equation and having steady flow of money that won't be cut off if "someone beats you to market" was pretty revolutionary. Consider Bell Labs, staffed with real "nerds" that never had to prostitute themselves or to pitch an idea on the merits of making money -- they simply did stuff that was fun, in ther nerdy way. Because of this we have wireless communication, transistors, digital cameras sensors, c, and many others.

(There were a lot of negatives due to this AT&T monopoly but we are talking about nerds here and having to socialize your own worth/value. It's a shitty game that real nerds aren't necessary interested in playing)

Looks like he updated his "About me" section

At the moment, my main focus is [...] fighting against (governmental or corporate) mass surveillance

While he always had "Ethics in Computer Science” as an interest, I wonder what blinds people into accepting offers at Google -- the advertising company. I want to take his words as sincere, but Google has been privacy violating for longer than his tenure with android. Money and prestige is a hell of a drug I suppose. He could very well work for grapheneos but no money or immediate persteige there (sadly).

I've worked roles where our priorities shift with the wind. Many times it is for good reason, like a strategic customer to get a foothold in a market. Other times it is just because management hyped up some effort. All's this to say, nod saying you will do it then just go about your day doing focusing on the actual priorities. Don't let workload mount up bc deadlines are all made up.

This feels like a troll comment, but I'll bite.

Mathematics requires substantial creativity at every level. There is problem selection, conjecture formation, proof strategies, definitions, models, and explanations. Yes, it's constrained and guided by logic and rigor but having logic won't give you creativity.

Music is a human endeavor and musical recordings hurt musicians, bands, orchestras, etc. Especially those starting out.

The medium it is recorded on has no bearing on what composed the music. If people don't get rewarded for composing they won't. Same with mathematics. If people don't get paid for being creative they just won't be creative.

I am not saying I agree with everything in the article. OP of this thread just made a low effort comment that was addressed in lengths during the article.

Sorry did you read the article or just the headline? The theme is mathematics is a human-endevor and automation undermines that, particularly the ones starting out. It risks killing the culture entirely. Some other key points:

- AI-generated papers could overwhelm peer-review systems with low-quality work.

- It may become difficult to assign proper credit for discoveries.

- Researchers who choose not to use AI tools could be disadvantaged.

- There are ethical concerns about mathematical work being used to train AI for military and surveillance purposes.

Stack Overflow is receiving about 3,800 questions a month, which is what it was getting in 2008, before it had finished being launched.

Interesting, is SO getting traffic again? I thought it wasn't doing well? Or have they adapted?

The programming book was, when you look at it squarely, always a slightly absurd object. Printed text on bound paper, describing software that lived on screens, which the reader had to retype, by hand, into a screen of their own.

The point of programming books was never "give a man a fish" but "teach a man to fish." If you were not hands on, experimenting, and instead copy-pasting you likely didn't get anything out of the book anyway.

It's too early for me to have a firm opinion one way or another.

Just a data point: this month I had a knarly bug in generated bpf code. The C language was correct but the compiler produced a bug that corrupted packets. I spent around 8 hours debugging _where_ the issue is and how to work around, never really understanding what went wrong. That knowledge came with several more days on and off looking at it--after I had mitigated the production issue.

So if I extrapolate this experience to LLMs (who are not deterministic) and who will make larger systems. What we trade for velocity we will pay for with hours of debugging because we won't understand how things work. I think this is unavoidable.

Another way I'm looking at it: after some time of not writing code, it will be analogous to instructing the LLM and the output being assembly--where I simply don't have the muscle to grok the output. How do I mitigate that knowledge gap? I see micro serves coming back. Today it is easy to slop up disposable scripts. Our services need to be modular so we can dispose of broken things--so they are only coupled with each other by strict APIs.