What I’ve often noticed is that javadocs are kind of treated as a second class citizen when it comes a lot of opensource projects; not all projects, there are some with excellent javadocs; but, sadly, more often than not javadocs are an afterthought. Now, I’m as guilty as the next person for not having great javadocs; but you can spruce up your javadocs with some pretty UML diagrams courtesy of plantuml, graphviz and umldoclet…

I try to be consistent in my development environments since they are spread across a number of platform: Windows, Linux and latterly Mac because McAfee sucked the performance out of my corporate issued laptop. I’m one of those odd people who happens to use all 3 major platforms actively for development. Scripts have always been bash, which means that I need to be able to run bash on my Windows systems; a long time ago it was Cygwin, but I found I didn’t need many of the features that it provided so I ended up using the bash that’s provided by Git for Windows; I have found that I need rsync to be available to make vagrant provision machines properly. I also like a bit of Windows subsystem for Linux so I have the choice of either installing my tools via scoop.sh or sudo apt-get. Sadly scoop hasn’t persuaded me that powershell is my goto shell.

Should you do it now or should you do it later? Strike while the iron’s hot or wait and see? In the context of development, this isn’t always an easy decision. You may not have the bandwidth or resources to finish that uber-feature right now when you have customers breathing down your neck about bugs that really should be classified as feature requests. You can opt to develop a solution that is tactical and not strategic; deferring those strategic decisions until some later time is a perfectly valid and meaningful form of planning. The biggest issue with deferring a decision is that circumstances can take the momentum away from you, and dictate any future path that you can take.

Unit tests are good; that’s the accepted truth and you won’t find many developers that disagree with that statement. Yet we live in a world where there are projects running in production that don’t have unit tests. In fact, having crap tests, like having unmaintained documentation, is, in any reasonably complex codebase, arguably worse than having no tests at all. What then is the point of unit tests? Subjectively, I find that unit tests can be used as a measure of understanding what you’re trying to deliver.

I’m a long time Microsoft DOS/WFW/95/NT/2000/XP/Vista/7/10 user on the desktop; I can make it sing and dance exactly to my tune. Where other people complain about Windows, or get frustrated by it; I never have a problem. Now, Windows isn’t perfect, far from it, but it’s a basically a tool that causes me minimal friction, letting me get on and solve interesting problems; I don’t use it in production, just for my desktop. Last summer, I got so annoyed with the corporate build of Windows 10 that I submitted a requisition for a Macbook Pro; I’m not actually sure which model it is, but it has a touch bar and 16Gb of RAM. Now that I’ve been using it for about 5 months I thought I’d jot down my thoughts about the transition. My last long-term experience of the Mac was back in 2007/2008; does it create more or less friction a decade later?