Is there something you do every day that builds an asset for you? Every single day? Something that creates another bit of intellectual property that belongs to you? Something that makes an asset yo…
Open Design Kit: methods for doing distributed design
Per this page (https://www.npmjs.com/package/wiki), I started Node.js command prompt and entered the following command:
npm install -g wiki
I then opened a browser tab and went to http://localhost:3000 and was able to see the Welcome Visitors page:
To be able to see the journal icons and be able to make edits, I clicked on the word “wiki” at the bottom of the page. After doing that, I saw a check mark appear next to the word, and I was able to make and save edits. It still looked like there is a yellow background to the pages. In the past, I thought that meant that changes would not be saved, but I will need to look into that more.
Next steps – look at getting wiki source code and running that so I can make local changes.
Chris AldrichA WordPress plugin that allows you to easily create a huge variety of social media post types to own your social media life online.
The Post Kinds Plugin for WordPress attempts to make it much easier to create customized displays for and format each of these types of posts (and many more). It leverages the flexibility and power of WordPress to be your single social media hub while, along with other IndieWeb friendly plugins, still allowing you to interact with other social networks.
In my experience in avionics software development, the creation of software is driven by approved requirements. As requirements change or are refined, the software is updated to be consistent with those requirements. One type of “debt” I see is when functionality is not completed on time, and gets deferred to a later software release (cost increase). Another type is when a problem is found (requirements, source code, tests, documents), but addressing the problem is deferred to a future time (the problem does not impact the functionality of the requirements, source code, or tests, or is deemed not a safety issue). This type of debt (typically called “open problem reports” (OPRs) is getting more scrutiny by aircraft certification agencies and OEMs (Bombardier, Boeing, etc.), since they see increasing numbers of OPRs as an indicator that the overall “health” of the software may not be as good as it should be, and that there should be as few OPRs as possible (in other words, fix your problems as you find them).
For myself, I prefer to fix problems when they come up. However, when you work as a member of a team, sometimes business decisions dictate otherwise….
