6,881 karma · joined October 11, 2010
https://www.benkophone.com/
Currently building:
https://www.benko.app/
team@benko.app
The list goes on.
It’s a total replication of idiocracy. What right wing social media slop are you consuming that you think the US is in good shape?
Define big I guess. They're non-trivial, mix of internal enterprise tools, a multiplatform app (android/ios/mac/windows/web currently headbutting its way through review), including a billing system for my small telecommunications business.
> I dont think this is good for your mental health or physicaly your brains health
I find the experience of doing it without writing the code to be intellectually pretty similar. I still solve a lot of problems, the LLM couldn't, for example, one shot the event sourcing model I built for synching data between devices. It took quite a few iterations and I had to define a lot of the architecture, but I did it at a level that wasn't "here is a class, here is a module, this module does XYZ", more at the "whitepaper" level or describing how specific bits of the app needed to work in order to solve some problem.
It's also very similar to managing other developers.
> Its like driving your car 3 blocks instead of walking, your physical health will suffer
It's more similar to having staff rather than doing everything yourself. The problem solving just shifts to a different area, and you get more done.
So whatever, I just don't really feel the need to burn tokens on Fable anyway.
The way that information is organised and formatted matters for compliance. It’s pretty similar to writing good procedural documentation for humans.
Almost all the breakages after a big refactor are stale assertions but every time I catch a couple of critical problems that make the entire exercise very worth it.
The whole dev process is so fast compared to writing software manually that I find it absurd that I wouldn’t invest heavily in automated tests.
I can’t find any because the admin is so horrendously corrupt.
Can't wait for them to sue the NRA next!
git checkout feature
git rebase main
git checkout main
git merge feature
that way you get all your conflicts on the feature branch during rebase and your merge is always clean.
https://stackoverflow.com/a/28510260
That completely fixed the problem. Now I only ever get conflicts on my feature branches. The rule is always: rebase away from main, and merge towards main. All conflicts are then on your branches, never on main, and always from rebase, never from merge. Then I set the pull behaviour to rebase, too.
I've never had a silent regression since, and never had a problematic conflict scenario.
I did recently learn about ORIG_HEAD though which was very cool, because I had accidentally rebased to main instead of to a dev branch from which I had created a bunch of worktrees, then when I merged back to the dev branch all hell broke loose, and I learned that I could revert a merge by checking out ORIG_HEAD: