Thanks for all the feedback! To address some of the key points in the comments:
1. Completely agree learning the fundamentals is important. I did mention groking the underlying CompSci in the article.
2. The market has generally decided that an AI Engineer is an engineer who is proficient at applying AI in the products they create – not somebody who uses AI to create the products. This article used the former as its example, not the latter.
3. Completely agree that an engineer in the upper right quadrant could just as well be a fundraiser and founder, too. If that's what they want, more power to them. In any event, I love creating a culture on my teams that gets engineers routinely thinking like customer-centric founders. Which brings us to...
4. I don't view prioritizing new technologies as hype-chasing. There's an enormous amount of EQ required to understand which technologies are likely to be a net positive vs. negative to a marketplace and the customers that comprise it over the long-term, hence the point about customer-centricity. 20-30 years ago, I was all in on dyanmic web technologies but wasn't investing time or energy into Flash or Java applets. I was, generally speaking, never a proponent of NoSQL or microservice architectures, but did love iterative improvements to SQL databases and the advent of cloud-native platforms. For the past few years, I've been all in on LLMs but never bothered to dabble in blockchain, Web3, NFTs, or the metaverse. There's a reason for all of this contrast, and it's grounded in focusing on what actually drives outcomes for customers, not just what's trending. It comes down to making intelligent bets on the future.
We use Angular over at zenginehq.com. Not only did we build an entire business process management platform on top of it; we even exposed a JS plugin architecture that allows developers to create Angular plugins on top of the platform. Really cool stuff.
Sure, Angular has its flaws & quirks, just like any framework. But it gets so many things right that it's worth sticking with it, IMHO.
Thanks for the feedback! My name is Anthony Putignano, VP of Engineering at WizeHive.
Zoho Creator is great and indeed the functionality is similar. One point of differentiation we're particularly excited about with Zengine is the JavaScript plugin architecture: https://zenginehq.github.io/developers/plugins/ Using plugins, a developer can extend the Zengine interface with new mini- and full-page- UIs. Please check it out! We're looking for feedback on the idea & technical implementation.
WizeHive's mission? Empower business users to get customized business apps up and running in under an hour.
We're hacking on an AngularJS frontend with a plugin architecture. This talks to a CakePHP & MySQL backend with a splash of node.js, MongoDB, and more.
Thanks for all the feedback! To address some of the key points in the comments:
1. Completely agree learning the fundamentals is important. I did mention groking the underlying CompSci in the article.
2. The market has generally decided that an AI Engineer is an engineer who is proficient at applying AI in the products they create – not somebody who uses AI to create the products. This article used the former as its example, not the latter.
3. Completely agree that an engineer in the upper right quadrant could just as well be a fundraiser and founder, too. If that's what they want, more power to them. In any event, I love creating a culture on my teams that gets engineers routinely thinking like customer-centric founders. Which brings us to...
4. I don't view prioritizing new technologies as hype-chasing. There's an enormous amount of EQ required to understand which technologies are likely to be a net positive vs. negative to a marketplace and the customers that comprise it over the long-term, hence the point about customer-centricity. 20-30 years ago, I was all in on dyanmic web technologies but wasn't investing time or energy into Flash or Java applets. I was, generally speaking, never a proponent of NoSQL or microservice architectures, but did love iterative improvements to SQL databases and the advent of cloud-native platforms. For the past few years, I've been all in on LLMs but never bothered to dabble in blockchain, Web3, NFTs, or the metaverse. There's a reason for all of this contrast, and it's grounded in focusing on what actually drives outcomes for customers, not just what's trending. It comes down to making intelligent bets on the future.
Cheers!