Posted by jpluimers on 2019/06/07

`ls` colour codes
I got confused as I thought red text would mean an error.
But they’re not: greenish yellow on a read background means error (a symbolic link to a place that’s no longer there).
It’s the output of https://github.com/gkotian/gautam_linux/blob/master/scripts/colours.sh as the one at
Actually the script is here https://raw.githubusercontent.com/gkotian/gautam_linux/master/scripts/colours.sh as the one at [WayBack] command line – What do the different colors mean in the terminal? – Ask Ubuntu failed with errors like this one:
-bash: *.xbm: bad substitution
The full script output is below.
Since various terminals have a different mapping from colours in the ANSI escape code colour table, I used the standard HTML colours using (which slightly differs from the Terminal.app screenshot on the right):
References:
Note that the shell on Mac OS X uses a different way of configuring colours CLICOLOR as described in [WayBack] settings – CLICOLOR and LS_COLORS in bash – Unix & Linux Stack Exchange. I might cover that another day.
Script output:
Read the rest of this entry »
Posted in *nix, *nix-tools, ANSI escape code, bash, CSS, Development, Encoding, HTML, HTML5, Linux, openSuSE, Power User, Software Development, SuSE Linux, Tumbleweed, Web Development | Leave a Comment »
Posted by jpluimers on 2019/06/06
Reminder to re-read [WayBack] I am looking for a good replacement for INI files for storing large / complex configuration. So far I have used JvApplicatoinIniStorage + a custom INI f… – Thomas Mueller (dummzeuch) – Google+
INI files are textual and allow for comments. They are not good at large bits of information, and are hard to compare because the order is unimportant.
Alternatives like JSON or DFM have similar limitations.
XML is too chatty, and hard to get right by humans.
Related: [WayBack] JSON as configuration files: please don’t
–jeroen
Posted in Delphi, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2019/06/06
A few nice reads on that not to estimate and why:
Related:
Via:
–jeroen
Posted in Agile, Development, Scrum, Software Development | Leave a Comment »
Posted by jpluimers on 2019/06/04
Should be on the wall for every development team around:
Why We Write Tickets
Shared with my team the other day in Slack …
Why we write tickets
- So if we get sick, a teammate can help us out
- To help us decompose our work into small pieces
- As a placeholder for a real-life conversation
- To keep track of how we resolved the issue
- To make our standups effective
- To point out dependencies
- To reflect on the mix/makeup of our work during retros
- Self-discipline.
- Don’t take on too much.
- Try to do one thing at a time
Why we DON’T write tickets
- To track our time
- To compete with other team members
- To show managers we’re busy
- To make managing people possible
- To report status, or % complete
- Because Jira is fun to use
- External discipline
John CutlerFollow – Multiple hat-wearer. Product development nut. I love wrangling complex problems and answering the why with qual/quant data. May 4
Source: [WayBack] Why We Write Tickets – Hacker Noon
Via: [WayBack] Why We Write Tickets – Hacker Noon – Marjan Venema – Google+
–jeroen
Read the rest of this entry »
Posted in Agile, Development, Software Development | Leave a Comment »