Software Architecture

presentation at Developers Katowice

We have a situation where a monolithic piece of software has grown too big for a single team to handle. So the idea is that another team could be responsible for a feature in this project.

What would your preconditions be for multiple teams collaborating on a single software code base?

Hello! illiterate_coder here, Data Architect hailing from the Bay Area. Looking forward to engaging with the community on Lemmy!

In my company (not the post author) we are in the middle of a modernization project. This is a nice article about how to structure the events of this kind of projects where architecture is a key element.

It is not the first time I see workflows like this for modernization (it is far more lightweight than what it looks like) and I always found interesting how easy this is to turn from modernization to feature development.

Hi all. I'm hailing from Belgium, and am an enterprise architect in a reasonably large financial institution. My software engineering and software architecture skills grew mainly from low-level code development for real-time embedded systems (nothing to do with my current employer), and were refreshed through additional training/courses.

My current focus is more strongly towards infrastructure and non-functionals, but I keep a close eye on the software architectural evolutions, to be aware of evolutions and to be ready on infrastructure side for whatever new comes around. And to be able to tell colleague architects that they can resolve things themselves without blaming infrastructure ;-)

I am interested to transition from a software engineer to a software architect. I would like to expand my knowledge on the subject.

What's your must read list? Any books, articles, videos and courses are appreciated.

Right now I am reading Contious Architecture in Practice .

It's a long read, but it's an interesting discussion on how to test API services. It's definitely counterintuitive for me being more familiar with testing pyramid.

I found interesting the section about full-stack boxes, something that I have used in the last 2 jobs I worked on and I confirm the authors consideration about maintenance.

Also, the idea that testing is spectrum between pre-production and production is mind blowing to me. Especially, the metrics provided about how low value pre-production tests are. I wonder if it's a chicken/egg situation where the lack of pre-production testing would increase the number of bugs that would have been found pre-production.

Is this something you are applying on your workplace, please share your experiences and any relevant reading material.

Hi, I'm Joe. Trying Lemmy for the first time, and stumbled upon this. I've been doing software for 30 years. Work in NYC, and think a lot about quantitative software architecture and how it helps business management. From the UK, been in New York for nearly 20 years.

Hello @softwarearchitecture! Good to have a place other than https://reddit.com/r/softwarearchitecture. I'm following from my Mastodon instance of choice, I'm not sure how the interaction will work.

If you've stumbled across this community, drop a reply and let us know who you are.

I'm Bob, a software architecture and craftsman. I've been programming for about 20 years, mostly in web applications, building event driven DDD things.

I wrote a book called Architecture Patterns with Python, and I'm supposed to be writing another about serverless architecture, but mostly I fret about climate change and fix build pipelines.