Skip to main content


Nothing is for FREE pay for the class

In most technical endeavors there are the occasional savants, however, they are a rare find. Most times you find someone with an advanced aptitude. In the last few days I find myself hard pressed to understand what the developers were thinking when they decided to use cocoapods as part of Flutter and why gitlab's config file had to be that complicated. I'm still trying to clean up the disk consumption in Docker and why some virtual machines at AWS timeout and some work just great. And why rancher decided to build k3os on ubuntu and not rancheros.
for the price of the class you get all your questions answered. It seems to me that you just gotta pay to play. It's the open source economy...
Recent posts

an eye on simple version control

This is part 2 of my version control rant. And without starting at the beginning let's just start. I want a simple version control system with a web UI, runs in docker, simple to deploy, operate and backup. So let's go thru the list... (as I was wring this post I found a great reference)

RCS requires a checkout/lock to prevent others from making changes while this person is working. That works for small teams but it's too easy to forget to lock a file. It's a GNU project and it's last change was in 2015 so not sure it'll work on windows or mac although there may be some 3rd party versions. It;s also LOCAL only.

CVS I thought this was also a GNU project but it's not. Apparently It's last changes were in 2008. This project is mostly dead. As I recall there was a time when CTOs were converting to Subversion like it was xmas day. CVS is just a little better than RCS in that I think there is conflict resolution/merge built in. (checkin/checkout)

version control

First of all let's call it like it is. git was never meant for average users; it was one man's solution for one very large problem. and as it stands right now most projects are simply not that complicated and do not need that sort of tool. I reference some coworkers who are still using RCS and CVS. I'll reference Fossil which I like a lot because it's simple not to mention that the individual project repositories is a SQLite DB.

So why on earth would I want something the size and complexity of git for version control? Right now I struggle with gitlab because the best free on-prem version of git with a CI/CD engine. Also it's double duty as a runner and it's integration with docker also make it it a gem... but then when you run out of disk space you are cooked. As I was.

Let me restate this in plain English. Most projects are small. Even if you think you have a large project it's probably small. Also you do not need git to snapshot your code. Just something …

against VMware

One significant con is finite resources.

My on-prem gitlab server ran out of disk space and my world nearly came crashing down. The Intel NUC is an i5 with 32GB RAM and 500GB SSD running CoreOS. There are several containers running in the docker config that include gitlab, gitlab-runner, haproxy, and mattermost. Each of those containers share all available RAM and SSD. So if one goes crazy then they all lose.

And that's what happened to me. gitlab-runner does not really clean up after itself so this time it mashed the whole system. Also gitlab stores all of the container registries and backup archives. Right now a single collection of my registries if about 200GB. I have about that amount in backups too even though the source is only about 75M.

Following the documentation I managed to orphan all of my source code. One slight miscalculation and I could have lost years of work.

But I'm looking at my on-prem hardware and there simply is never enough.

Flutter lang versus the world

The flutter language and ecosystem is interesting and is actually built on many generation of giants. However from my position it seems more like lazy rather than pragmatic. "We" are in a very different world right now and flutter is not really going to fix it.

For years managers have been wanting a unified programming language so that [a] client interface programmers and [b] server and service programmers; could be interchangeable. Sure there were some minor successes when nodejs was released and made it mainstream. In fact there are still a number of meaningful applications but that's another story.

Where we are is management has nothing but contempt for the rockstar programmer and the wanna-be rockstar programmers. Management sees us as simple labor. Of course management is not alone as there are many other pressures. Take a look at any org chart and the rank and file programmer is typically at the bottom. From time to time a company has a technical track however thes…

enterprise database at scale

I just finished writing a post about Star Trek LCARS and the user interface. Then some google headline presented an article about enterprise databases at scale. And that just pissed me off. I look at some of my customers and I get stressed when they want to customize everything. Those damn reports can represent anything as the business team makes wholesale slaughter of the other side of the business... the reports start to lose meaning.

Data scientists seem to get lost in the idea of data normalization when the real issue is standardization. For example, if you want to build a successful business and then take that success to a second business then you probably need your tools to come along. But if the systems that feed those tools are faulty or represent something different then you've failed.
One of my clients has revamped their systems multiple times over the years and the problem is that there are no measurements to see if the changes had their desired effect. And that measure…

next generation reporting

The title of this article is a double entendre. If you have watched Star Trek the next generation then you know that LCARS is the Enterprise computer's visual interface.

What is amazing about this interface is that it presents compact and actionable information. What you never see is pages and pages of endless scrolling rows and columns of data that the operator would need to scan thru to find the thing they needed. Also, when you think about the operators and in many cases the engineers like Wesley Crusher they used many of the same screens to "program" the computer.

Many years ago I was trying to get my company's executive to accept the fact that Linux and BSD were good operating systems and in many cases better alternatives to Microsoft Windows. (at the time Oracle purchased or was about to purchase Sun Microsystems which had been on the decline for years and while Windows was increasing market share it was not ready for the enterprise or the internet. Remember th…