Interview Prep
Write documentation without leaving your IDE. Preview your docs locally before publishing them. Collaborate using a version control system. Publish with confidence using automated builds.
Architect Talking Points (Banking)
Use @Transactional for atomic operations.
Prefer blocking JDBC for mature driver ecosystem.
Use optimistic/pessimistic locking.
Enable audit logging.
Use circuit breakers for downstream services.
Use centralized logging (ELK).
FAANG systems prioritize:
Massive scale
Latency
Elasticity
Event-driven architecture
High concurrency
Writing technical documentation
When writing technical documentation, it needs a team effort where everyone contributes and collaborates. For the content you write, you want to be able to publish for different audiences in different target formats like static HTML pages, in-line help or PDFs.
Why to use AsciiDoc and IntelliJ
The AsciiDoc format allows you to write your content once and automate its publishing using standard build automation tools.
The IntelliJ family of IDEs like IntelliJ IDEA, GoLand, WebStorm or PyCharm allows you to efficiently navigate and edit your content. It allows you to collaborate with other developers writers using version control systems like Git.