187 karma · joined November 3, 2010
1. Everyone uses feature branches
2. Everyone cleans up their branch using interactive rebase on top of main before review
3. All merges have been freshly rebase on main
I think it works very well and keeps the history clean while preserving "each commit does one thing".
I eventually just accepted it, but this new agent layer really takes things to a new level.
The tilde key exists in the key map here: https://developer.apple.com/library/archive/technotes/tn2450...
You can see how I did mine here if you're interested: https://github.com/bruse/dotfiles/tree/main/macOS (I suspect com.local.KeyRemapping.plist is most interesting, but the key layout file is there too, with some comments on how it was generated).
Or what type of secrets are stored in the local .env files that the LLM should not see?
I try to run environments where developers don't get to see production secrets at all. Of course this doesn't work for small teams or solo developers, but even then the secrets are very separated from development work.
Now I wonder if the maintenance cost for this type of internal system has gone down to a level where that is no longer an issue.
Trying to figure out what a good workflow looks like.
It is so demonstrably false. Anyone who has worked in an finance adjacent industry likely knows the definition of a PEP.
Once a company gets a little bit bigger, the processes around information sharing, planning and other communication has to be in place anyway. Teams need to collaborate, work needs to be tracked, there has to be meetings for planning. Once you're already doing that you might not lose anything by going remote.
This is bad in all cases, but certainly misinformation in the democratic process is up there with the worst. Of course, perhaps more importantly for Google, it's a PR disaster waiting to happen when Gemini starts touting incorrect information seemingly supporting one political party or another.
It seems some people prefer calling/chatting to finding info on their own. Even trivial info.
I think one of the issues is that in some parts of academia, progress is made one PhD at a time. And a PhD is almost always too narrow to bring all of these fields together. I'm sure they are solvable problems, and I'm sure they will be solved. But maybe it will take some other research structure? Private? Guaranteed long time funding for academic teams?
These days we have 3d cameras, but they still only see part of the objects we want to manipulate. The back side is hidden. So you need to either specify and model all objects to interact with, or have some word of a world model where we can predict what the full object, it's weight, center of gravity, surface texture, etc, is like.
And before we even decide to manipulate it, we have to detect it, categorize it and segment it (where does the pan stop and the stove begin?). We have to plan out a manipulation task, including finding grasp points, finding movement patterns that do not interfere with the rest of the environment, etc.
It's a whole bunch of separate problems that need solving all at once. There's motor control, building the right manipulators with the right sensors, bringing all the sensor data into something where we can make a single decision, understanding of the world and what happens during manipulation, and higher level planning.
It worked! I thought I was a genius. Now I'm amazed how I almost randomly got it right.