Hiya! Welcome!!!

this is the personal website of a certain tommy p. keane.

if that illustration over there doesn't look like the vegan, Ph.D. dropout, myopic, Scientific Engineer (born in the USA during the 1980s) that you're lookin' for, then you might've stumbled across the wrong tommy. thanks for visiting, though!

but, if this all sounds like the tommy p. keane that you were expecting, then, welcome!, again! this is basically the only site that tommy maintains on the internet(s), so whatever you're lookin' for is probably around here somewhere.

if you'd like to change the site theme, you can use the image/svg+xml (Settings) button to configure the site cookies. otherwise, this is a cookie-less and tracker-less site.

tommy has a personal, public GitHub page full of repositories of free, open-source code that you are (of course) welcome to peruse and use (according to their licenses).

Hopefully, these GitHub repositories are a pretty good (albeit incomplete) indication of the kind of work tommy does -- in case you're here in regards to a career opportunity.

Or, if you're just curious about software development, the documentation and code is usually pretty verbose, and might (hopefully) be a useful resource. 😄

Social Sites & Profiles

tommy doesn't currently have a profile on any of the popular social sites, except for a couple related to professional development. for the sake of clarity, the following is a list of popular professional and social sites. If tommy has a profile there, then a link should follow -- otherwise, if you see somebody there with the same name or likeness, that's probably not actually this tommy.

  • LinkedIn™: nope.
  • Facebook™: nope.
  • Instagram™: nope.
  • TikTok™: nope.
  • Snapchat™: nope.
  • Twitter™: nope.
  • RenRen™: nope.
  • Weibo™: nope.
  • Google Scholar™: nope.
  • HackerRank™: tommypkeane

Work Opportunities

tommy is currently employed full-time as a Machine Learning (ML) Infrastructure Engineer, working (remotely) for a Boston-area SaaS Startup.

tommy is not actively job-seeking, but if you want to see a non-redacted resumé or have any questions, just click on the little help button to see our contact info, and feel free to reach-out anytime.

After being being furloughed due to the SARS-CoV-2 Pandemic, tommy accepted a "Separation Agreement" and was unemployed from April through August 2020 -- taking the time to career search, continue developing DevOps and Software Engineering skills, and finally starting (and organising) the projects you now see on this updated site.

for the sake of anonymity and to encourage a personal-professional disconnect, the names of tommy's current and previous employers have been redacted from this site, but you can look through the Business (CV) page(s) to learn about tommy's work history and relevant technology skills.


tommy is a native speaker of American English, and it's the only language tommy is actually fluent in. one thing to watch out for, though, is that tommy tends to use British English spellings (double L, S instead of Z, extra U, and all that) with maximum effort and occluded reasoning. there's also a bit of a Bostonian influence, so tommy may do an ah instead of a u, or probably add an r to make things easier to pronounce. oh, not really a warning; but there is, of course, an accurately abundant use of commas. and as some thievery from academic writing, most of this site is written in the third-person plural (we, us, our, ...), even though it's just me, here, alone, again, naturally.

tommy tries to use they/them in any creative, explanatory, scientific, or professional writing; so as to be neutral and inclusive. tommy will legitimately be happy to be referred to by any pronouns you wanna use -- most likely order of preference: they / he / she. tommy doesn't have anything “figured out”, tommy's a pacifistic vegan, and probably a paranoid solipsist just tryin' to remain anonymous.

SaaS: Software as a Service -- a type of commercial software where clients subscribe to access a web-application, and when they end their subscription they (typically) lose access to the application.

e.g., “We sawr it...” instead of “We saw it...” -- very much like the phonetic Liaison in the French Language.