Ben Howell

[...] . In the next few articles we'll look at some using Scala and Akka, such as this: Publish/Subscribe using Scala and Akka EventBus TL;DR Just give me the code: GitHub EventStream Let’s build our [...]

[...] in a series on implementing publish/subscribe with Akka and Scala. The first post, Publish/Subscribe using Scala and Akka EventStream covers some facets of Scala and Akka that'll be skipped over in [...]

[...] simple queue. It can also be implemented using actors as shown in a previous article: Publish/Subscribe using Scala and Akka EventStream Pros: decouples caller and callee in both space and time. [...]

[...] each criteria in the affirmative? There seems to be a misunderstanding amongst a lot of software engineers that if you don’t meet the buzzword checklist or you don’t have N years of experience in [...]

[...] reason and can have unknown and devastating consequences. It is for this reason that as software engineers we should always be ethical in the code we write. Notes Reverse engineering, function [...]

[...] are a few common traits that indicate certain people would be quite capable of becoming software engineers and would greatly enjoy doing so as a career. Making If you like making or fixing things [...]

[...] objects” but, yes I do see a similarity between the interests of mechanical and software engineers. The message in other words? OK, so I perhaps wasn’t as clear as I could’ve been in [...]

[...] and unsavoury hiring advice has a habit of getting on my goat as is clear in my rant in a previous article about recruitment. Hiring employees for a given position with a salary that's fair. Of [...]

[...] be implemented using a simple queue. It can also be implemented using actors as shown in a previous article: Publish/Subscribe using Scala and Akka EventStream Pros: decouples caller and callee in [...]

[...] This is a follow-up post to a previous article I wrote: “Should I become a Programmer?” I'd like to address a couple of the comments I [...]

[...] Documentation is the most important part of any system and goes well beyond system design, code comments, technical and user manuals. Any system before it is built should have good design [...]

[...] always be ethical in the code we write. Notes Reverse engineering, function naming, code comments and image thanks to marcan over on EEVBlog. The original source and discussion can be [...]

[...] establish here can be readily applied in UI applications with JavaFX, as presented in: Scripted user interfaces with Nashorn and JavaFX as well as myriad other scenarios, such as plugin scripts for [...]

Java 8 has introduced a bunch of great features and one of the gems amongst those new features is Nashorn. Nashorn is the replacement for the Rhino Ja [...]

[...] . Enough of that. Let’s build our subchannel classification event bus using Akka EventBus. SCEventBus.scala Please explain. Here we’ve created our Subchannel [...]

[...] we'll look at some using Scala and Akka, such as this: Publish/Subscribe using Scala and Akka EventBus TL;DR Just give me the code: GitHub EventStream Let’s build our first example using the Akka [...]

[...] be a well thought through design choice and should be documented accordingly. The plugin developer documentation should very clearly spell out this binding contract (i.e. the required functions in [...]

[...] else. Document all safety systems, redundancy, fail-over and contingency plans. Hardware documentation such as technical and user manuals. These types of documentation are usually supplied by [...]

[...] , a completely redundant power supply in the form of a diesel generator may be used (A). Documentation Documentation is the most important part of any system and goes well beyond system design, code [...]