Naming things in software engineering is difficult, so I pondered what to call this blog for a long time before naming it. I came up with boundary waters for a few reasons:
- I grew up near the Boundary Waters Canoe Area, and I have a lot of great memories visiting that majestic part of Minnesota.
- Software development has a lot of topic areas that are related to boundaries and it was a common theme in a lot of the initial topic areas I'm planning on writing about.
- There are a lot of different boundaries at the BWCA that I can use for analogies:
- The US - Canada border
- Lakes & islands
- The water itself
- The .dev domain became available and it's very unlikely to get confused with the actual geographic area.
I'm starting this blog on the one-year anniversary of changing jobs. I left a company in the telecommunications industry I had spent over 26 years at to go work at Visa. I now have a systems architecture role that does not include coding on a regular basis. I decided I needed an outlet for the coding I was no longer doing and this is it.
I'm new to blogger.com, so expect things to change as I learn it's features.
Comments
Post a Comment