Wait, people are complaining about manor lords already? So far I like it and haven’t come across anything bothersome yet. I haven’t played a ton, but I’m getting a good village going.
If anyone thinks hiring 50 people will get them an update in a week, they’ve never worked on a group project at all, let along a comolicated one. They’ve been working on it for what, 5 years now? And it’s just gotten what is essentially a beta buukd?
These people need to chill out and let a good game slowly unfold, not take a promising start and try to speed run into the trash can.
Luckily the devs are a lot smarter than the average 11 year old.
This is what I hate about squashing. I love the fact that my crazy journey to a finished feature is there in the log for everyone to see, including myself lol. But squashing makes me feel empty when I write commit messages. Where’s the fun… Just a straight line of perfectionism. Maybe someone has a crazy but cool idea that would be worth picking. 🍒
Maybe. I do more DevOps these days, so tend to have many small changes that can’t even be tested without checking them in and running in CI. I’d have hundreds of “fix unit tests” commits alone
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.
I’ve been thinking about that when talking to my DevOps colleagues, that there’s gotta be a better way to test CI before committing. The whole change-commit-test dance would kill me if on a daily basis. So cumbersome.
I think long messages are a good habit. Start with something readable in the history, past that who cares? Most people rarely read past the preview, and if they do they want details
I think it’s great because it makes you reflect on what the goal was and what you did. I sometimes stop to make a quick change as I’m writing, or just collect my thoughts before mentally dismissing the task
Added zip code to the reseller portal when batch-creating transactions in <main-project>
I try to start off descriptive, in case I want to diff a few changes back. After that, sometimes I write notes or general reflections on life in there… Until yesterday I thought no one was reading them
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.