Welcome to the 8th issue of TMPDIR Weekly, a newsletter covering Embedded Linux, IoT systems, and technology in general. Please pass it on to anyone else you think might be interested and send any tips or feedback to our forum or email@example.com.
The next Generation GNU profiler was announced in August to GNU binutils mailing lists. This is a new tool covering profiler functionality and plugging gaps in existing implementations. It can profile multithreaded programs and shared libraries as well. The biggest change is that it can profile production binaries, which means there is no need to build programs with -pg to get a good profile. This will reduce the usage friction in a huge way. It supports C/C++ and Java. There was a good talk at the Linux Plumbers Conference GNU track on this.
The Speedy PaSh shell compiler project tries to speed up POSIX compliant shell scripts by providing automatic parallelism to the script, can be effective especially on multicore systems. Its been adopted by Linux Foundation and thusly expects to receive more development and user time.
is a user space daemon to manage OOM conditions, it was done at facebook and has
been integrated into systemd about a year ago, its has been coming along nicely
ever since, there was a
nice update on it at LPC.
A patch to reduce number of native dependencies has been posted to OpenEmbedded core mailing list. This patch should reduce amound of shared state required to build packages as it decouples some of default dependencies from native sysroot and should improve overall build times also. This however is not all rosy as it has unveiled a lot of packages requiring these default dependencies which would need to explicitly call them in the recipes. A common overlooked dependency is pkgconfig. This is not expected to go into upcoming October release but is more slotted for next LTS in April 2022.
Continuing to experiement with NATS AuthN/AuthZ concepts and refine an approach to Simple IoT Authentication.
When I compare the SIOT block diagram to the complexity of other IOT systems, I conclude we must be doing something really right or really wrong.
There are so many good tools available, but we must understand the data we have, and use techniques that accurately convey the information we need -- displaying raw points is not always good enough.
As I’ve been refining my approach to work, a phrase has been sticking in my mind:
Lead with documentation
What this means in practice is when I start working on anything that requires a little up front thought, architecture, or planning, the first thing I do is open up the documentation for the project and start writing. If collaboration/discussion is required, I open a pull request to facilitate discussion. However, the approach is still documented in the repo files, not in the PR, Github issue, etc.
This is very different than how most people work, but I’m finding it enjoyable and productive. It is taking effort to switch, as I still tend to put too much documentation in Github issues. Old habits die hard and change takes time.
For this approach to be effective, documentation needs to be frictionless. For me, this means Markdown – preferably in the same repo as the design/source files. Then it is easy to edit code and docs in the same editor.
Some of the benefits to this approach:
- when you are done with a task, the documentation is already done. Doing documentation after the fact is a rather distasteful task. However, if it is done before the task, it is very engaging.
- it helps you think. As Leslie Lamport says, To think, you have to write. If you’re thinking without writing, you only think you’re thinking.
- documentation does not become stale, outdated, and useless.
FOSS Engineering jobs
The Linux Foundation has published a job report which says that industry is looking for FOSS engineers more than ever before.
Interest in staff who have experience contributing to
open source projects increased this year; 44% of hiring managers stated this to be the most important technical skill or experience when looking for new team members, higher than any other.
Participating in OSS projects and building up your Github profile seems like a prudent move in this technology age.
Quote for the week
There are only two kinds of opensource projects, the most hated ones and ones no one uses.
Thanks for reading!
Khem and Cliff