Last week-end I was exploring the current possibilities of automated Ghidra analysis with Codex. My first attempt derailed quickly, but after giving it the pyghidra documentation, it reliably wrote Python scripts that would alter data types etc. exactly how I wanted, but based on fixed rules.
My next goal would be to incorporate LLM decisions into the process, e.g. let the LLM come up with a guess at a meaningful function name to make it easier to read, stuff like that. I made a skill for this functionality and let Codex plough through in agentic mode. I stopped it after a while as I was not sure what it was doing, and I didn't have more time to work on it since. I would need to do some sanity checks on the ones it has already renamed.
Would be curious what workflows others have already devised? Is MCP the way to go?
Is there a place where people discuss these things?
I've been wondering the same. Apparently, where I live (HCOL) people don't care about ever paying off the full amount, as long as the monthly installment is low. Regulations only require that you paid off 33% of the house value after 15 years.
You do need to start at 20% capitalization though, which at current prices means they need to own assets already (market risk), or have bonkers amounts of currency sitting around (inflation risk). I understand the FOMO some people must have.
I wonder if ultimately there is a cascade happening, where increased valuations lead previous owners to either take new mortgages, or sell their old house, and pay more for a new one. Which creates a cycle of ever increasing prices? I've never read anything though whether such an effect exists.
When I read stories like this about cool technology from the past that people can still enjoy today, I think it's a pity that the source code is locked away and lost as people and companies move on to new things.
IMO, there should be some kind of archive that conserves and publishes them after some time has passed, so that they could be ported to new hardware and kept accessible. and somehow documented for future historians.
> What neuromorphic hardware can I buy to run your code/ the SNN?
Current neuromorphic hardware is not easily accesible, but you can simulate spiking neural networks. Check out, e.g. https://brian2.readthedocs.io/en/stable/ or Nengo.ai
Empirically, you could have bought a share of the SPX at any point in time, and sold it with profit later. The real problem is what happened in the time between, and whether you were able to hold on.
Nice reminder of some general principles. I wonder how well it applies to young scientists given today's academic career prospects, though.
> If you want to make progress in any area, you need to be willing to give up your best ideas from time to time. [...] Medawar notes that he twice spent two whole years trying to corroborate groundless hypotheses.
Unfortunately, being willing to scrap your idea is only one part of the equation. Securing funding after 2 "failed" post-docs is an entirely different matter.
In this context, the dimensions are the degrees of freedom that a particle can move in. I think it becomes meaningful when you consider the metric (ie. definition of distances) and the laws of nature inside that space, and if additional dimensions help in formulating more phenomena with a less complex system of equations.
-> Classically, there are 3 spatial dimensions (directions of movement) with Euclidean metric, and all the classical laws (Newton's laws, gravity, etc.). Quite successful, but breaking down in extreme cases (high energy, ie. velocity/mass/etc). +there is a whole range of seemingly unrelated laws necessary.
-> with relativity theory (both special and general), time becomes a 4th dimension, but it has a special status in the metric (opposed sign), making spacetime non-Euclidean. One effect of this is suddenly you don't need a law of gravity anymore. Things just follow geodesics in this space. It also explains some effects that could not be derived from classical gravity. Essentially explaining more phenomena with less "overhead", in exchange for more dimensions.
Yes, that's what I meant. Perhaps it's related to the way the printing company produced the books, so this might not be an issue with other companies.
My memory is a bit fuzzy about the details, maybe it was about the inner margins of left-hand side and right-hand side changing. Maybe someone else recognises what I mean? :)
Since Latex is very powerful, I'm sure there is a way to code that behaviour in. But I had spent too many hours already on that project and I was happy with the result anyway, so I stopped investigating.
Having your own book in your hands feels awesome. I've done the same, but not with KDP. Unfortunately, I can't publish it as I had to give up my rights to it (screw you OUP/publishing requirements!).
On the technical side, it wasn't so straightforward to me to get a good result. In my case, I had to iterate a few times and order a new copy with adjustments to margins, etc. until it looked right.
One issue I didn't manage to solve back then was that the inner margin needs to slightly increase towards the end of the book. That's because the binding is eating up visual space since you can't open the book flat without destroying it. Professional publishing tools do this automatically, but Latex doesn't have an option for it. At least that's how I remember the issue. But maybe things have changed?
It's funny, but I feel in the opposite position. To me, computers had become associated with work-only, so much that I needed a change. I decided to assemble a new machine for fun coding and maybe some games (though I probably won't really have much time for it). starting up the new Flight Sim feels great and gives me a different perspective, after staring at a screen of e-mails and calendar and presentation slides for hours.
Last week-end I was exploring the current possibilities of automated Ghidra analysis with Codex. My first attempt derailed quickly, but after giving it the pyghidra documentation, it reliably wrote Python scripts that would alter data types etc. exactly how I wanted, but based on fixed rules.
My next goal would be to incorporate LLM decisions into the process, e.g. let the LLM come up with a guess at a meaningful function name to make it easier to read, stuff like that. I made a skill for this functionality and let Codex plough through in agentic mode. I stopped it after a while as I was not sure what it was doing, and I didn't have more time to work on it since. I would need to do some sanity checks on the ones it has already renamed.
Would be curious what workflows others have already devised? Is MCP the way to go?
Is there a place where people discuss these things?