|Latest 7 Posts
| Change is in the Air|
Fri, Sep 1st 2017 3
| Open Source Contribution|
Fri, Jun 16th 2017 4
| Docker Quick Tips|
Fri, Apr 28th 2017 2
| Notes in 9: Dev Tools Grab Bg|
Tue, Apr 4th 2017 3
| Custom JSON Serialization With GSON|
Mon, Jan 23rd 2017 5
| Recapping 2016|
Mon, Jan 16th 2017 4
| Rebirth: An App of Ice and Fire|
Wed, Dec 14th 2016 7
| Building Java Objects From JSON|
Thu, Jan 22nd 2015 9
| Notes in 9: Docker + SonarQube|
Wed, Feb 24th 2016 9
| When You Need a Comparator|
Fri, Jan 9th 2015 7
| Manually Renewing HTTPS w/ Let's Encrypt|
Wed, Jul 27th 2016 7
| Rebirth: An App of Ice and Fire|
Wed, Dec 14th 2016 7
| Server REST Consumption with Authentication|
Mon, Aug 18th 2014 6
| Variations on a Function: XPages Calendar Picker Improver, a Dojo Version|
Wed, Aug 13th 2014 6
| A Quick Talk|
Mon, Jan 12th 2015 6
| Nerdy Yet Awesome|
Fri, Feb 26th 2016 6
| Site Anchors|
Wed, Jun 1st 2016 6
||SCM Survey Results
The TLCC + Teamstudio webinar today is “Getting Started with the OpenNTF Domino API”, presented by Paul Withers and Jesse Gallagher. I’ve been listening/watching while working and if you’re looking to ease your pain with some of the idiosynchrises in XPages, you’ll want to check out the webinar (a recording of the webinar should pop up before long, I’ll link to it here) and give the OpenNTF Domino API a go.
Last week, I put out a few toughts out in regards to source control management (scm) and even included a single question survey.
Here is the main donut chart, which is the same from my previous post, which have been live updating, as they’re published from right in Google Docs in the response spreadsheet I set up.
With a total of 53 unique responses (so far as I can tell), I feel like this was a pretty good turn out in number of votes. Here’s the break down; note: I’ve omitted CVS (concurrent versions system), with 0 total votes.
|file system copy
I think it’s not a huge surprise that git took first place; it’s ubiquitous and used by lots of people. It’s especially relevant, IMO, as GitHub is exclusively git and Bitbucket does both git and Hg. Teamstudio Ciao! had a pretty good showing as well, which probably reflects the demographics of my blog readers; I had to convert one value of an “other” entry which was a write-in of Ciao. Mercurial (Hg) turned out decently as well, though behind the first two. We had a couple of svn fans as well. There are pros and cons to each scm, which is why I don’t believe this to be a fight or even much of an argument, just a question of what’s most valuable to the developer and their development team.
For a clearer overall picture, I summed the values of those using a dvcs (git or hg) to a value of ‘distributed’, those using a centralized version control system to a value of ‘central’ (this includes Teamstudio Ciao responses, as it requires a check-in, check-out mechanic), those using a file system copy to a value of ‘questionable choices’ (it’s better than nothing I’ll grant you, but you could be doing so much more), and those with none to ‘living dangerously’. Those results, in table and pie chart form:
If you’re one of those file system copy or ‘none’ folks, I seriously hope you’re at least making use of Domino Designer’s built-in ability to compare versions, which only requires you perform the “Set Up Source Control for this Application…”, without needing to commit or track it anywhere. It’s a handy feature and worthy of use, esepcially for those of you I deemed to be making “questionable choices” (making a file system copy) or “living dangerously” (‘none’).
All in all, if you’re a hold out against using an scm, I think you’ll notice that I’m skeptical of your choice in the matter. The advantage of using an scm is, I hope, self-evident. You can store your changes as revisions with minimal overhead to your development process; you can relate your revisions to issues (features, bugs, etc.), often with a simple addition to your commit message (refs, fixes, closes) if you’re using something like GitHub, Bitbucket, GitLab, or others; and then there’s the confidence in knowing that no matter what you change, you can always roll back to a previous commit (or tag or release) and know that your code will be as pristine as it was when you knew it was working, all by a simple command (or button click, for the GUI fans).
All in all, thanks for the interest and the feed back. It’s always nice to know what others think on a matter. As usual, write better code! :beers:
Apr 12, 2016
| Recent Blog Posts
Change is in the Air|
Fri, Sep 1st 2017 1:00p Eric McCormick
I’m Back What Can I Say? In Case You Missed It If you find yourself asking “where was Eric?”, this should summarize it all: Instead of trying to do everything all summer, I tend to take a break from blogging and a lot of open source endeavors over the summer. It means I can focus on family time along with yard and house projects. Ah... Summer That’s all paid off and, with fall fast approaching, I’ve found myself wanting to start those things back up; ramping up into winter when
Open Source Contribution|
Fri, Jun 16th 2017 5:00p Eric McCormick
Intro It’s time to clear some of the backlog. I started this post a few months back and it should probably be sent on its way to clear the pile of drafts I haven’t finished yet… 🤔 I have a bit of a passion for open source software. My preferred distribution of Linux has been Ubuntu since 4.10, the Warty Warthog (I was even a minor contributor on a short lived, wildly popular project that aimed at improving the Ubuntu experience early on), I’ve enjoyed most open source projects I’ve
Docker Quick Tips|
Fri, Apr 28th 2017 3:00p Eric McCormick
Docker If you have been living under a rock, Docker is pretty much amazing. If you haven’t been living under a rock, you may be getting used to the idea of Docker, but still have the occasional question. I’ve found myself using Docker in increasing amounts and complexity over the last year or so. I’ve recently decided to start recording some of the tasks I’ve found useful, some of which may be less familiar to a beginner. If you’re so inclined, check out the playlist, embedded here.
Notes in 9: Dev Tools Grab Bg|
Tue, Apr 4th 2017 1:00p Eric McCormick
Intro I’m on Notes in 9 again, with a “grab bag” of a couple of tools I’ve put together recently that may be of a varying degree of useful for other Domino + XPages developers. You don’t need these to do development, but for the right person, they may help with their development workflow. Also of note, with the upgrade to Swiper with the FP8 release of Notes + Domino Designer, the limitations previously mentioned are no longer there! This means that my second tool I talked about, node-
Custom JSON Serialization With GSON|
Mon, Jan 23rd 2017 2:00p Eric McCormick
Mon, Jan 16th 2017 3:00p Eric McCormick
Per usual, I’ve had a little break between things and decided to catch up with a bit of a summary of some recent things that each didn’t necessitate their own post.
2017 IBM Champion
For starters, I’m honored to be named an IBM Champion in Collaboration Solutions (/ Social Business) for the third time. This would be a hat trick in (ice) hockey 🏒. I’m happy to be recognized with a group of people, developers and more, who are passionate about both their work and the plat
Rebirth: An App of Ice and Fire|
Wed, Dec 14th 2016 4:00p Eric McCormick
If you read my blog for any of the Saga of Servlets series, then I hope that you’re excited I’m returning to the application I put together for it. This time, it’s as a conversation piece in regards to some of the build process modernization I engaged in recently, in order to unify the code base in its git repository. In any case, it’s helping pave the way forward before I update some of the back-end elements, when it will again be a talking point for some additional rework and
Scripting Server Upgrades|
Fri, Nov 11th 2016 2:00p Eric McCormick
This one might be slight departure from my usual, but those that have followed my blogging this past year will have noticed a bit more of a leaning towards DevOps in some of my posts. This echoes a lot of what I’ve been concluding as increasingly a necessary part of development; that we need to consider a picture large enough to encompass the themes surrounding development functions and, like any good developer (DRY ~= “lazy”), automate the heck out of it.
I had p
Everything Old is New Again|
Mon, Oct 24th 2016 8:00p Eric McCormick
Every so often, it’s good to reassess one’s position. This is good from both a standpoint of being inquisitive and even interrogative, but when it comes to the ever changing landscape of the front-end development space, it’s not only inevitable, but must be embraced for what feels the need to “stay afloat”. I’m changing theme of my blog, hopefully for the better. The previous theme was good and did a great job of getting things started, but while I had forked a copy of a good
Thu, Oct 20th 2016 8:00a Eric McCormick
If you’re just here to learn a little about how to “squash” commits with git, skip down a ways. Otherwise, hold on, and I will catch you up on a couple of personal notes before we get there.
On the Blog
It’s been a little while since I blogged last. This has been due to a combination of reasons; specifically, I’ve been busy with:
my family, it was the end of summer with lots of things going on
a number of projects around the house (a deck removal and basement remodel