Umbrella Game Rule/brand for lots of my activities (more)

If you have a "traditional" WebApp, and you want to make it available as a MobileApp, how do you do it? (more)

Personal Finance meta-planning paid-WebApp Start Up I run, to help people who are too busy Raising Kids to want to spend time "learning" Personal Finance. (more)

The idea of having a native MobileApp render a server-generated web page for a screen, rather than coding it native. A way of leveraging your existing WebApp work in the less-used portions of your site/app (because native is expensive, esp if you want to support both iOS and Android. (more)

Variant of React which compiles to iOS and Android MobileApps. (more)

React makes it painless to create interactive UIs. Design simple views for each state in your application, and React will efficiently update and render just the right components when your data changes. https://facebook.github.io/react/ (more)

JavaScript Rich Client FrameWork (more)

Ruby On Rails implementation of PJAX.

Push State + AJAX (more)

aka Twitter Storm - swarm of Twitter posts (more)

A Manifesto for Less-BullShit-Living: (more)

Meaningful life - see Meaningful Life Roadmap (more)

Really not just a WikiEngine/WikiFarm, but that's it's current outward-facing flavor. (more)

Structured Wiki (more)

I use FreeMind, an Open Source app. (more)

a Wiki run to be written-to and read-by a single individual. See WikiTypes. (more)

app I use to keep an entire Private Wiki folder of text files in synch between Drop Box and Android devices - because mobile-Drop Box will only keep manually-flagged files available Off-Line. (more)

see WikiLog

This kinda space: a Wiki that supports WebLog features (though I suppose you could do it the other way around, as well) (more)

Martin Fowler suggests the Feature Toggle instead of (Version Control System) Branching to support Continuous Integration. Good for A-B Test, etc. The basic idea is to have a configuration file that defines a bunch of toggles for various features you have pending. The running application then uses these toggles in order to decide whether or not to show the new feature... It's very important to retire the toggles once the pending features have bedded down in production. This involves removing the definitions on the configuration file and all the code that uses them. Otherwise you will get a pile of toggles that nobody can remember how to use... Feature toggles can be used for permanent variable configuration too, such as different versions of a software for different contexts. This is a different usage to handling pending features but most of the implementation is the same. If you use feature toggles for other scenarios too, it's wise to clearly separate the pending feature case from the permanent cases. (more)