Original article: https://seeinglogic.com/posts/visual-readability-patterns/

This article discusses various visual patterns that contribute to code complexity and make it difficult to read. It examines metrics like Halstead Complexity and Cognitive Complexity, highlighting their strengths and weaknesses in measuring readability. The author concludes that while no single metric is perfect, they provide a framework for understanding and discussing code quality. The main takeaway is that writing readable code involves using simple, familiar patterns, creating smaller functions, and managing variables effectively.

Here are the main rules for making code easy to read, with examples:

1. Line/Operator/Operand Count Make smaller functions with fewer variables and operators.

• Hard to Read (More operators and operands):

This is just a dump of some interesting undocumented features of webOS (3.8 specifically, on early 2018 4k LG TV) and other development-related tips.

• OpenVPN frontend (OpenVPN itself is easily buildable and runs on webOS TVs: https://discord.com/channels/407937994037919756/835489130967859251/906943542457401395)
• App autostart manager - dynamically update arbitrary app config and register it as input (see Registering an app as an input)
• webos-vncserver frontend with autostart option
• Package hyperiond into Piccap directly
• Quick Screenshot (expose HTTP port that just returns PNG of current screen contents)
• Custom IR remote codes editor/updater/blaster

$ export MYSQLCLIENT_LDFLAGS=$(pkg-config --libs mysqlclient)
$ export MYSQLCLIENT_CFLAGS=$(pkg-config --cflags mysqlclient)
$ pip install mysqlclient

PyMySQL/mysqlclient#584

See this issue.
Docker best practise to Control and configure Docker with systemd.

1. Create daemon.json file in /etc/docker:

    {"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]}
   

brew install nginx

Configuration file for nginx will be at /usr/local/etc/nginx/nginx.conf

Web apps can be stored at /usr/local/var/www

Start:

REST API response format based on some of the best practices

https://api.example.com/v1/items

https://example.com/api/v1/items