84 karma · joined August 8, 2024
Every time you see a macroscopic phenomena, you are looking at a stupidly high amount of quantum levels with very similar energies.
/s
Just learned the stack operations and trying to get used to them, but I have some bigger projects in my personal backlog.
I don't know anything about the cube world as I'm just a noob in this.
As an alternative, just create a new branch! `git branch savepoint-pre-rebase`. That's all. This is extremely cheap (just copy a reference to a commit) and you are free to play all you want.
You are a little more paranoid? `git switch -c test-rebase` and work over the new branch.
Sometimes it's ok to work like this, but you asking git not being judgamental is like saying your roomba should accomodate to you didin't asking you to empty it's dust bag.
I have to touch some of the most unnerving modules in a legacy project and everything is a trap. Lot's of similar repeated code with ugly patterns and some big brain trying to hide the ugliness with layers and layers of indirections and inheritance, and calling it clean because there is a factory class. The biggest joke? each implementation have a different interface for key methods, so later you to check what instance got created.
I want to keel myself. Anyone could assist me in a seppuku?
https://github.com/ading2210/linuxpdf
/s
- ¿could we watch x movie? - let me see. no, it in this other service beside the 3 we are paying.
But biodiversity is a good target and as unbiased as you can get. More biodiversity means more adaptability and resilience of the system.
I'm sure there is a copy in an external ssd I lost 2 summers ago.
But they turning some knobs based on load also looks razonable.
Is your data organized or is just a dump of unrelated content?
- If you have a bag of files without any metadata the best option is to create something like a RAG, with a pre OCR step for image files (or even some multimodal model call).
- If the content is well organized with a logic structure an agent could extract information with a little look around.
Is static or varies day by day?
- If is static you could index all at once, if not, an agent that pick what to reindex would be a better call.
I'm not aware of a solution like this, but seems doable as an MCP server. But the cost will scale quiclky.
It's better to teach people that there is no free lunch, and they should take care about the calories they are consuming, even if that imply reduce frequency of sweet foods, than sugar coating an equally bad alternative to make it sound like it's healthier.
If there is no authenticationData then the if !Ok is never run and the code continues execution as it were authenticated.
I like your funny words. No, really, I should expend some time learning APL.
But your idea deeply resonate with my last weeks struggle.
I have a legacy python code with too much coupling, and every prior attempt to "improve things" went adding more abstraction over a plain wrong data model.
You can't infer, reading the code linearly, what methods mutate their input objects. Some do, some don't. Sometimes the same input argument is returned even without mutation.
I would prefer some magic string that could be analyzed and understood than this sea of indirection with factories returning different calculators that in some instances they don't even share the same interface.
Sorry for the rant.
Vectorization, more cache levels, branch prediction, multiple cores and processors, gpu, virtual machines, (operating systems, but they didn't change much, I only let the placeholder for the layer), containers, but all that in the cloud, distributed databases, frameworks written in a language that need to be compiled to a language that is actually implemented by a web browser in the client (we are far better on compatibility between browsers, but much libraries or practices keep stuck in the past).
I haven't touched shift in practices that make it far worse.
That make it more unreasonable.