Skip to main content

Intel employment interview approx 1995

I don't remember the exact date but it was some time in the 1990's. By then I had achieved my 10,000 hours and it was time for me to work for someone else. At the time I had worked on every conceivable layer of the software development stack:

  • PLA - programmable logic arrays
  • BIOS
  • QA automation
  • TSR - terminate stay resident
  • device simulation
  • GUI applications including object oriented design predating C++ for OS/2
  • database applications
  • disk device drivers
  • video device drivers
  • AIX kernel design for the mach kernel
  • OS/2 internals and complete retrofit of presentation manager
  • communications programs
  • software copy protection removal
  • other communication protocols
  • x86, x386, x960 assembler projects
And so I decided to interview with Intel in Portland and I was granted an interview. During the interview I was asked the question "how many lines of code did I write in the last year"? While I had particularly prepared for that question it was something I had the answer for. 
While working on ValueLink and related tools I had written about 52,000 lines of code.
Seeing the smirk on the interviewer's face and thinking I was estimating too high I qualified it by saying that some percentage of that was probably headers and some comments. And then he proceeded to question the veracity of my claim and it's probably the one reason why I was not offered the job.

So to the unnamed drone I can now tell you to piss off. (i) because I recall the story almost 20 years later (ii) because working part time on a project over the last 7 months I have written over 35,000 lines of code completely without crazy whitespace or comments. That averages to 60K per year. And likely closer to 100K if I count all of my full time work.

Just for good measure... piss off, again!

Popular posts from this blog

Prometheus vs Bosun

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


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…

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.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…