Software Dark Ages
A couple of years ago, I worked in a SaaS company that suffered from probably all possible issues with software development. Code was so complex that adding simples changes could take months. All tasks and the scope of the project were defined by the project manager alone. Developers didn’t understand what problem they were solving. Without an understanding the customer’s expectations, many implemented functionalities were useless.
Popular
- The Go libraries that never failed us: 22 libraries you need to know
- Safer Enums in Go
- Common Anti-Patterns in Go Web Applications
- How to implement Clean Architecture in Go
- The Repository pattern in Go: a painless way to simplify your service logic
- Introduction to DDD Lite: When microservices in Go are not enough
Tags
- golang
- go
- ddd
- watermill
- domain-driven design
- events
- ci
- clean architecture
- firestore
- web-applications
- anti-patterns
- cloudrun
- gcloud
- googlecloud
- serverless
- devops
- firebase
- gitlab
- microservices
- reactive
- repository
- testing
- advanced
- architecture
- basics
- building-business-applications
- cqrs
- kafka
- mysql
- nats
- pipelines
- scalability
- amqp
- authentication
- bounded-context
- c4
- cicd
- databases
- design-patterns
- diagrams
- docker
- dry
- e-book
- enums
- event-driven
- event-storming
- frameworks
- gamedev
- generics
- google-cloud
- grpc
- htmx
- javascript
- libraries
- metrics
- monolith
- openapi
- prometheus
- python
- rabbitmq
- security
- software-architecture
- sql
- sse
- strategic-ddd
- swagger
- terraform
- tips
- versioning