HN user

tdullien

1,079 karma
Posts24
Comments203
View on HN
thomasdullien.github.io 29d ago

Halvar's Guide to Entrepreneurship

tdullien
2pts0
addxorrol.blogspot.com 3mo ago

Safer vibecoding via old hacker habits

tdullien
1pts3
addxorrol.blogspot.com 7mo ago

Ask your LLM for receipts: What I learned teaching Claude C++ crash triage

tdullien
3pts0
tongyi-agent.github.io 8mo ago

Tongyi Deep Research – relatively lightweight hi-perf open-source model

tdullien
1pts0
addxorrol.blogspot.com 1y ago

Comparing PyTorch code optimization Gemini vs. Claude

tdullien
3pts0
www.zymtrace.com 1y ago

Distributed Continuous GPU Profiling

tdullien
12pts2
addxorrol.blogspot.com 1y ago

Polytopes and MLP Training Visualisation

tdullien
2pts0
docs.google.com 1y ago

Is this memory safety in the room with us?

tdullien
8pts1
addxorrol.blogspot.com 2y ago

Fast-takeoff AI Doom scenarios are implausible

tdullien
1pts0
addxorrol.blogspot.com 2y ago

Some geometric intuition for single-layer ReLU networks

tdullien
4pts2
addxorrol.blogspot.com 2y ago

The end of my Elastic/optimyze journey

tdullien
2pts0
www.elastic.co 3y ago

Importing 4B chess games using ES and Universal Profiling

tdullien
2pts0
www.elastic.co 3y ago

Unwind stacks in eBPF without frame pointers

tdullien
2pts0
addxorrol.blogspot.com 4y ago

The Missing (Datacenter) OS

tdullien
4pts2
prodfiler.com 4y ago

Speeding up an eBPF optimizer by 1.4-1.9x with a few easy tricks

tdullien
20pts0
prodfiler.com 4y ago

The mystery of Kubelet eating (too much) CPU and IOPS

tdullien
21pts0
prodfiler.com 4y ago

Show HN: Whole-fleet continuous profiler for C/C++/Rust/Go/JVM/Python/Ruby/PHP

tdullien
33pts3
wttr.in 5y ago

TIL: Curl Wttr.in

tdullien
2pts1
ieeexplore.ieee.org 8y ago

Weird machines, exploitability, and provable unexploitability

tdullien
30pts4
addxorrol.blogspot.com 9y ago

Process and flexibility in startups and larger organisations

tdullien
2pts0
www.ecfr.eu 10y ago

ECFR Policy Article “Creating European Digital Champions”

tdullien
1pts0
docs.google.com 10y ago

3 things that Rowhammer taught me (talk slides)

tdullien
1pts0
addxorrol.blogspot.com 11y ago

Why changes to Wassenaar make oppression and surveillance easier, not harder

tdullien
2pts0
lekkertech.net 12y ago

Akamai's "secure allocator" is broken and doesn't protect against heartbleed

tdullien
1pts0

I should add something about this, but if a market looks like a drunken bar fight, I'd probably not want to go there.

That said: A good market will become crowded quickly in either way.

Yeah.

Also - I use the term "coach" broadly here. Many people react very poorly to the term "therapist", and "coach" is a much broader term encompassing both therapy or just people that have significant experience in a field. Or just an older relative or acquaintance that is willing to provide regular advice/feedback.

There's definitely charlatanism, particularly when people advertise themselves as "business coach" or "startup coach".

I don't think you need 8 years to build a product people like, Prodfiler got good resonance and we built it in ~18 months, it would probably take 4 months now...

Yes. Usually, the VCs will want you to not take an extravagant salary, but a solid family with which you can keep your family comfortable. And that's normally the right bar.

And if there are liquidity pressures a few years into the process, and you have traction at Series B or C - don't hesitate to think about a small secondary.

You don't have a product until there's ~3 customers, with perspective to more. Before that you're essentially a consultant. I'll add that to the next version of the doc, too.

The point is: For anything you build, you can find 1 customer. It's only when there's multiple customers that like the product and want to improve it where you move from "consulting" or "custom development" to "product".

I will add a section. Pay yourself a salary at the very latest the moment you've raised funding. If a VC objects to you doing that, get a different VC. You're in for the long run, and support from your family etc. is important, and you're already taking on a huge risk by pooling all your risk in one company, vs. the VC who is happily diversified.

