Show HN: Automating daily reports, because fuck it(gist.github.com) |
Show HN: Automating daily reports, because fuck it(gist.github.com) |
One of them got pretty tired of writing the same shit, and was like 99% sure the supervisor wasn't reading the reports, so started adding "I don't think anybody is reading these. This is a waste of my time." right above his e-mail signature.
It took over 3 months before it got noticed. Supervisor wasn't pleased, but had to admit he was right. He still required reports, but only on Fridays.
alias gitsum='git log --pretty=format:"* %s" --author `git config user.email`' #myself
gitsum --since 1.day
gitsum --since 1.week
gitsum --since 8.hours
gitsum --since 1.day | pbcopyb) 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`
I wrote some code that generated random data in the right format and people begged for it so I shared it.
Plenty of people started to create random reports, their bosses didn't give a fuck because they were pissed of as well (and wanted to use my tool as well).
The company ended up with a heap of nonsense data and I guess that someone realized that because this circus was gone after a few months.
That was in one of the largest and best known US company in the 00's, no wonder it went from a national pride to a peripheral company.
No team meetings, everyone is soloed.
Management is great.
we had a bot in our chat app, it auto asks everyone the questions 2 times daily, what did you do, what you are working etc...
The funny part about this though was that our team had amazing JIRA hygiene because we barely had any work to do (I'm not exaggerating when I say I would have about 5 hours of work a week, I would try to help other teams out but that was "stepping on other teams turf"). The teams that had the worst JIRA hygiene were the core platform teams shipping new features. Our team built internal tools so we didn't have to care about UX/scaling/etc.
Ultimately some of our team was laid off, but it made me realize upper management really had no idea what was going on since they were not technical. All they saw was pretty JIRA graphs and thought our team was a bunch of rockstars.
I guess, end of the day, that requirement - for daily reports - is sort of a red flag all by itself. Once they get to that point, something's borked.
[1] Oh, and his Leadership. I heard executives have that.
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.
git log -p | gpt4
I mean, whom are you more likely to believe:
1) someone who — when being sued — said, oh, no, we didn't steal your technology, we developed this independently, or
2) someone who said the same thing and also had at least some contemporaneous documentation to corroborate the assertion?
(Incidentally, this is one of those areas where perfect is the enemy of good enough.)
Hmm. Git ... Git ... Let me see: As in, git along, little dogie? Or you stupid git? Or the village in Iran?
(Yes, I'm familiar with Git; its commit records could help corroborate development, too.)
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 down.
(In a large educational establishment, not IT).
“so-and-so archived channel #topicfrom3yearsago”
stfu Slackbot