Skip to content

Commit

Permalink
fix featureful -> feature-rich
Browse files Browse the repository at this point in the history
  • Loading branch information
zakirullin committed Jan 17, 2024
1 parent 1a49bed commit 14d401b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ Is this the right way to approach the uncertainty of a new system? It's enormous

A well-crafted monolith with truly isolated modules is often much more convenient and flexible than a bunch of microservices. It's only when the need for separate deployments becomes crucial (e.g. development team scaling) that you should consider adding a network layer between the modules (future microservices).

## Featureful languages
## Feature-rich languages
We feel excited when new features got released in our favourite language. We spend some time learning these features, we build code upon them.

If there are lots of features, we may spend half an hour playing with a few lines of code, to use one or another feature. And it's kind of a waste of time. But what's worse, **when you come back later, you would have to recreate that thought process!** `🤯`
Expand Down

0 comments on commit 14d401b

Please sign in to comment.