275 karma · joined July 24, 2022
Quite literally "cold-turkey'ed" from 4.5-ish hours/day to 2 hours a day in a single day, consistent over the last few weeks.
I set up my second phone with a custom homescreen, and installing the 'bad' apps on there (Instagram, Youtube, NYTimes in particular). I dont use it for other apps.
Now if I want to scroll, which I still do sometimes, I have to walk to a specific chair next to which my 'addiction phone' is, I'll scroll for 10-15 minutes, and get back to the real world. I used to have particular issues with scrolling during vibe-coding sessions, and I'm genuinely surprised how well this approach worked for me.
Each cat mirrors the agent's state, such as sleeping when idle, walking when working, sitting when waiting for input, running toward your cursor when it needs permission.
Fully native Swift, no Electron, under 5 MB, zero network requests, all session data stays local as plain JSON.
I published it source-available with an honor-system license, but this week I’m going to fully open source it and remove the licence. The payment/nag system was an interesting experiment but the project is more useful to me as a proper OSS tool at this point.
I hadn’t seen many practical writeups on running coding agents in cloud VMs specifically, so I figured it was worth sharing what actually worked day-to-day for me. I use this approach practically daily now
https://jakobs.dev/learnings-ingesting-millions-pages-rag-az...
Although, in fairness, I probably wouldn’t make a much better case for either of the sides
Looking at it, they heavily focus on tracking the movements of players now to replay in AR
I’ll definitely try to apply it in one of my pet projects. Good stuff
I will add a comment/edit to the post once I am home to clarify the relative ease of solving MNIST
Will sign up for one of the events, for now feel free to already look at https://Jakobs.dev
My colleague and I have been working on this tool and using it in some internal projects. It works quite well as an intent->functions machine, and makes the process of invoking functions with GPT a lot more bearable. We hope to make it a library which does one thing so great that it will be the industry standard in its niche, so looking for some feedback on the documentation and use.
Hmm...
Is this indicative of a bad job market, or instead perhaps a bad fit between the perceived skills/value the persons belives themselves to have, and the view of the recruiters?