Through the Looking Glass: Bitcoin Treasury Companies
B K Meister
https://arxiv.org/abs/2507.14910 https://arxiv.org/pdf/2507.14910
If anyone I have a connection with has any thoughts on part or full time design/illustration roles, I would LOVE to hear from you.
18 years experience and am open to new challenges!
#lookingforwork #getfedihired
My most recently uploaded work can be found in my portfolio at https://www.andycarolan.com
If you wish to find out more about me as a person, my strengths, skills and what I'm like to work with, please take a look at my personal user manual at https://www.andycarolan.com/myusermanual
CV/Resume on request
Solvable Models of Heat Transport in Quantum Mechanics
R Loganayagam, Prithvi Narayan, Swathi T S
https://arxiv.org/abs/2508.09253 https://arxiv.org/pdf/25…
Now that my game released on steam, I am looking for a new long term opportunity to work as a game designer.
If you need a (freelance) Game designer, hit me up!
here you can see my cool stuff
http://dominik-dammer.de/
SHIELDA: Structured Handling of Exceptions in LLM-Driven Agentic Workflows
Jingwen Zhou, Jieshan Chen, Qinghua Lu, Dehai Zhao, Liming Zhu
https://arxiv.org/abs/2508.07935 https:…
Portable Targeted Sampling Framework Using LLVM
Zhantong Qiu, Mahyar Samani, Jason Lowe-Power
https://arxiv.org/abs/2509.02873 https://arxiv.org/pdf/2509.0…
SPARC: Soft Probabilistic Adaptive multi-interest Retrieval Model via Codebooks for recommender system
Jialiang Shi, Yaguang Dou, Tian Qi
https://arxiv.org/abs/2508.09090 https:…
If you're writing a library, you should really avoid #CMake. CMake is designed to lock you in. As in, once you release a #FreeSoftware project using CMake, you can't switch to another build system with causing real trouble to your users. And if you support multiple build systems, as soon as you start supporting CMake, some of your users are going to start locking everyone else in.
That's because CMake uses a custom package discovery mechanism that's hardly compatible with anything else, and that is so complex that it's very hard to reimplement it with any other build system. So when others start relying on the CMake config files being installed (and they naturally will, since that's how CMake does things), you can't stop installing them without actually breaking stuff. And if you want to preserve them without actually using CMake, well, good luck with that.
And if CMake is one of the options you support, then some of your consumers will accidentally start relying on it anyway. And this will be much worse for everyone, because now their projects won't work for people who build your project with any other build system. Which in turn will force more projects to use CMake anyway. Which in turn will make more people rely on CMake being used…
Use #Meson as the build system, it's clean and not designed to lock you in. Use pkg-config for library data; it's simple and portable.
#OpenSource
Crosslisted article(s) found for q-fin.PM. https://arxiv.org/list/q-fin.PM/new
[1/1]:
- Dynamic Factor Models with Forward-Looking Views
Anas Abdelhakmi, Andrew E. B. Lim