I wonder what my last commit at each job was. I’ll bet it was boring. About 10% of my commit messages are genuinely interesting.
I wonder what my last commit at each job was. I’ll bet it was boring. About 10% of my commit messages are genuinely interesting.
I think the last new instruction the JVM added was invokedynamic like 10 years ago. I believe they did it so lambdas could be called efficiently. Polymorphic incline cache and stuff.
But the JVM has grown more complex in other ways. The way to force simd instructions is pretty wild, for example.
I don’t know enough to call it a mess or not. It works though.
I think Linux has grown beyond the good will from contributors. I got the sense most folks do this as part of their job.
So it’s not your boss. It’s someone who you have to make happy to do your job. And your boss can’t help. Quitting won’t help. Not if you want to work on the kernel.
It really does drive people away. I’m not good enough for the kernel, but there’s a project I could contribute to as part of my job but I don’t because there are mean folks there. My first contribution there was met with cursing.
We squash. I’m not really interesting in your local journey to land the change. It’s sometimes useful during review, but after that it’s mostly the state of the main branch I care about. It’s what I need to bisect anyway.
I don’t like commits that are just references to issues. Copy the issue into the commit message so
git blame
tells you something useful. Unless it’s just closing a simple big. Then the title and issue reference are plenty.Depends on the project I imagine.