Start Writing in ES6

•June 30, 2015 • Leave a Comment

Good advice from “Preparing for the future of AngularJS”, even if you have no interest in Angular 2.0.  My current transpiler of choice is Babel for no reason other than a colleague recommended it.  There are others, so choose and play.

As more of an FYI, Babel also has experimental support for ES7 proposals.

Roslyn, LLILC and WebAssembly?

•June 29, 2015 • Leave a Comment

Given Joe Duffy’s blog is so quite these days, its time to speculate.

The LLILC announcement some months ago is interesting – a continued openness from Microsoft.  The main difference between Roslyn and LLILC, as provided by LLILC github is:

Roslyn provides frontend support, whilst LLILC (via LLVM) provides backend support:

Roslyn exposes the data structures of a frontend – so it’s ideal for building tools such as IDEs, with syntax coloring, warning squiggles, use/definition lookup, refactoring, etc; or translators that convert C# to some other language; or pretty-print formatters; or analyzers that check conformance with coding guidelines (think FxCop).

LLILC, via LLVM, exposes the data structures of a backend – so it’s ideal for building tools that inject extra code (eg: performance profiler, code tracer, debugger, parallelism analyzer, race detector); or super-optimizing code (eg: auto-vectorizer, auto-parallelizer); or test-case reduction.

The key in the above is the reference to LLVM, especially if you read “From ASM.JS to WebAssembly“, and then you read “WebAssembly LLVM Backend Being Discussed”.

Further, Brendan Eich’s recent interview on WebAssembly provides us with this:

Microsoft has their own compiler so they’ll be doing wasm from a different compiler framework, but that’s great.

Given the LLILC work, it would be logically to leverage the LLVM to generate wasm

Interesting times.

Polyglot Lambda Architecture

•June 29, 2015 • Leave a Comment

OTTO has a number of great postings on the work they are doing.  One of the most recent articles is “A tale of two lambdas: The joys of working in a polyglot team.” which speaks volumes to using the right language for the problem you are trying to solve.  Spark has really helped to move the lambda concept forwards in the last time period.  Would also agree with OTT on  Elasticsearch – ELK.  Personally not used Graphite, but it does look interesting.

On MLlib, I’ve previously blogged about success with trading research/idea recommendations.  Its also worth calling out that Logisitic Regression algorithm is very useful in finding relationship from binary response variables – an example in the trading world is the age old classic RFQ reject/accept.

DevOps Teams – An Anti-Pattern

•June 23, 2015 • Leave a Comment

Whilst in Sydney I had an interesting discussion around DevOps.  I see DevOps as a skill that sits in a team, not as a separate team.  If DevOps (and similarly QA) are separate teams its an anti-pattern, meaning the team hasn’t understood the concept of “Done”, and have failed to embrace the culture of delivery (to production).

ES6 – Is JavaScript the New Java?

•June 23, 2015 • Leave a Comment

I’ve been to a few JavaScript meet-ups recently – some public, some internal.  What’s clear is that ES6 will be a breath of fresh air for JavaScript – anyone Java software engineers looking at ES6 code will feel more at home.  Likewise any ActionScript Flex developers will also feel a bit of deja vu.  With Node.js, and the browser language war won by JavaScript, one can’t help but wonder how JavaScript server side will evolve over the next few years within organisation that have historically only accepted JVM based languages.

On the topic of JavaScript libraries and frameworks, there is an overwhelming number to choose from, which in many ways requires a team to decide based on prior experience or spend time trying out options before venturing down a JavaScript road.  SDTimes offers some views on this subject – “The future of JavaScript is (almost) now”.  As I blogged about previous, React Native looks very interesting.  Paiza Engineering Blog offers a view on Data binding code in 9 JavaScript frameworks.

A few items that maybe of interest to readers:

Angular 2, although a long way off, appears to be a contender for the future.  Worth a read (but be aware the Angular 2 API changes almost daily):

HR – An Anti-Pattern for Managers

•June 23, 2015 • Leave a Comment

When the Netflix Culture deck hit the web some long time period ago it generated some good conversation.  Although I never wrote anything about it at the time, other than posting the link, I found the deck most interesting for the conversations it generated:

  • “Hire, Reward, and Tolerate Only Fully Formed Adults” – a great comment from HBR.
  • “During 30 years in business I’ve never seen an HR initiative that improved morale”
  • “We had no vesting period—the options could be cashed in immediately”
  • Some great call-outs here and here.
  • “Outstanding” employees only. Netflix doesn’t accept anyone who does an “adequate” job (Hastings says those hires often lead to “generous severance packages”).
  • “Freedom and responsibility” vs command-and-control: Employees get to make decisions; managers just give them the right context to do so.
  • No “brilliant jerks.” It doesn’t matter how good you are at the job. If you’re a jerk, you won’t stick around Netflix for long.

Which leads me to the following thought:

Are HR departments an anti-pattern for managers actually being managers.

The Coolness of React Native

•June 20, 2015 • Leave a Comment

Whist in Sydney recently I went to the “Introduction to React Native” Meetup at the News Corp offices.  Both presentations were good, but the demo at the end was enlightening, and force me to return to my hotel, complete the rebuilding of a completely broken OSX, and execute the Getting Started guide over on the React Native site.  React Parts was mentioned in the presentation as being the place to go for appropriate components – although the few components briefly scanned did appears to be missing tests :(

Clearly although React Native is still in its early days it offers some coolness around building native iOS components.  Android appears to be possible with React Native in the future, and one can only assume Apple Watch iOS apps will also be supported


Get every new post delivered to your Inbox.

Join 693 other followers