Posts about:
The majority of applications for the AECO (Architecture, engineering, construction, operation) industry are desktop applications (primarily MS Windows© based). These applications tend to be expensive in cost, especially so today with ‘subscription’ modes of licensing becoming more common.
A few months back, my wife and I moved to Spain from Argentina. Last week, my colleague Mike joined me here, as well as our two first local hires, new members of our software team. I was extremely excited, I’ve been working solo here in Spain now for several months, so it was nice to get a chance just to speak to my colleagues face to face for the first time in 18 months or so.
Especially in the last year, there seems to be no shortage of issues to solve in any organization. While we grapple with our internal challenges, we are also helping our customers transform their businesses. In all these experiences, a constant that we always return to is the problem definition. Understanding what we're trying to solve before we tackle it helps us prioritize and efficiently implement.
In our last few posts, we introduced you to our ecosystem design principles and the platforms we chose. Implementation can always be more perfect, and just as we changed a lot internally in the last 5 months, the next year will hold even more surprises for us. We know you are going through similar changes, so this is of how we formed an architecture for our data ecosystem.
I can remember my days in chemistry class when everyone would have to either partner up to complete an experiment or go at it alone. At the beginning of the school year, students would quickly grab a partner and, for the most part, pick someone from their inner circle of friends. I would be a little more "tactical" when choosing partners for a couple of reasons. First, there were classmates of mine at the time that were taking more advanced classes and had more experience that made them great partners. Second, I knew that partnering up would be a much more efficient way of attacking the assignment as one could "guide" and explain the desired outcome, and the other person on the team could perform the actual experiment and execute it.
A team of technologists, engineers, and architects, we’re brought together by the belief that technology has a systemic impact on the future of our cities. Our team of industry veterans aims to change the way we build.
