21–30 of 54 posts
LOL I have to do weekly report and submit it every Friday. The kicker is, I have a meeting Monday morning about what I'm doing the week and what I worked on last week. No team meetings, everyone is soloed. Management is great.
too much too much rework, just slap a `.atom` on the back of your GH URL and be done with it.
TL;DR: I plan and it helps me. When I'm working in IC mode: - I plan for the next day at the end of the day (org-mode). - If I'm working on planned tasks (programming, demoing, documentation, etc.) I tick checkboxes. These tasks are usually small enough to do in 1-2 hours. - I also tick checkboxes for must do things e.g. when on call. I'm sceptical about planning and working on a bunch of things without putting them…
Earlier quoted context omitted.
We used to receive so many automatically generated emails and I really doubted that anyone was reading them but every time I asked if I could disable them people would swear that they were essential. I got so sick of them that I commented out the line in the script that sent them with a note that I would pay $20 if someone found that line. Nobody ever noticed that the emails stopped and I left years later without pay…
One of the first things I do at every job is setup outlook rules to auto forward all those Atlassian, slack, etc auto generated emails to respective folders. I never look at them, it's never a problem. It's amazing the huge effect that reducing the information overload has on one's day to day sanity.
(In a large educational establishment, not IT).
I did something similar to this a while back with a one-liner aliased in my Bash includes, called gitsum (short for git summary). alias gitsum='git log --pretty=format:"* %s" --author `git config user.email`' #myself It gives my git commit messages as a Markdown bullet-point list. It only works per-branch unlike the linked gist, but one cool thing about it is that you can tack on additional git flags, such as --since…
b) here's the same thing but redone as a git alias (in the [alias] section of your ~/.gitconfig). This would be invoked as `git logme`
logme = !git log --pretty=format:\"* %s\" --author `git config user.email`
LOL I have to do weekly report and submit it every Friday. The kicker is, I have a meeting Monday morning about what I'm doing the week and what I worked on last week. No team meetings, everyone is soloed. Management is great.
That's... good, right? You write a report on Friday, and come Monday morning you can just read the points from that very report during the meeting. Zero stress.
Earlier quoted context omitted.
One of the first things I do at every job is setup outlook rules to auto forward all those Atlassian, slack, etc auto generated emails to respective folders. I never look at them, it's never a problem. It's amazing the huge effect that reducing the information overload has on one's day to day sanity.
I have to admit that I extended the filters to include email sent to selected distribution groups and from one or two specific colleagues. Also any email that was cc'ed to me from certain other colleagues - the ones who cc loads of people. Got more done that way. (In a large educational establishment, not IT).
What happened? Well, a per-sprint task to track overhead and PTO is what happened. Which many people just added 40 hours of effort to.
Nice! Definitely agree with the sentiment! Might be worth investigating git log -p | gpt4 if management starts requiring something more organic-looking.