Design Patterns
Design patterns give you a vocabulary to describe design choices you made. They don't give you a set of things that inform design.
31–40 of 416 posts
Design Patterns
Design patterns give you a vocabulary to describe design choices you made. They don't give you a set of things that inform design.
Don't go too overboard with message queues. There's nonzero development and operational overhead incurred when part of your application takes its input in a weird binary format, and when the data in your queue is thrown away after processing, and when you need to think about scaling of workers and concurrency. If you're not working with real "big data" – and, let's be honest, almost nobody is – I would advise using a…
Doesn't matter what the project is. Could just be tossing around a string of data that eventually gets dumped into the db and sent to the server.
Research different methods of architecting such a system. Code up a few.
By doing this, you will actually find the answer to the question you posed. And, arguably, have fun doing it.
Makefiles. I always dismissed them as a C compiler thing. Something that could never be useful for Python programming. But nowadays every project I create has a Makefile to bind together all task involved on that project. From bootstrapping the dev environment, running checks/test, starting a devserver, building releases and container images. Makefiles are just such a nice place to put scripts for these common tasks…