I had my fair share in designing and building large systems. I've taken part in
rewriting Uber's distributed payment systems
[https://blog.pragmaticengineer.com/distributed-architecture-concepts-i-have-learned-while-building-payments-systems/]
, designing and shipping Skype on Xbox One and open-sourcing RIBs
[https://github.com/uber/RIBs], Uber's mobile architecture framework. All of
these systems had thorough
You must log in or register to comment.
A general programming discussion community.
Rules:
- Be civil.
- Please start discussions that spark conversation
Other communities
Systems
Functional Programming
Also related
- 0 users online
- 5 users / day
- 14 users / week
- 44 users / month
- 138 users / 6 months
- 1 subscriber
- 336 Posts
- 544 Comments
- Modlog
- mods:
- Evan
- @Restioson@lemmy.ml
As someone who has architected software to the point of becoming my company’s official architect simple design is usually the best design, but building software with no design or forethought just leads to spaghetti.
If you want to talk about the costs of having an FTE architect on your team I think there’s a lot of merit - but “architecting” is a hat somebody has to wear and if one of your senior devs spends 5% of their time wearing that hat it’s a good thing.
This article was written by a part time software architect who hates being called a software architect.
Formal Software Architecture is overrated. That should be the title of this, because they clearly designed and architected a system. I’d even go as far and say they came up with their own formal system of how to architect a system.
Anti Commercial-AI license