Ilyos shares

- Large codebases are worth working in because they usually pay your salary
- By far the most important thing is consistency
- Never start a feature without first researching prior art in the codebase
- If you don’t follow existing patterns, you better have a very good reason for it
- Understand the production footprint of the codebase
- Don’t expect to be able to test every case - instead, rely on monitoring
- Remove code any chance you get, but be very careful about it
- Make it as easy as possible for domain experts to catch your mistakes

There is coffee all over the world. Increasingly, in a world in which computing is ubiquitous, the computists want to make coffee. Coffee brewing is an art, but the distributed intelligence of the web- connected world transcends art. Thus, there is a strong, dark, rich requirement for a protocol designed espressoly for the brewing of coffee. Coffee is brewed using coffee pots. Networked coffee pots require a control protocol if they are to be controlled.

Eventually, years in, this will culminate in overnight success. You’ll have achieved something that seems magical – impossible, even.

It just takes some time.

You can always find people who are more extroverted or introverted than you. Instead of hiding behind some sort of pride in a personality trait, you should recognize the necessary skills and learn them, especially at work. That being said, slow thinking and collaboration goes a long way.