Investors who imply you shouldn't take a salary are no bueno.

Author here. I'd be curious what went wrong in your case? (Also, happy to soften that advice further if there's strong evidence that people find the advice detrimental).

That's a clever and intriguing idea. I have to think through the security implications a bit though - I don't actually know much about how git operates with regards to hooks etc.

I'd imagine you lose the ability to have the coding agent do the commits for you? E.g. if you just mount the code directory, then an agent running on the remote side can't commit anything, right?

So you'd have to mount the .git directory from the remote side to then push?

The old warez cracking scene had an outsize impact on computer security. GRSecurity, Heartbleed vulnerability, most reverse engineering tools for security, etc. etc. etc.

There's so much history here, touching on all sorts of insanity including selling 0-day to the US government that was then used to apprehend high-level Al-Qaida personnel, random warez busts leading to people taking oversea jobs, etc. etc. etc.

If anyone still has old .NFO archives from 1990-2000, I'd be very interested in getting as many as possible.

The privatization of the train system in Germany was a particularly insane disaster that is only now, 30 years later, being undone/repaired.

If you look at an org chart of the DB these days, the most fascinating part is that DB consists of almost 600 separate corporate entities that are all supposed to invoice each other.

Speaking with insiders, it appears that when the privatization happened, the new corporate structure took what was essentially every mid-size branch of the org chart and created a separate corporate entity, with cross-invoicing for what would normally normal intra-company cooperation. I think the (misguided) goal was to obtain some form of accountability inside a large organisation that had been state-funded and not good at internal accounting.

This fragmentation lead to insane inflexibility, as each of the 600 entities has a separate PnL and is loathe to do anything that doesn’t look good on their books.

Add to this a history of incompetent leadership (Mehdorn, who also ran AirBerlin into the ground, and who was also responsible for the disastrous BER airport build-out), repeated rounds of cost-cutting that prioritized “efficiency” over “resiliency of the network” etc. etc.

DB is currently undergoing a massive corporate restructuring to simplify the 600+ entity structure, but there has been a massive loss of expertise, underinvestment in infrastructure, poor IT (if you see a job ad for a Windows NT4 admin, it’s likely DB), etc. etc. — it’ll take a decade or more to dig the org out of the hole it is in.

There's been an ongoing issue with North Korean state agents infiltrating SV companies, and this proposal helps them pass the interview process more easily.

There's multipronged benefit for them: Access to company infrastructure to potentially cause harm or ransom in the future, access to technology / intelligence, but also simply foreign currency.

Xoogler here (2011-2018). It's heartwarming that a core part of Google culture ("for every problem we have 3 solutions: 2 that are deprecated and 1 that is experimental") is alive and well.

I only remember 2015 TF and I was wondering: why would I use Python to assemble a computational graph when what I really want is to write code and then differentiate through it?

So there's a long intellectual history behind these technologies, and Intel had multiple chances of taking the leadership on this around 2018 - they failed to do so, some of the talent went to Apple, and now Intel has to play catch-up.

I'm pretty certain it'll be the x86 variant of either MTE or MIE.

I don't know tbh, and I gave that talk when I was in terrible shape, so I'm not upset ;).

If people care a lot, I can record a YouTube video on the topic.

Every predictor is a compressor, every compressor is a predictor.

If you're interested in this, it's a good idea reading about the Hutter prize (https://en.wikipedia.org/wiki/Hutter_Prize) and going from there.

In general, lossless compression works by predicting the next (letter/token/frame) and then encoding the difference from the prediction in the data stream succinctly. The better you predict, the less you need to encode, the better you compress.

The flip side of this is that all fields of compression have a lot to gain from progress in AI.

Fair, there is a lot that is incomprehensible to all of us. I wouldn't call it "state" as it's fixed, but that is a rather subtle point.

That said, would you anthropomorphize a meteorological simulation just because it contains lots and lots of constants that you don't understand well?

I'm pretty sure that recurrent dynamical systems pretty quickly become universal computers, but we are treating those that generate human language differently from others, and I don't quite see the difference.

Author here. What's the difference, in your perception, between an LLM and a large-scale meteorological simulation, if there is any?

If you're willing to ascribe the possibility of consciousness to any complex-enough computation of a recurrence equation (and hence to something like ... "earth"), I'm willing to agree that under that definition LLMs might be conscious. :)