HN user

barishnamazov

901 karma

barish.me

Posts29
Comments103
View on HN
atelier.barish.me 2mo ago

The Spreadsheet Was the Constitution

barishnamazov
1pts0
github.com 2mo ago

Show HN: Interpretable AutoResearch – Legible Agent Workflows

barishnamazov
4pts0
fab.cba.mit.edu 2mo ago

The Fab Charter

barishnamazov
2pts0
github.com 3mo ago

Git Blame: From Passive-Aggressive Forensics to Active-Aggressive Emails [pdf]

barishnamazov
3pts0
publicsuffix.org 4mo ago

The Public Suffix List

barishnamazov
2pts1
epistle.barish.me 4mo ago

Show HN: Epistle – Encrypted letters shared via URL, no server storage

barishnamazov
2pts0
barish.me 4mo ago

AI Chatbots Still Can't Render Code Properly (and How to Fix It)

barishnamazov
4pts0
www.turing.ac.uk 5mo ago

The Turing Lectures

barishnamazov
1pts0
www.bloomberg.com 5mo ago

Dating apps are training us to want the wrong people

barishnamazov
5pts2
thesquareplanet.com 5mo ago

Smashing the Stack in the 21st Century

barishnamazov
2pts0
css.csail.mit.edu 6mo ago

Computer Systems Security 6.566 / Spring 2024

barishnamazov
123pts17
techcrunch.com 6mo ago

Non-developers are writing apps instead of buying them

barishnamazov
5pts4
eightiesclock.mit.edu 6mo ago

Build a Digital Clock from the 1980's

barishnamazov
4pts1
dl.acm.org 6mo ago

Programming pearls: a sample of brilliance (1987) [pdf]

barishnamazov
2pts0
web.cs.ucdavis.edu 6mo ago

On Being a Human Being in the Time of Collapse (2022) [pdf]

barishnamazov
169pts161
www.reuters.com 6mo ago

US to suspend immigrant visa processing for 75 nations, State Department says

barishnamazov
152pts113
arstechnica.com 6mo ago

Google removes AI health summaries

barishnamazov
226pts175
www.reuters.com 6mo ago

How cybercriminals plot to rob a target within a week

barishnamazov
2pts0
techcrunch.com 6mo ago

Founder of spyware maker pleads guilty

barishnamazov
6pts0
en.wikipedia.org 6mo ago

Hash Array Mapped Trie

barishnamazov
2pts0
www.reuters.com 6mo ago

Horrible fire at the Swiss ski resort bar

barishnamazov
2pts3
reutersinstitute.politics.ox.ac.uk 6mo ago

Journalism, media, and technology trends and predictions 2025

barishnamazov
4pts0
techcrunch.com 6mo ago

OpenAI bets big on audio as Silicon Valley declares war on screens

barishnamazov
8pts3
www.tomshardware.com 6mo ago

Arpanet standardized TCP/IP on this day in 1983

barishnamazov
46pts1
github.com 6mo ago

Next.js makes many tiny serverless requests for all visible links

barishnamazov
2pts1
barish.me 9mo ago

Stop Searching with Your Eyes

barishnamazov
2pts1
github.com 9mo ago

Wellness Ping

barishnamazov
4pts1
barish.me 9mo ago

Mathematical Patterns in Phone Numbers

barishnamazov
1pts1
barish.me 10mo ago

Permanently On-Call

barishnamazov
3pts0
[dead] 1 month ago

Why is this 404 page shared by a fresh account getting upvotes? Might as well be a social experiment...

What matters less is the mechanical knowledge of how to express the solution in code. The LLM generates code, not understanding.

I think it's the opposite -- if you have a good way to design your software (e.g., conceptual and modular), LLM will generate the understanding as well. Design does not only mean code architecture, it also means how you express the concepts in it to a user. If software isn't really understood by humans, I doubt LLMs will be able to generate working code for it anyway, so we get a design problem to solve.

I'd personally rethink about applying some advice in that section. Here's my take.

Time-boxing AI sessions.

Unless you are a full-time vibe coder, you already wouldn't be using AI all the time. But time boxing it feels artificial, if it's able to make good and real progress (not unmaintainable slop).

Separating AI time from thinking time.

My usage of AI involves doing a lot of thinking, either collaboratively within a chat, or by myself while it's doing some agentic loop.

Accepting 70% from AI.

This is a confusing statement. 70% what? What does 70% usable even mean? If it means around 70% of features work and other 30% is broken, perhaps AI shouldn't be used for those 30% in the first place.

Being strategic about the hype cycle.

Hype cycles have always been a thing. It's good for mind in general to avoid them.

Logging where AI helps and where it doesn't.

I do most of this logging in my agent md files instead of a separate log. Also after a bit my memory picks it up really quickly what AI can do and what it can't. I assume this is a natural process for many fellow engineers.

Not reviewing everything AI produces.

If you are shipping in an insane speed, this is just an expected outcome, not an advice you can follow.

This write-up has good ideas but gives me the "AI-generated reading fatigue." Things that can cleanly be expressed in 1-2 sentences are whole paragraphs, often with examples that seem unnecessary or unrealistic. There are also some wrong claims like below:

The Hacker News front page alone is enough to give you whiplash. One day it's "Show HN: Autonomous Research Swarm" and the next it's "Ask HN: How will AI swarms coordinate?" Nobody knows. Everyone's building anyway.

These posts got less than 5 upvotes, they didn't make it to home page. And while overall quality of Show HN might have dropped, HN homepage is still quite sane.

The topic is also not something "nobody talks about," it's being discussed even before agentic tools became available: https://hn.algolia.com/?q=AI+fatigue

I foolishly sat in 8.821 [0] while at MIT thinking I could make sense out of quantum gravity. Most of the math went over my head, but the way I understand this paper, it’s basically a cosmic engineering fix for a geometry problem. Please correct me if necessary.

String theory usually prefers universes that want to crunch inwards (Anti-de Sitter space). Our universe, however, is accelerating outwards (Dark Energy).

To fix this, the authors are essentially creating a force balance. They have magnetic flux pushing the universe's extra dimensions outward (like inflating a tire), and they use the Casimir effect (quantum vacuum pressure) to pull them back inward.

When you balance those two opposing pressures, you get a stable system with a tiny bit of leftover energy. That "leftover" is the Dark Energy we observe.

You start with 11 dimensions (M-theory) and roll up 6 of them to get this 5D model. It sounds abstract, but for my engineer brain, it's helpful to think of that extra 5th dimension not as a "place" you can visit, but as a hidden control loop. The forces fighting it out inside that 5th dimension are what generate the energy potential we perceive as Dark Energy in our 4D world. The authors stop at 5D here, but getting that control loop stable is the hardest part

The big observatiom here is that this balance isn't static -- it suggests Dark Energy gets weaker over time ("quintessence"). If the recent DESI data holds up, this specific string theory solution might actually fit the observational curve better than the standard model.

[0] https://ocw.mit.edu/courses/8-821-string-theory-and-holograp...

Ah, you meant I overestimate the quality of people, not underestimate. I think that really depends. I have worked with some amazing people :-)

Low quality engineering is always visible to outside. Low quality engineers using LLMs won't get any better.

You clearly underestimate the quality of people I have seen and worked with.

I'm not sure what you're referring to. I didn't say anything about capabilities of people. If anything, I defend people :-)

And yes guard rails can be added easily.

Do you mean models can be prevented to do dumb things? I'm not too sure about that, unless a strict software architecture is engineered by humans where LLMs simply write code and implement features. Not everything is web development where we can simply lock filesystems and prod database changes. Software is very complex across the industry.

I'm a believer that LLMs will keep getting better. But even today (which might or might not be "sufficient" training) they can easily run `rm -rf ~`.

Not that humans can't make these mistakes (in fact, I have nuked my home directory myself before), but I don't think it's a specific problem some guardrails can solve currently. I'm looking for innovations (either model-wise or engineering-wise) that'd do better than letting an agent run code until a goal is seemingly achieved.

The turkey is fed by the farmer every morning at 9 AM.

Day 1: Fed. (Inductive confidence rises)

Day 100: Fed. (Inductive confidence is near 100%)

Day 250: The farmer comes at 9 AM... and cuts its throat. Happy thanksgiving.

The Turkey was an LLM. It predicted the future based entirely on the distribution of the past. It had no "understanding" of the purpose of the farmer.

This is why Meyer's "American/Inductive" view is dangerous for critical software. An LLM coding agent is the Inductive Turkey example. It writes perfect code for 1000 days because the tasks match the training data. On Day 1001, you ask for something slightly out of distribution, and it confidently deletes your production database because it added a piece of code that cleans your tables.

Humans are inductive machines, for the most part, too. The difference is that, fortunately, fine-tuning them is extremely easy.

I assume this is satire, but that aside -- many of my friends who entered into big tech as new grads with "unlimited pto" are indeed very hesitant to take it. They are worried that it'd affect how their managers see them. The same idea with showing up before your manager and leaving after they leave.

I was hoping to see some discussion about how to relieve the pressure in my back. Damn AI terms these days.

FYI, back raises have been really helpful.

Calling a Polymarket dashboard a "Bloomberg Terminal" is doing a lot of heavy lifting here.

The value of a Bloomberg Terminal isn't the UI (which is famously terrible/efficient); it's the latency, the hardware, the proprietary data feeds, the chat network, and the reliability.

Building a React frontend that fetches some JSON from an API in 2 hours is impressive, sure, but it’s not the hard part of fintech. We need to stop conflating "I built a UI that looks like X" with "I rebuilt the business value of X."

"I wrote 0 lines of code. I reviewed 0 lines of code."

This is the part that terrifies me. Generating code has never been the bottleneck; understanding it has. If you aren't reviewing the code, you are effectively introducing a black box into your stack that you are responsible for but do not understand.

While on point, I like the patterns Effect is introducing, but I have already been using them pre- and post-AI for a long time now (especially in TypeScript). It's not an innovation. We shouldn't be surprised when LLMs are better at working on robust code bases with modular design.