Live data from Hacker News

Solving the Jane Street reverse engineering challenge

jestoph.com

91–100 of 100 posts

Re: Solving the Jane Street reverse engineering challenge

#91

I wonder how far a LLM could get with this. It will be cool when we get to the point where you can decap a chip, take a picture, and then an LLM can create an emulator for that chip.

I tried and ChatGPT 5.6 managed to figure out the answer within an hour.

Re: Solving the Jane Street reverse engineering challenge

#93
post #4

> Well I don’t really know what to work on next Let me help you: work on figuring out how to spend the millions of dollars every year Jane Street will pay you to clock in. I've heard private aviation is expensive, for example. :)

> Let me help you: work on figuring out how to spend the millions of dollars every year Jane Street will pay you to clock in.

Does Jane Street really pay that much? Of course 7 figures is possible, but these median comps seem lower than FAANG (and with much higher workload): https://www.levels.fyi/companies/jane-street/salaries/softwa...

Re: Solving the Jane Street reverse engineering challenge

#94
post #22
post #13

Earlier quoted context omitted.

> It turns out that this ‘sky130’ thing is like a … standard? Or something for making chips. Very cool seeing someone completely naive going into this :) If you want to read more about a bit more... cheaty way to do this, I have written about using formal verification machinery to straight up force the solution out of the netlist here: https://atx.name/electronics/asic-re/ . Could be a bit of an infohazard, but I thi…

I'll definitely be reading this thankyou! I think this would have been a much better way to approach it, it's a bit of a joke in the piece that I always do things the hard way, but it's a genuine mystery to me why I operate this way. I should add I have an EE degree (but have never worked as an EE), so even though I don't know industry standards like this sky130 thing, it's not completely foreign to me.

Are you me? EE, always manage to go the hard route (inadvertently)…

Re: Solving the Jane Street reverse engineering challenge

#95
post #50

There's a typo on your link to the two stars image. It should be `/img/two-stars.png` instead it's right now `/img/two-starts.pgn`. For those interested in the image itself: https://jestoph.com/img/two-stars.png

Oh no! Thanks for that, I must have read it 10 times before posting but somehow didn't spot that it was wrong

Re: Solving the Jane Street reverse engineering challenge

#96
post #48

Weren't you supposed to wait until the submissions close to publish spoilers? (Or did they close yesterday?)

I emailed them and asked as I'm in Sydney and didn't want to mess it up - they said to wait until the end of my workday, so I posted it at roughly 5:30 my time. I hope I didn't spoil it!

Re: Solving the Jane Street reverse engineering challenge

#97

I also look at it and got the same result as well, but I did not submit it. I also figured out the purpose of the circuit: it is a 11x11 Star Battle checker (2 stars per row/column/region, no touching)

That is incredible! I've never heard of a Star Battle checker, but that explains the output! Another commenter pointed out there was also some morse code in the layout

Re: Solving the Jane Street reverse engineering challenge

#99

> I ended up using a tool called ‘z3’. It’s kind of magical? Every time it finds a solution I get a surge of joy. This resonates so much. I had a similar feeling after going to my very first operations research lecture. Solving seemingly incomprehensibly complex problems by framing them as a bunch of simple constraints and getting a solution seemed like such magic.

z3 or constraint programming comes in very handy in at least one challenge every year in Advent of Code! https://adventofcode.com

Re: Solving the Jane Street reverse engineering challenge

#100
post #96
post #48

Weren't you supposed to wait until the submissions close to publish spoilers? (Or did they close yesterday?)

I emailed them and asked as I'm in Sydney and didn't want to mess it up - they said to wait until the end of my workday, so I posted it at roughly 5:30 my time. I hope I didn't spoil it!

Their logistics were a bit weird: they asked not to post spoilers, but also ask you to link to your write-up.

In any case, I had it all worked out already. But looking at other people's submissions today showed me that I found some easter eggs other hadn't. That was encouraging. (And I missed some that others found, of course.)

Post reply on HN