Skip to content

Instantly share code, notes, and snippets.

View robacourt's full-sized avatar

Rob A'Court robacourt

2 followers · 0 following
View GitHub Profile
@robacourt
robacourt / gist:3df7627609c95362ecf8
Created March 1, 2016 13:19
Elixir/Erlang Developer - Cloudhouse
At Cloudhouse, our mission is to eliminate the hassle of delivering software. There has to be a better way and we reckon we're smart enough to work out how. If you think you can help then step forward.
Right now we're looking for more exceptional software engineers/smart creatives that are:
- Experts in Erlang or Elixir
- An Open Source Contributer
This second point is mainly so we can see some real code that you've written, but we also think if you're an open source contributer it's a good indication of your mindset.
Our pioneering Elixir project is a WAN accelerator for SQL Server but we also play with lots of other technologies and solve all sorts of interesting problems. For more info see: http://www.cloudhouse.com/how-we-do-it
@robacourt
robacourt / elixir_dev.md
Last active March 2, 2016 00:46
Elixir/Erlang Developer - Cloudhouse

Elixir/Erlang Developer Required - Cloudhouse

Cloudhouse aims to allow any application to run from the cloud. Our WAN accelerator and virtualisation technologies allow applications that were originally designed to be installed on a PC and run on a LAN to be used anywhere. This presents us some interesting challenges! If you think you can help we'd like to hear from you.

Right now we're looking for more exceptional software engineers/smart creatives that are:

  • Experts in Erlang or Elixir
  • An open source contributor

This second point is mainly so we can see some real code that you've written, but we also think if you're an open source contributor it's a good indication of your mindset.

@robacourt
robacourt / da_app_testing.md
Last active May 25, 2016 10:42

Steps for testing an app

  1. Wipe the client and server telemetry files
  2. Start DA Client and Server
  3. Find 3-5 workflows through the app (try to make the workflow realistic, e.g. create an invoice, add various items to it and issue the invoice)
  4. Go through the exact workflow until all the pulses in it are learnt (see below)
  5. If after 8 times through the workflow the pulses still haven't learnt take a SQL Trace of the workflow and a NetMon capture from the database server
  6. If the pulse query count varies substancially for the same workflow let us know. For example a workflow may have 5 pulses, when you first run it the query count may be 5, 100, 2, 40, if the second time you run it the query count is 5, 250, 2, 40 we'd like to know!
  7. Run the analysis tool on the client and server telemetry files, get both reasons and performance stats.
@robacourt
robacourt / debian.md
Last active August 1, 2016 09:31