The precision is around 60% - 70%. It could be increased with LLMs+RAG and I've tried it already, but that would cost some $$ on this amount of comments.
> Get on my level, son. It’ll be one man unicorns, new breed of CEOs running army of openclaws. I’ll have you fucking know that I’ve just launched “build me a next unicorn” prompt and 1000 agents have been running nonstop for a week.
Woah, what is that 2026? Emulating the economy using human flesh is obsolete. Just emulate the entire C-suite with the fleet of agents in the latent space of LLMs running on the orbital datacenters, powered by the same solar energy that used to keep humans warm.
Tested on both ink and laser. There is a small introduction of error even with the laser printer and you have another error introduced by scanning. That limits how small the QR codes can be. Paper+QR codes are feasible only for very small files.
Some time ago, I tried to use https://github.com/alisinabh/paperify to back up some data I had in the form of QR codes on paper. Turns out the standard printer is very limiting in terms of how many bits of data you can fit into paper if you want to read it reliably. I would guess this would be the same in their case. Maybe they will come up with a good protocol with error codes that would suit their "printer".
Anyway, I like the concept of storing QR codes on paper or other medium even if it is not really practical.
Thanks, this might come in handy. Currently, 4 years in the business. Working for an S&P500 company at the moment, but I am considering running my own thing or joining a startup as the next stop.
I am personally not a fan of TODOs, use tasks instead. TODOs are embedded in codebase - difficult to work with, that's why we have Jira where you can manipulate, filter and aggregate tasks. The only acceptable case of TODOs in my opinion is to leave them as suggestions to a future person in the case of refactor. Then you could have a task that says something like "Refactor feature xyz and solve TODOs".
I feel that LaTeX is still a good option for broad use, as it is the default that "everyone" knows. It may happen that Typst will be forgotten in 10 years, I doubt that will happen with LaTeX.
> So, I gather that you treated your solutions as throw-away code, rather than keeping them?
I kept the code that I found clever or useful, but I had a very borderline approach to archiving my stuff in general back then. I was still in high school.
Ah okay, I was active there 9-12 years ago, so it migh been before the crash. I remember checking it, however, 7 years ago, and I was still able to log in.
No one tells you that they delete inactive accounts. I used to have over 300 solved problems htere. Now it is all gone, all the effort, but the skill remained of course.
The question is whether you would like to work for a company that doesn't want to allocate human resources for your interview. It gives the same or even worse vibe as when the interview is disorganised or borderline. Often, the interview and the short contact with people is the only thing you will have in order to decide if you would like to work with those people or not.