This post appeared originally in our sysadvent series and has been moved here following the discontinuation of the sysadvent microsite
Ever wanted to record a log of an interactive console session? Easy, just use
the script utility. It’s probably already present on your system, no
installation required.
To start recording, run script --timing=script.tim script.log. This spawns a
new shell, recording stops when you exit from it.
To replay the log, run scriptreplay script.tim script.log. It is also
possible to speed up or slow down the playback speed. For example, in order to
play back the recording at half of the original speed, use scriptreplay
script.tim script.log 0.5. Ctrl+S pauses the playback, Ctrl+Q resumes.
The nice thing about script is that it records everything that happens on the
console, it’s not just a simple log of invoked commands. If you open a text
editor like vi in the recorded session, you’ll be able to see exactly how and
where you navigate the cursor, exactly how and when text was changed -
including any typos that were later corrected, and so on.
For the full documentation, check out the manual pages script(1) and scriptreplay(1).
Lombok – avoid getting burned by the boilerplate
Executive summary
This blog describes briefly the most commonly used annotations of the code generation tool Lombok which shields the Java developer from having to generate or write so called ‘boilerplate code’. It begins with explaining that term and the problems it may cause, continues with a brief setup description of a Maven based Java project that incorporates Lombok and then display some useful annotations.
These annotations are grouped after function such as object creation, field access, some methods ... [continue reading]