Live data from Hacker News

Show HN: Automating daily reports, because fuck it

gist.github.com

31–40 of 54 posts

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

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

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

#32
post #19

too much too much rework, just slap a `.atom` on the back of your GH URL and be done with it.

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

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

#34
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…

Not a lawyer, but a podcast I used to follow did a "Bar Exam Question of the Week". One of the questions had to do with frequent business records being an exemption to hearsay. By that question, I'd say this would be the exact purpose of this kind of record keeping. Though, I don't think it has to be daily, just some constant interval.

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

#35
Had to do something similar in my company. We had to write how long we worked on a projects and what the task was. This was due every month and of course I only did it at the end of the month. It was all already planned and everybody knew what was being done, it was just an annoying layer on top that took hours. So I made a script that listed my git commits, searched the Jira ticket associated with it and gave me the tags in those tickets. The art of being lazy amirite

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

#37
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?

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

#40
There was a time where my company decided to implement time sheets after a consultant said it is a nice thing to do.

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.

Post reply on HN