Live data from Hacker News

Show HN: Automating daily reports, because fuck it

gist.github.com

41–50 of 54 posts

Re: Show HN: Automating daily reports, because fuck it

#41

At a previous job, software testers had to write reports every Mon/Wed/Fri on what they did and e-mail them to their supervisor. 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. Supe…

I did the exact same thing years ago, except, after about two or three daily reports I took the immature route. I started inserting lines like, "10:45am, took a shit", "11:03am, scratched my balls", "11:04am, farted; smells like Robertos", and so on. The main difference in my situation was my supervisor noticed immediately. However, the daily reports stopped anyway. The rumor I heard was that my supervisor took my immature reports to his boss in hopes of getting his blessing to fire me, however, his boss actually turned it around on him, saying the daily reports requirement was counter-productive, and "treat people like children and they'll act like children".

Re: Show HN: Automating daily reports, because fuck it

#43
post #31

For litigation use, even semi-regularly keeping a daily log can help to show independent development. That can help defeat claims of misappropriation of another party's trade secrets and/or infringing copying of another party's copyrighted material. 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) som…

Have you heard of this thing called Git?

> Have you heard of this thing called Git?

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.)

Re: Show HN: Automating daily reports, because fuck it

#44

Earlier quoted context omitted.

What does this mean? I tried adding .atom to the OP url and got a 404

i think they mean like this: https://github.com/yzdbg.atom - gives the rss feed of the original author's public github activity

correct. Then whoever can use whatever reader to format the stream however and whenever. All for free as far as your extra efforts go, we can put the time into writing better commit messages and we all win.

Re: Show HN: Automating daily reports, because fuck it

#45
post #27
post #24

Earlier quoted context omitted.

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).

If I could filter them out on Slack. It is a boon for the over-communicators.

I’ve wished so often I could block Slackbot

“so-and-so archived channel #topicfrom3yearsago”

stfu Slackbot

Re: Show HN: Automating daily reports, because fuck it

#46

At a previous job, software testers had to write reports every Mon/Wed/Fri on what they did and e-mail them to their supervisor. 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. Supe…

I did the exact same thing years ago, except, after about two or three daily reports I took the immature route. I started inserting lines like, "10:45am, took a shit", "11:03am, scratched my balls", "11:04am, farted; smells like Robertos", and so on. The main difference in my situation was my supervisor noticed immediately. However, the daily reports stopped anyway. The rumor I heard was that my supervisor took my im…

based

Re: Show HN: Automating daily reports, because fuck it

#47
post #29

Nice! Definitely agree with the sentiment! Might be worth investigating git log -p | gpt4 if management starts requiring something more organic-looking.

does such a gpt4 cli tool exist? i mean sure itd be easy to write one but i wouldnt mind trying one off the shelf

https://github.com/simonw/llm

Re: Show HN: Automating daily reports, because fuck it

#49

At a previous job, software testers had to write reports every Mon/Wed/Fri on what they did and e-mail them to their supervisor. 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. Supe…

I did the exact same thing years ago, except, after about two or three daily reports I took the immature route. I started inserting lines like, "10:45am, took a shit", "11:03am, scratched my balls", "11:04am, farted; smells like Robertos", and so on. The main difference in my situation was my supervisor noticed immediately. However, the daily reports stopped anyway. The rumor I heard was that my supervisor took my im…

Hackers will always win.

Re: Show HN: Automating daily reports, because fuck it

#50
post #31

For litigation use, even semi-regularly keeping a daily log can help to show independent development. That can help defeat claims of misappropriation of another party's trade secrets and/or infringing copying of another party's copyrighted material. 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) som…

Have you heard of this thing called Git?

We are commenting on a thread about a tool that uses git!
Post reply on HN