5 ms·

> I also find it really sad that a lot of the small teams who are on the road to success get distracted by applying "best practices" that were built for big tea

> I also find it really sad that a lot of the small teams who are on the road to success get distracted by applying "best practices" that were built for big teams (e.g. Google uses kubernetes, we should too). Totally. It takes some experience and maturity to be confident enough to resist the big business “best” practices. That, or a very intuitive entrepreneur

Aperocky 4y ago
Simple is better than complex. Frame this quote on the wall beside the monitor, things will magically (simply?) improve.
- andreareina 4y ago
  The good kind of simplicity is hard. I’ve seen (and built) a bunch of things that were too simple and consequently underpowered for the task at hand[1]. Then there’s the issue of, ok this thing definitely needs to be done; do we do it in this module or in that one? This is all separate from the tendency to conflate simple with what’s easy [2]. [1] <rant>poetry doesn’t understand that when I ` poetry add foo` I don’t want the latest version, I want the latest version that is compatible with the rest of my declared dependencies, especially my declared Python version</rant> [2] https://www.infoq.com/presentations/Simple-Made-Easy/ https://www.infoq.com/presentations/Simple-Made-Easy/
  - TeMPOraL 4y ago
    > <rant>poetry doesn’t understand that when I ` poetry add foo` I don’t want the latest version, I want the latest version that is compatible with the rest of my declared dependencies, especially my declared Python version</rant> IIRC, the command was $ poetry add foo most recent \ which fits this crowd most decent
- arkh 4y ago
  I prefer "simple is not easy".
- imetatroll 4y ago
  If only. My experience is that most mediocre programmers don't know how to think for themselves.
- noirscape 4y ago
  Another good one is YAGNI. You Aren't Going to Need It. Basically, don't optimize for standards you'll never actually need. If you're writing say, a webapp that at most is expected to serve maybe 100 to 200 users from a single deployment, you don't need a full blown serverless stack with half a dozen microservices to handle all your requests, just get a decent VPS, configure both nginx and the server workers properly and consider caching the database heavy requests using say, memcached. Throw in a round-robin of multiple deployments "as needed" and unless you're hitting "big social media company" levels of traffic and you can scale up to pretty insane degrees.
steveBK123 4y ago
You also need to prevent your tech management from going to stupid tech management consultant conferences where they get fed this garbage

Aperocky 4y ago

Simple is better than complex. Frame this quote on the wall beside the monitor, things will magically (simply?) improve.

andreareina 4y ago
The good kind of simplicity is hard. I’ve seen (and built) a bunch of things that were too simple and consequently underpowered for the task at hand[1]. Then there’s the issue of, ok this thing definitely needs to be done; do we do it in this module or in that one? This is all separate from the tendency to conflate simple with what’s easy [2]. [1] <rant>poetry doesn’t understand that when I ` poetry add foo` I don’t want the latest version, I want the latest version that is compatible with the rest of my declared dependencies, especially my declared Python version</rant> [2] https://www.infoq.com/presentations/Simple-Made-Easy/ https://www.infoq.com/presentations/Simple-Made-Easy/
- TeMPOraL 4y ago
  > <rant>poetry doesn’t understand that when I ` poetry add foo` I don’t want the latest version, I want the latest version that is compatible with the rest of my declared dependencies, especially my declared Python version</rant> IIRC, the command was $ poetry add foo most recent \ which fits this crowd most decent
arkh 4y ago
I prefer "simple is not easy".
imetatroll 4y ago
If only. My experience is that most mediocre programmers don't know how to think for themselves.
noirscape 4y ago
Another good one is YAGNI. You Aren't Going to Need It. Basically, don't optimize for standards you'll never actually need. If you're writing say, a webapp that at most is expected to serve maybe 100 to 200 users from a single deployment, you don't need a full blown serverless stack with half a dozen microservices to handle all your requests, just get a decent VPS, configure both nginx and the server workers properly and consider caching the database heavy requests using say, memcached. Throw in a round-robin of multiple deployments "as needed" and unless you're hitting "big social media company" levels of traffic and you can scale up to pretty insane degrees.

steveBK123 4y ago

You also need to prevent your tech management from going to stupid tech management consultant conferences where they get fed this garbage