4 ms·
There's money to be made in the IBM midrange market. The company I work for is still using the iSeries (although we're switching to TOP_5_CLOUD_ERP system as w
by bluedino 11y ago
There's money to be made in the IBM midrange market. The company I work for is still using the iSeries (although we're switching to TOP_5_CLOUD_ERP system as we speak), and we use Apache and PHP to connect to modern systems.
Every year, IBM is at the user conference for the software we currently use. They're always showing off their newest Linux machine with 200 cores and I don't know why, because half the people there aren't even using bar coding, and everyone there is a small fry.
Here's where a niche developer comes in. You can use Java which is supported by IBM, Zend has a nice PHP setup, and IBM's bastardized version of Apache. Want to build an API to interact with this stone age fucker? You can do it. Build a Slack integration and look like a hero. Heck build some crappy web app because it's easier and faster to do development with your favorite framework than it is to do it on the IBM with RPG and whatever the fuck that thing runs. SQL your brains out!
These customers aren't leaving the IBM without investing a half a million dollars into a new platform. Every year, there are less and less people there, but they'll gladly spend $50k to integrate some simple workflow.
Rent a booth for $1,000, give away an iPad or some FitBits and pass out some business cards. Go to 3-4 of these a year and you should be able to keep busy for a while. And you already know SQL, PHP, Apache, you just get to discover the 'intricacies' of doing it on the IBM.
- bencollier49 11y agoYou didn't do that work for a water treatment plant by any chance, did you?
- donatj 11y agoA company I used to work for built online shopping carts. We were building one for an industrial company who's inventory system ran on an AS/400, and we were doing an integration. I had ZERO familiarity with IBM mainframes at the time and presumed (wrongly) that it ran some flavor of UNIX. I was to work with their lead developer to get the integration going. He was maybe late 50s, I never met him face to face, only over the phone. I suggest that they build a "simple JSON or XML API" for us to connect to. This makes their lead very uncomfortable. He does NOT want to put the machine on the public facing Internet (reasonable enough) and has never worked with XML or JSON. He instead wants to set up a system where hourly it would email us CSV diffs. Maintaining data working from diffs sounded like a nightmare to me, plus I'd never programmaticly worked with receiving emails. Whole thing sounded iffy. Plus understanding their data model it would not be shoved into CSV without a fight. After a bunch of back and forth (weeks) we work out a system where the server would upload a combination of CSV and XML to an FTP share we controlled and I could reprocess the data hourly. It actually worked reasonably well. I'm curious if it's still in operation, I've long forgotten the name of the company we built this for, there were just so many.
- beilabs 11y agoI'm almost certain I've worked with the same guy...
- eru 11y agoWhat do you mean by barcoding? Are you talking about retail bar codes? Or is there something mainframe related?