I have around 13 years of experience out of which most of it is individual contributor building analytical engines for unstructured data and improving ingestion formats for performance. I have worked on Parquet, Lucene and Arrow. I have good experience with distributed Systems design. On the language front, I have mostly worked with JAVA and Scala.
You can call it conspiracy theory but I believe that US/Russia and many other countries gonna benefit out of it by selling arms as most countries started increase their defence budget.
Distributed System Engineer | Remote (India) | Full-time | https://loconav.com/
LocoNav, a Sequoia Capital backed fleet-tech startup, is looking for passionate developers to join our software development team. With presence in 25+ countries and market leadership in India, we recently raised a Series B for $37Mn. We are now growing exponentially and want to work with awesome engineers at many levels to solve problems in IoT, ML and more. Developers with experience in building products at scale can email resumes directly to me at manik.singla@loconav.com.
LocoNav, a Sequoia Capital backed fleet-tech startup, is looking for passionate developers to join our software development team. With presence in 25+ countries and market leadership in India, we recently raised a Series B for $37Mn. We are now growing exponentially and want to work with awesome engineers at many levels to solve problems in IoT, ML, AI and more. Developers with experience in building products at scale can email resumes directly to me at manik.singla@loconav.com.
LocoNav, a Sequoia Capital backed fleet-tech startup, is looking for passionate developers to join our software development team. With presence in 25+ countries and market leadership in India, we recently raised a Series B for $37Mn. We are now growing exponentially and want to work with awesome engineers at many levels to solve problems in IoT, ML, AI and more. Developers with experience in building products at scale can email resumes directly to me at manik.singla@loconav.com.
Article highlight some great points. But I think Feature flags bring value where we dont need to rollback code if its failing. Also failure so not so straight forward in most of cases where we enable a feature and it fails. Sometimes it degrades performance over time, sometime you want to enable it slow to understand its semantic under production traffic, sometimes we want to enable something around some launch date etc.
For sure, it brings extra complexity in code because of left over flags which are not cleaned up. Not only complexity which is added while writing flag but later new code also added for all these condition to unsure compatibility. Cleanup should be managed like tech debt but its not unfortunately.
My company is paying $ 200 if someone wants to buy something to help with home office setup. On top of that, we are allowed to take equipments from office in case feasible.
IMO, one of the reason that company doesn't want to spend more is saving cash in tough market.
There are companies out there(Sumologic is one) which provide free access depending on unstructured data volume. But in case, you have huge volumes of data in TBs and you want to manage it using open source, you might end up spending money in scaling and supporting system that you should instead buy paid versions.
I have around 13 years of experience out of which most of it is individual contributor building analytical engines for unstructured data and improving ingestion formats for performance. I have worked on Parquet, Lucene and Arrow. I have good experience with distributed Systems design. On the language front, I have mostly worked with JAVA and Scala.