Skip to main content

The 10x programmer or the Super-polyglot

I was just looking at for a project I'm working on. I have a number of concerns about integrating with non-critical 3rd party systems; the least of which is privacy and security. What concerns me most is that most new programmers are not polyglots and actually have an opinionated view of the ultimate development stack and so the two compete for mindshare as we try to decide what to build, integrate or buy.
I continue to proselytize the virtues of knowing your stack in order to avoid careless integration.
Going back to swagger; it's written in java and while that's not a very big deal there are the mixed signals from Oracle depending on who you follow and the news you read (FUD). But then there is also the embedded crud-ware that Oracle includes in the installers. You cannot just install Java and go. Of course there are 3rd party JDKs but then you have to validate which JVMs are supported/tested on which app; and so version creep begins. And that can be offset with containers like rkt and docker.
The amount of wrapping is starting to get pretty thick. Each layer requires expert knowledge. Each layer requires regression and readiness testing.
And then there is the question of real value. swagger's value proposition is it's code generation and it's GUI. There are several parts to the code generation and it depends on your perspective. Swagger's code is generated from a spec file. There is nothing special about the spec but the generator will generate client stubs for the defined API.

This is interesting in that the client stubs can be generated with version consistency with the spec file so long as the file is kept consistent with the server side APIs. And that's the rub. Where is the server side in all of this? The amount of work required to keep the spec file should be minimal and a product of some other compilation step.
code generation should be a one to many operation. Having some defined API method a generator should be able to identify the APIs, generate the API entry point and the client stub. (sourcegraph has some interesting go tools in this space)
Your 10x programmer and your super-polyglot will drown if they get tripped up in menial tasks. It's the wrong problem for the wrong person. I'm also trying to say that if you know your tools you should not have to use this sort of tool.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…