Skip to main content

Y2K and DLLs

What do Y2K and DLLs have in common?

Y2K was the biggest load of nothing to happen in modern history. Everyone went running around expecting the bottom to fall off of everything from the wrist watch to the power grid. But it never happened. (typically because because smart programmers trimmed the two digit century from their internal date formats.)

A manager of mine, said of Y2K, that he received a 10K bonus for saving some number of bytes for compressing the century from all date formats and now he was getting a similar bonus for putting it back in.

DLLs refer to dynamic link libraries. These are libraries or binary files that are used and shared between applications. You might have multiple programs that share a library. These were invented or made popular around the time of early Windows as Microsoft was evolving from DOS com and manageable exe files. Windows had so much bloat and the disk drives at the time were so small that this was the only way to keep things manageable. Today DLLs are almost obsolete as evidenced by languages like Go which offers a statically linked option.

One of the biggest challenges for DLLs is that they may be versioned meaning that there are compatibility issues as they evolve and it's up to the installers and package managers to keep things organized and running.

What I'm pointing out is that while the decisions that led up to Y2K and DLLs were avoidable and in the end cost many millions in consulting fees, development costs, project overruns. DLLs created a number of challenges for the Windows installers and lots of compatibility issues over time.

What is it that you are doing right now, what decisions are you making that has the potential to be on scale with these?  Well, stop it!

Comments

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…

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: http://www.eeti.com.tw/drivers_Linux.html (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 setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…