What I use

Atom

I think I last posted about IDEs almost three years ago, so figuring it was time for an update, over at the Via blog we’ve opted to run the odd post about what tools we use in our day-to-day work.

I’m up first with a brief look at my web / text / JavaScript editor of choice, Atom.

Crikey. Fifteen years of tech and more…

It seems extraordinary to me that I started this website over fifteen years ago now. That’s an awful long time ago when we consider the world of the web and the technology around it. Amusingly (and what a testament to the platform), this site was built on IBM Domino back then, and still is now. There have been a fair few iterations of the site, the most recent incarnation also being the longest in place.

I’m conscious that the site has been pretty quiet the last few years, with just a handful of posts annually, but blogging is not what it was I suppose. I still follow a number of sites in a newsreader, and I still often feel the urge to write: I need to act upon it more often!

Of course, it’s not just about this site alone: I also blog over on the company site, and we have been mighty busy there. Recent work has had me doing all sorts:

  • Java-based migration code for IBM Connections, Microsoft SharePoint, IBM Domino and IBM Quickr
  • Putting together a client library in Java for Office 365 / Microsoft SharePoint (OAuth and all).
  • Lots and lots of JavaScript (node.js, Express, React, vanilla client-side JS, and even the odd bit of IBM-flavoured server-side JavaScript!)
  • Absolutely heaps of Google apps script and Google API work, some of which we expanded on upon recently: Using Google Apps Script with LDC Via.

If any of this tickles your fancy, floats your boat or scratches an itch, then get in touch!

Why we don’t migrate code to LDC Via

I’ve written a short post over on the LDC Via blog which addresses a question we’ve been asked a number of times in the two years since we pushed the “Go Live!” button on LDC Via (at Engage 2015 in Ghent no less): to wit, why don't we migrate application logic, and / or code?

I don’t write JavaScript like I write LotusScript. Do you? Languages have moved on (capabilities, syntax, patterns): what works for VB6-style Lotusscript looks odd in 21st century Java or JavaScript.

Have a read and feel free to weigh in!

Read more: Why don’t we migrate code?

About

I’m a software architect / developer / general IT wrangler specialising in web, mobile web and middleware using things like node.js, Java, C#, PHP, HTML5 and more.

Best described as a simpleton, but kindly. You can read more here.

";