HN user

jmatthews

335 karma

software/data engineer, python, golang, c#, java, c++, in that order. Domain expert with data: hygiene, acquisition, warehousing. Generalist.

Posts10
Comments160
View on HN
Do your own writing 4 months ago

I learned some of this the hard way. I did the thinking and the distillation, but I had AI write the prose and that's all a lot of people saw, the AI tell-tales.

it's not that you're teaching the AI, it's that you're framing the conversation on a reference material and having a conversation around it. Exploring a problem with referential framing, like a white paper or a dense blog post is a useful cognitive hack. You just have to be careful to pin extraordinary claims to extraordinary evidence.

I'll give a software example because I'm just better at it, but if you describe Trello and tell me to decompose it on a white board I start thinking in terms of queues and write|edit|save tuples. I don't have to invent queues in my head and I have to wonder if it is possible to proactively assign a series of tranforms or schedules on an fresh input.

I know how to do it and it's all internalized. Even if I've never needed to do it.

that's the toolbox I'm trying to develop in ML. For example. I've studies LSTM and implemented one. What I didn't know was if gating was turing complete and essentially unbound. I didn't know if gates could be arbitrarily complex. Importantly I had no idea how to translate "I need a switch here" to a gate, or if a switch was even possible given the need to be differentiable for backprop.

It's not a trick bud. The github page shows my user name and Claude. The content is intended to be read by an AI agent and explored through a text interface. That is explicit in the readme and the primer itself.

If you think you can generate this artifact with a prompt then show me. This was 2 days of exploration and research.

my apologies it wasn't up to your standards. In fairness to me, that line is exactly what my effort was. I wasn't trying to "learn ML" I am trying to build a mental model that let's me decompose real problem into ML primitives.

It's unclear to me if you think the resource has no value or if it bother you that I wrote it using a coding agent.

I wrote the syllabus and worked through each section. Where my understanding was weak I explored the space, pulled in research, referred the model to other sources, and just generally tried to ground the topic in something I understood.

What resulted was something that helped a lot of subjects click together for me. Especially when to reach for a particular activation function and the section on gating.

This enter survey was motivated by an ML expirent I ran with assosicative memories that just failed horribly. So rather than post mortem that I set about understanding why it failed.

Anyhow, thank you for the feedback. I submitted this in good faith that it may help others.

I've bounced off of many good textbooks. Even Karpathy's YouTube series was too dense for me. I'm trying to come in at a more palatable level.

This was a two day exploration where I provided the syllabus and ran through it with Claude Code, asking questions, trying to anchor it to stuff I understand well. I feel like the artifact has value.

I'm just trying to develop the lens where I can see a problem and know what properties of it are meaningful from an ML standpoint.

Coming from a specific domain where I have a sharpened instinct for how things are haven't really given me the ability to decompose the problem using ML primitives. That's what I'm working on.

This is my weekend project. I am building up my pattern recognition in machine learning. By that I mean see X problem, instantly think of Y solution. The primer markdown file is the artifact of that exploration.

read it from top to bottom or better have your favorite language model read it and then explore the space with a strong guided syllabus.

For me getting the AI harness to solve the puzzle has become the puzzle. Just one more level of abstraction. Just like I don't code in assembly language anymore, now I don't name every variable.

AI coding is just a non-deterministic programming language and compiler duo

You essentially outline why it should be broken up.

I'm not convinced making the ad tech sector more competitive would prompt that outcome but, "It would disrupt mature products" isn't a compelling argument to allow the existence of a monopoly.

Google is a monopoly, they exert monopoly power and enjoy monopoly pricing.

I think the more likely outcome would be more dynamic products under smaller bannerheads.

I would like to post this respectfully, just for posterity. The anti science insular concepts being assumed as fact, the discredited overpopulation theories, the sky is falling parts of climate change.

I can't credibly participate because from my perspective what is being discussed is a popular sci-fi series that I haven't read. The dogmas and rituals are alien to me.

It is insane how tone deaf most of the comments are, jarring even. I forget how insular so much of the community is and I often make the mistake of equating intelligence, which exists here in spades, with critical thought.

Understand that most of the sentiment expressed here is identical to the pre-digested mass media pablum intended for 100 IQ consumers.

Think of mass media coverage of a subject you're an expert in and how horrifyingly wrong it typically is on so many levels, and try to rectify the two.

I've read the couple of critical responses but on merit, the message is true. Anecdotally, my wife takes hundreds of photos every month that essentially no one will ever see again.

Android has a memories feature that serves them back up to us on occasion. This is a pattern writ large for huge swaths of data.

Differences in governance or allowable access leads to mass duplication and data rot on anything remotely dynamic.

I was that kid, now I have 3 sons and I am homeschooling my oldest because he is similar. The hack is essentially to praise the work, not the outcome. On some level you have to be unfair to your kid to be fair with him.

You can't take this as authoritative but my business has a data relationship with Toyota and they have a ton of juicy telemetry data.

Their attorneys are mad protective of the PII they have. Our relationship serves the public interest. We use the data to find people with open recalls where Toyota doesn't know who the current owner is.

I say this to say that we have other OEM relationships that are far more liberal with their encumbered data. This far Toyota seems to be playing it very straight.

The creation of the steam turbine is also fascinating.

It's a testament to engineering that hot air engines are remotely competitive when so many of the physics line up for steam.(phase change, heat capacity, heat conductivity)

The limiting factor as always is heat transfer between the heat source and the medium. If we had better heat exchangers, the theoretical maximum of steam is still the best.

I like to make an appearance in threads in this domain and just say, yeah, it's not just possible but "fun" to put the puzzle pieces together.

It is a very tough problem to solve. Especially when you consider the richness of the datasets you use to put the pieces together.

In my experience the only effective means is to poison the data, in addition to the common sense steps mentioned here.

Poisoning a dataset means seeding a wide variety of the datasets you use to discover PII with fictional look alikes that resist debunking.

Additionally you can poison the core set if you are very clever about it.