Skip to main content

News time- Moving jobs and moving locations

Now that I told most of the people who I work with, and the vendors who I deal with often.  I've decided to accept a position at a very exciting startup.  The company is located in Atlanta, so I'll be moving down south.  It should be interesting since with the high growth Atlanta is not as "southern" as it could be. 

The company name is ( and its a very interesting business.  They match up companies who want to have parts manufactured with manufacturers.  The kicker is that they have a good presence in europe, and a large presence in China.  It allows for smaller shops to get the benefits of the big companies regarding leveraging the global economy.  It has some very high profile investors, and has a profitable, and fast growing business.

I will be doing all kinds of infrastructure work there.  There is a hot list of major issues which I hope to start to tackle right away, but I'll be moving back into a role further from the tools and technology and into general  IT issues.  I will use my skills to focus on system issues, application problems, network issues, and security problems.  I already have to tackle some problems around exchange, sharepoint, and the hosting environment.  There is a lack of specific kinds of tools there, and I hope to take a best of breed approach with a combination of open source, and small company products (Sorry HP and IBM).  There are a lot of cool products out there I have tested and wished I had a smaller enterprise to deal with.  Now that i'll be working in a smaller environment in terms of production and enterprise it will be a good chance to use these tools.

Since my current employer is large, public, and sensitive, I've avoided naming them.  I will be leaving there on 8/1, and starting my new position on 8/4.

Please keep reading, I will post anything that comes up in the meantime, and should resume in early August.

Thanks to you all, please leave comments, IMs, or email me!


Anonymous said…
Jonah, we couldn't be more excited to have you on board. Going to be great working together again! See you in a few weeks :)

Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, m aybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments. The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off component

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging): (registration is free) when HTTP_REQUEST { # Check if there is a JSESSIONID cookie if {[HTTP::cookie "JSESSIONID"] ne ""}{ # Persist off of the cookie value with a timeout of 2 hours (7200 seconds) p