Find out what you, or someone on your team, did on the last working day

This is not much related to the project itself, but I don&#x27;t like this recent trend of implementing command line tools in Node. Command line tools are minimal and should be usable on bare-bones systems, without requiring a whole cutting edge runtime to be installed, be it Python or Node or whatever.<p>I understand many don&#x27;t agree with this, but this is my preference &#x2F; opinion.

In Mercurial:<p>hg log --rev &quot;date(yesterday)&quot; --template &quot;{shortest(node, 6)} - {desc|firstline} ({date|age}) &lt;{author|person}&gt;\n&quot;<p>This shows off both revsets (the language parsed by the --rev option) and templates (the language parsed by the --template option). The revset can be modified into &quot;date(yesterday) and user(jordi)&quot; to limit it to only a particular user.<p>As it stands, this revset+template combination won&#x27;t colourise the output. For that we need to add labels to the template:<p>hg log -r &quot;date(yesterday)&quot; -T &quot;{label(&#x27;changeset.{phase}&#x27;, shortest(node, 6))} - {label(&#x27;log.summary&#x27;, desc|firstline)} ({label(&#x27;log.date&#x27;, date|age)}) &lt;{label(&#x27;log.user&#x27;, author|person)}&gt;\n&quot;<p>At this length, it starts to look unwieldy, but it should go into your hgrc anyway, where you can easily split it into multiple lines without having to worry about shell quoting. Here are more details about the general method:<p><a href="http:&#x2F;&#x2F;jordi.inversethought.com&#x2F;blog&#x2F;customising-mercurial-like-a-pro&#x2F;" rel="nofollow">http:&#x2F;&#x2F;jordi.inversethought.com&#x2F;blog&#x2F;customising-mercurial-l...</a>

I know you can expect the source code, but this trend of pasting things into the terminal with sudo is crazy:<p>&gt; curl -L <a href="https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;kamranahmedse&#x2F;git-standup&#x2F;master&#x2F;installer.sh" rel="nofollow">https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;kamranahmedse&#x2F;git-standup&#x2F;...</a> | sudo sh

`$ curl -L <a href="https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;kamranahmedse&#x2F;git-standup&#x2F;master&#x2F;installer.sh" rel="nofollow">https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;kamranahmedse&#x2F;git-standup&#x2F;...</a> | sudo sh `<p>nice. this shit again

Plain old `git log` can handle most of this, if you care less for a nice interface.<p>git log --author=&quot;tlbonnette@gmail.com&quot; --since=1.days<p>You can of course tweak the way that git log outputs too, to make it more readable.<p>Something like:<p>git log --pretty=format:%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)&lt;%an&gt;%Creset --abbrev-commit<p>can make it quite pretty.

My much less polished bash script:<p><pre><code> $ tt 2017-03-21 repo1 author date commit desc commit desc repo2 author date commit desc function tt { local day=$1; local d=$PWD; local buf=&quot;&quot;; echo $day; cd $GR; for i in *; do local p=$GR&#x2F;$i; if [ -d &quot;$p&#x2F;.git&quot; ]; then cd &quot;$p&quot;; whatup $day fi done cd $d; } function whatup { local day=&quot;$1&quot; if [ &quot;$day&quot; = &quot;&quot; ]; then day=`date +&#x27;%Y-%m-%d&#x27;` fi local author=&quot;$2&quot; if [ &quot;$author&quot; = &quot;&quot; ]; then author=&quot;amichal&quot; fi local dir=`basename $PWD`; local msg=`git log --all --author $author --oneline --since=&quot;$day 00:00:00&quot; --until=&quot;$day 23:59:59.999&quot;` if [[ ! -z &quot;${msg&#x2F;&#x2F; }&quot; ]]; then echo &quot;$dir $author $day&quot; echo &quot;$msg&quot; echo &quot;----------&quot; fi }</code></pre>

I love those exciting stand-ups where you tell everyone what you did yesterday

This would be much more useful if it also polled calendars and code reviews!

What happens if someone&#x27;s name is &quot;all&quot;

Security policies don&#x27;t sound right.<p>Leaving first employer: Sit in a windowless room with a newspaper and several other people also with feet on desks also reading newspapers, riding out 90 days of resignation notice looking forward to next job. Fully paid, needing to turn-up 4 hours per day mainly centered around lunch, which included a break and had social time with soon-to-be former-colleagues. Cannot in any way be associated with future employer during these 90 days: meetings, personal interaction, emails, visits, anything.<p>Edit: For those that think this doesn&#x27;t sound right, think of your access to market-sensitive information, and a loyalty exists with the soon-to-be former employer. Mitigation of ourselves and the organisation.<p>I, and others in the windowless room were completely OK with this set-up of arrangements, as were our future employers who knew this on signing us. Not a non-complete clause in any way, simple prudence.