Approximately a year has passed since Salesforce announced the new Lightning experience. And what a year for Salesforce! At first I thought ‘this is going to take a while, there’s going to be a learning curve, probably known bugs to deal with’, we tentatively started switching on the New Lightning Experience to play around with the new User Interface. In a short while we tested some visualforce pages embedded in the new Salesforce application. Finally, this summer we made the leap to building the first Lightning components and Lightning application.
Lightning Components Framework: https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/intro_framework.htm
Open source Aura Framework: http://documentation.auraframework.org/auradocs
One of my favourite series as a child was ‘The Flash’. He could miraculously find himself from his home dressed in pyjamas, down the street in front of a shop window within seconds. When I built my first Lightning app this year, the images from ‘The Flash’ running around with the speed of light immediately came to my mind. Three words: fast, simple, beautiful. No wonder they named it Lightning. Continue reading “The Year of Lightning”
Update: Since writing this blog I’ve learnt that there may be a better approach to this problem. These days, Neo4j allows you to make indexes on numeric properties and run range queries that use the index. We can take advantage of this for dates by storing them as millisecond timestamps, allowing us to perform date range queries without the need to maintain a time tree.
If you’re aware of this and still vaguely interested in time trees from an academic point of view, by all means read on 😁.
The new and improved FT website, launching 5 October, has many exciting and engaging new features, one of which is the subject of my own team’s focus: myFT.
Continue reading “Adventures with Neo4j and Timetrees”
Recently we had two new graduate engineers join the FT Technology department. We asked them to tell us about their first impressions of the FT and their own individual teams they have started working in. Continue reading “My First Week At The FT As A Graduate Engineer”
Fresh faces in FT Technology – Our rotating graduate scheme
Over the past year we’ve been working hard to establish a graduate recruitment scheme for Technology. We’ve taken on grads in the past but in defined roles and wanted to focus on broadening our scope to help talented people get into technology and experience the range of disciplines across engineering.
Continue reading “Swapping Mortarboards For Motherboards”
This week, on 13 September, FT Technology hosted Codebar.
codebar.io are an organisation who run coding workshops which teach and help underrepresented groups (women, BAME & LGBTQ) get into tech. Continue reading “FT hosts Codebar”
In 2015 the FT replaced its monolithic subscription and entitlements system – replacing it with a platform of microservices and APIs (Find out more here). This provided the FT with a modern, scalable platform for managing our users and subscriptions on FT.com.
Continue reading “Putting Jetpacks On Our Membership Platforms; How the FT made message processing near real time in salesforce.com”
Earlier this year, I joined FT’s membership team as a Java Developer. On a typical day, the membership team are responsible for developing and maintaining a series of microservices which provide APIs for FT to manage its subscribers through our various mobile platforms. This includes setting up new subscriptions on the FT site/mobile app, which our web application services are able to handle and ensure customers are successfully subscribed and more importantly, have access to content they are paying for. Continue reading “The Bootcamp Experience”
Varnish Software has awarded the Varnish Award for Innovation to the Financial Times and its architecture team. The FT uses Varnish Cache to implement multi-factor email login for employees to help protect against the increasing threat of phishing attacks. Continue reading “FT Wins Varnish Award”
Developing microservices with RESTful APIs means a large amount of testing will involve hitting endpoints and checking the results. From the tester’s point of view, this is a lot of doing the same thing over and over, hitting the same endpoints over and over.
As a result we concluded that automated tests was the way to go. We collectively decided to go with BDD style testing to make it easy for anyone to understand the test output. Continue reading “Automated API testing”