Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
All else being equal smaller ones. But I'd prefer a big, well organised & structured over a haphazard smaller one any day.
-
I prefer one weekend projects. My flaw is that i start over-enginering every time.
MVP should become my thing.
The only thing i like about micro services is that they are easier to complete. Besides that - fuck them too :) -
sorry, I think I like the Big ones, lasting little time.
Think about robbing a bank vs pickpocketing in the crowd. -
Big projects, small pieces.
I've really gotten into developing code as (npm/composer/cargo/cabal/etc) packages.
Spend two days writing an API SDK for example. Write readme/docs, set up a simple CI, publish on package registry. In a private repo if it's specific to our business -- but I also write public & MIT licensed packages very often.
Let other coworkers glue it together, but still get the satisfaction of contributing on a larger project in the long term.
Related Rants

The week before project deadline...
Can we do that??? 😶
What kind of project sizes do you prefer and why? Big one, lasting year(s), or smaller ones, in range of months?
question
size
project