Skip to main content

Saying goodbey to the Crudbase

Today we are releasing a major update to CWAB. From user feedback we realized the separate navigation of Crudbase and file system assets was causing confusion with users. We have now merged Crudbase operations and file system operations into a single navigational view.

Users no longer need to think about the Crudbase when developing applications. The Crudbase is now a background feature that a user can get to by right-clicking "Home".

A number of workflow improvements have also been introduced that should make working on CWAB an even more pleasant experience.

The task deck also now includes a deck that contains links to Youtube video screencasts demonstrating various aspects of the CWAB platform.


Popular posts from this blog

Managing configurations with object graphs

This post is basically a pitch I send to folks whom I think will be interested in a modern approach to configuration management. I am posting it here so I can refer people to it without sending them a long email.

One of the features of the HiveMind platform is a smart object technology that solves the problem of dealing with hierarchical configuration information often represented in formats Like YAML,JSON, Java Properties,XML...etc

The smart object technology allows developers/users to directly construct object graphs of any complexity. Once you have the actual object graph you can reverse the process back to representation in any one of the formats mentioned above.

I have setup a demo instance for trying it out @

Login with login info I sent you.

Be nice, you have full system access :)

To see an example representing the AWS IP list (

Navigate to: /com/crudzilla/betaApp/web/aws/index.ins


Get out of the box sometimes

Little boxes on the Laptop, Little boxes made of Javascript stacks, Little boxes on the Laptop, Little boxes all the same. There's a green one and a pink one And a blue one and a yellow one, And they're all made out of Javascript stacks And they all look just the same. And the developers in the industry All went to the IDEs, Where they were put in boxes And they came out all the same, And there's devOps and Rubyers, And micro services, And they're all made out of Javascript stacks And they all look just the same. And they all play on the GitHub And drink their Kool-aids dry, And they all have pretty syntax And the syntax go to HackNews, And the syntax get approval stamp And then to the IDEs, Where they are put in boxes And they come out all the same. And the bros go into business And marry and raise a VC round In boxes made of Javascript stacks And they all look just the same. There's a green one and a pink one And a blue one and a yellow one, And they're a…

Your code is not a project

Language matters, just as saying the wrong word to the wrong person can leave you with one less front tooth, so too can the incorrect use of language in general create a cascade of confusion that pervades an entire industry.

One of my pet peeves about the use of language in the software arena is the use of the word "Project". This usage as far as I know goes back to IDEs grouping software artifacts as projects. The notion of a project as the top level organizing construct for software projects (see what I did there?) is now a de facto standard. One problem with this is that it is a complete misuse of the notion of a project. A project is not a thing, it is a process! A project has (or at least should have) a well defined start and end.

As a process, by its very nature, its essence is vague. So when something whose essence is precise (software) is called a project it leaves the reader wondering exactly what is being described. Whenever I come across a documentation describing…