Remote: Yes Willing to relocate: No

Technologies:

- DevOps - Prometheus, ElasticSearch, Akamai CDN, Continuous Delivery on Kubernetes, Terraform and Jenkins.

- NFT Testing - Load testing with jMeter, Gatling. End-to-End performance analysis with Sentry and New Relic.

- Dev - Java, Kafka integration. Some experience with pet projects on Python and Node.

Résumé/CV: https://www.linkedin.com/in/jracabado/

I'm interested on technical leadership or senior reliability engineering roles. Having been working as an Architect the last year I lack regular hands-on practice but I'm happy to be challenged for a role that demands it.

I value autonomy and hard problems.

The first time I read this I could not understand it. It makes a lot of sense now seeing how plan execution is where project management really happens.

The idea would be to have a different interface to do the auto-completion.

I'm thinking of creating a visual UI through service discovery and providing an easy shortcut sheet to various points of a system.

But you can have a generic extension method that returns one of the types and then via inference you can do it implicitly typed.

It shoud be something like this in C# 5:

  public static class Lamb
  {
      public static Func<T> da(this Func<T> f)
      {
          return f;
      }
  }

  var egocentricFn = Lamb.da(() => "im a function");

One of the solutions I wanted to try was to partition the user base on a similar way that posts are filtered to you. That is based on the up votes you give. Now I'm not sure if it happens here but at least on Reddit you have it on your customised first page.

I believe that it isn't the user base that gets worse but that it gets much more diversified and people entrench themselves in groups and the "How bout dem Cowboys" problem arises.

Think of it as user and posts clustering, the secret sauce would be how those clusters interact, I don't have a tentative answer for that. This idea would top current aggregators by valuing discussion and intervenients in the same way that posts are valued.

An app to easily compare SQL execution plans.

I believe the better way would be graphical. I have needed this on MS SQL Server, SQL Sentry Plan Explorer has helped but lacks this comparison. Today I do it by diffin execution plans on XML format.

On my wildest dreams I would have a REPL accepting a DSL that would allow me to query the different DMV's (those are SQL Server data management views which give you insight on the inner state of SQL Server, Red Gate has a nice site on them http://sqlmonitormetrics.red-gate.com).

If it already exist is some form or platform please share.

But it has been on beta for almost 3 years I think. I wonder if it will ever go forward.

I am not doubting but just honestly asking. I've been discussing a possible Redis solution for complementing our current SQL Server.

Our problem isn't that big, we need to serve 10k req/sec of a simple query, can SQL Server do that? Isn't the connection pool the bottleneck to handle loads of this scale?

Several years ago with SQL Server 2008 R2 I achieved 200,000+ simple queries per second (http://bit.ly/IlH2id -- this is not a regimented benchmark by any measure of the imagination, but is only saying "validate before assuming" because you might find your install performs far better than you anticipate) using the standard TDS query interface. This was on pretty beefy hardware, and is obviously enormously contingent on the data being in memory (which you can force with 2012), however it blew me away and completely undermined an initiative we had to implement AppFabric / Redis or other solutions.

What is the mechanism to do this in MSSQL 2012?

Is Hekaton the feature you are referring to?

I just tried a yield in a recursive function and the output is as simple as a non-recursive function. Are there any edge cases interesting to see?

[1]http://blogs.msdn.com/b/ericlippert/archive/2009/08/24/itera...

Re: unforeseen edge cases, I'd love to see any failing pull requests for the test suite: https://github.com/facebook/regenerator/blob/master/test/tes...