Have you ever heard of the Luddite Fallacy? It refers to the fear that machines and technology will replace human Labor.
#Technology
sjilla.substack.com/p/the-luddit...

Good lessons:
- Perfection kills progress. Build in small chunks, iterate.
- Relationships, relationships, relationships. Having a strong network is so important.
- The software we are building right now will one day be decommissioned.
#SoftwareEngineering
dev.jimgrey.net/2024/07/03/l...

RAML and OpenAPI (OAS) HL comparison/trade-offs:
- RAML is less complex and allows customized APIs.
- OpenAPI is more suitable for interoperability and compatibility. Great for standard, stable, or compliant APIs.
#API #OpenAPI #RAML #SolutionArchitecture
dzone.com/articles/ram...

This Thoughtworks article 'Technology blueprint for growth' is full of great insights on biz and tech strategies integration, modernization, talent limitations, tech debt control and partnerships.

#TechnologyStrategy #BusinessStrategy #EnterpriseArchitecture

www.thoughtworks.com/perspectives...

Dr Werner Vogels has introduced the "laws of frugal architecture" which come in a website along with podcast episodes which are entertaining to follow. In essence, the frugal architect is dedicated to cost-efficiency and sustainability of architectures.
thefrugalarchitect.com

I liked this quote from the Courage section in which he mentions: "If you already know how you want to solve or accomplish a breakthrough, it’s probably not a breakthrough."
hups.com/blog/hoshin-...
#EnterpriseArchitecture #Strategy

"There are only two kinds of languages: the ones people complain about and the ones nobody uses."

- Bjarne Stroustrup.

😂

"I tend to jest that before everything was running on computers we also did not have a 'paper' department. In digital companies, IT is the business and the business is IT - the two are inseparable."
Gregor Hohpe in 37 things one Architect knows

What better than quoting @martinfowler.com to get a memorable first post. He once observed that "one of an architect's most important tasks is to eliminate irreversibility in software design." - To keep options open as Gregor Hohpe advocates.