One of our goals at A3J is to share, specifically information. We’ve never found it very useful to keep the cards close to our chests, and we’ve always had a great admiration for those who aren’t afraid to put it all out there without regard to profit or fame. The simple good will of getting information out that could help someone else is very uplifting. With each blog article, we are paying it forward as a result of benefiting from other’s good will in the past.
We wrote our first blog piece in December of 2016, more than two years ago. Hard to believe. Like any new company with all of the players wearing too many hats, blog pieces were a scarcity, only happening sporadically and without planning.
Then one day we wrote the article that would go down in A3J lore as the lightbulb moment. It was a little article on SSL and how to create a secure connection thereby protecting your Maximo environment. It was an issue we had struggled with. We knew many others who had as well. So we wrote something on how we went about this task. Needless to say it took off.
From then on we got serious about writing and recently we’ve created an internal initiative to make the writing more consistent. As with any company filled with techies, the elation was vast, and their pens began to scrawl poetic words to rival Fitzgerald. We jest. Some came more willingly than others to the writing table, but everyone could appreciate putting out helpful content that made someone’s job somewhere a little easier.
So look for these blogs to post on the first Thursday of the month with the first one starting in April. Many will be technically oriented but it’s all hands on deck and everyone will be writing an article. Along with the technical articles, some will have a marketing focus or a professional services/management focus or brand new to EAM/Maximo deer in headlight focus. Either way we hope they are helpful, insightful and maybe even occasionally entertaining. In the meantime, check out all of our blog articles at www.a3jgroup.com/a3j-group-blog
