Archive of Software Engineering
Dart: did Google miss the bull’s-eye?
The vocal portions of the Web that care about such things seem to have already made up their minds about Dart, the new web programming language from Google. My opinion of it has been flipping between intrigue and tedium. Maybe you don’t even know what I’m talking about so here’s…
Read More
High Frequency Trading How To
I stumbled across an interesting new blog about High Frequency Trading recently. WK’s High Frequency Trading How To covers some of the technical aspects of software and systems that handle high frequency trading from someone that has worked in the area. Hopefully the blog will continue with regular posts and…
Read More
CSS Sprites and the Jigosaurus
As mentioned before, Jigosaurus is a multiplayer jigsaw puzzle that is played through a web browser. When Aleksei, Yasser and I joined as part of the Caplin Graduate Scheme, we were given the task of getting it running and improving it, and today we’ll be looking at the client facing…
Read More
What does software look like?
As software engineers we work with substance which can neither be seen, smelt, touched, heard nor tasted. One might argue that we “see” the code, but in reality, our source code is no more than the instructions that we give for something to be built; we see the blueprints, but…
Read More
If you can’t think of a good name, use a bad one
I’ve just read a great tweet from @KentBeck that provides an interesting solution for something that I have always struggled with. if you don’t have a good name for it, give it a bad name. a really, really bad name so you’ll fix it later. Good naming is hard Sometimes…
Read More
What’s in a Persona?
Personas are a tool we use at Caplin to help us REALLY understand who our users are and engage everyone in the company in building something compelling that will delight our users. No I am not talking about a sexy, gimmicky UI which when first stumbled upon people go “Wow”….
Read More
The beauty of small tests
When tests are small, a test failure means just one thing – somewhere in these ten lines of code which are being tested, there is an error. Ok, sometimes this can mean that there is an error in the test script, or a there is a failure, or change of…
Read MoreAgile – Tests = Fragile
The nature of agile projects, with lots of small releases mean that there are a lot of test runs to execute if you want to have any confidence in the code and the product. Ignoring this testing just generates projects which will fail – not may fail – will fail,…
Read MoreWeekly Activity
Loading ...
