Oh, that's going to be interesting. AWS is not exactly known for ease of use and user experience. Excited to see what they come up with to make it more usable. Thanks for sharing!
s
shalabh
01/16/2019, 7:54 PM
Interesting. I'm reading https://josjong.com/2018/11/16/my-book-about-vertically-integrated-architecture/ which I find an interesting approach and very much along the lines of how I've been thinking about reducing the complexity and pain in large systems. One core idea is you have a single high level system-wide 'conceptual data model' rather than a tier and language specific data models that essentially are variations of the same data.
a
Aidan Cunniffe
01/16/2019, 8:40 PM
That’s an interesting idea — for the most part I buy in. One could then argue that amazon is by far the best positioned to bring about this change. Should be fun to watch
i
Ivan Reese
01/17/2019, 6:11 PM
I'm really interested in this, but I have a weird hunch that it's going to be DOA. For instance — what programming system/language that any of us use or hear about on a regular basis was initially created with the simultaneous effort of 50 engineers?
Everything I can think of was the product of a small handful of people.
Ivan Reese
01/17/2019, 6:13 PM
Tools like Visual Studio, sure, they could utilize the effort of 50 people. But that's not a language, it's a tool that has to integrate with a ton of other tools. And yes, anything that unifies AWS needs to integrate with all the pieces of AWS... but that's just wrapping up a bunch of APIs, not an effort-intensive large scale task.
s
shalabh
01/17/2019, 9:05 PM
Is it possible it started really small within Amazon and then grew to 50?
i
Ivan Reese
01/18/2019, 5:48 PM
What would those 50 engineers be doing?
s
shalabh
01/18/2019, 6:11 PM
Writing code to integrate with the plethora of AWS syste... oh I see what you are saying.
shalabh
01/18/2019, 6:14 PM
BTW, retro-fitting 'low code' layers on top of code heavy systems tend to have very hard limits. It's got to be designed in from the start.