Not sure it really has huge benefits, but I guess something like this should work:
```
#!/bin/sh
N=20
msg_len=$(git log -1 --pretty=%B | wc -c)
if [ "$msg_len" -lt "$N" ]; then
exit 125
fi
# Here you would run your actual test and report 0 (good), 1 (bad) as needed
exit 0
```
## Remote: Yes ## Past missions in Europe, North America, Africa. (When remote, visits as needed, days every few weeks to weeks every few months depending on distance.)
## One-liner ## Existing software I fix and extend. Challenges I tackle writing high quality software. Industrial, embedded, image/signal routing/processing, distributed, real-time, fail-safe redundancy.
## What situations call to reach me ##
* when "good enough" in your project means "runs really great",
* when others have not made / would not do such a good job / left you piles of bugs,
* when most freelancers or hires are too specialized or not hands-on enough. By contrast I can cover several techs, levels, and do architecture, design, write code and work with other people, tech and non-tech, including C*O.
Working in close contact (regular phone calls to remain together on track and to the point at all times).
Past missions in railway systems, embedded systems and other industries, open to other domains that need reliable software.
Short to medium-long missions preferred.
## Project size ## From one deployment (embedded/desktop) through dozens of networked PC, to software systems deployed to millions.
Topic: "talking to the bomb"
https://www.youtube.com/watch?v=h73PsFKtIck (warning this is considered to spoil the movie).