Ever wondered how Alan reimburses health claims so fast? Spoiler: we automated 70% of document processing.
We just dropped the first article of our doc processing series — stay tuned for more on how we're scaling this across other countries and use cases. https://t.co/DaEsUjQu4j
At Alan, we don't look for N years of experience on our stack when we hire. Many engineers discover our tools as they go. In this article, @nicoolas25 shares his experience on such a transition.
https://t.co/vIQoQ8ptnl
We've already written about how we build tailor-made insurance products. During our last hackathon, we worked on optimizing the way we interact with this builder! From business needs to mathematical modeling, read more about this Alan project
👉 https://t.co/pbgV4NTYy7
How we improved our Python backend start-up time
https://t.co/lUGxFRD4gK
1⃣Move code out of init files
2⃣Break down big files into smaller
3⃣Switch to relative imports for costly modules
by @emmgoldblum#Python
When we speak with engineers outside of Alan, we often get the same questions around our organisation and our way of interacting within the company. Basically, how is the day to day job of an Engineer at Alan? https://t.co/PuGqHKlcon, by @agerlic and @El_Picador
@AdamChainz@alanengineering Thanks for your question ! To name a few : we have one checking that our https://t.co/rxEH3EM4Rs files are empty, another one that we use relative imports (or inlined imports) for our logic/services in some files (typically controllers or commands).
At Alan, engineering teams run without manager. But not without leaders! This article sheds some light on our crew lead role. Enjoy the read! https://t.co/Kobp6mShzS