I had some goals for 2026 and just wanted to track my progress without over analyzing.
Solution: I vibe coded an app to keep track of how many times I complete a goal each day. Myself and my family are loving the app. I'd love to hear others' feedback if they find it useful.
My experience at Meta is that those weeks are spent not fixing bugs but working on refactors which increase your LOC and diff count. Many of the tasks engs work on are ones they themselves created months previously as "todos".
I question my life a lot when I'm reviewing code which appears to have been written incorrectly at first so that the author can land a follow up diff with the "fix"
Yeah he's hard to beat! Also I think the auto matchmatching was broken due to the websockets automagically closing after some inactivity. Should be fixed now if you want to play others. I'm starting work now but I'll double check it's actually fixed another time.
Same in my case. I quit my first software job because it made me feel so meaningless and depressed. I was immediately happier. I quit my second job because they overworked me. Same result.
I have less money now, but I don’t care. I’m much happier being where I am now.
People underestimate just how much work life affects your entire life.
A new privacy-friendly scripting language for the web. Somehow the language itself needs to make working with userdata something explicit, and then it could provide controls to the browser user.
I made a platform for publishing and purchasing photoshop files/effects, music, high res images etc. https://crate.as/
The main gimmick is that it’s a native Mac (and very soon Windows) app, so once you buy a file, you can drag it directly out of the app and into other programs as if it were file explorer.
I’m not at $500/month yet, but the project is well over 1k a month and I have a percentage of the income.
Unfortunately, selling source code is very hard. And the market for site builders is very saturated. But it’s hard to say in your case without having seen your product.
Bingo. 90% of the things I broke my back over because “it was an emergency” got scraped or abandoned a week later. And my ex-employer was wondering why our team turnover was through the roof.
I'm working on Swift interpreter and the codebase is fairly difficult to debug. There's a lot of reused bits. So if you put a debug point somewhere trying to capture one behavior, odds are that that line will run 10 times for other work before the relevant part uses it.
So I tend to write a LOT of print statements that flush of debug variables right before I where I want to debug. Then I set a conditional breakpoint so that I can have the logs "stop" right where I want the program to.
Example:
// debug print
let someValueICareAbout = variable...
print(someValueICareAbout)
print("") <- conditional debug point here "if someValueICareAbout == 3"
I think it's technically still "print debugging", because I'm only using the debugger to stop the program so I get a chance to read my output.
I’ve been working on https://liveapp.cc It allows for iOS apps to be deployed outside of the App Store by streaming apps through an App Clip. Apple has approved my app, but I’m expecting they’d ban it if I allowed users to host their apps for something more than beta testing
Solution: I vibe coded an app to keep track of how many times I complete a goal each day. Myself and my family are loving the app. I'd love to hear others' feedback if they find it useful.