AI Briefing#kurly
The latest AI and developer news about #kurly, with the original source and a short summary.
The latest AI and developer news about #kurly, with the original source and a short summary.
An inbound team developer demonstrated Scrum's communication efficiency and schedule autonomy through running 6 sprints.
Kurly held a live meetup to share its development culture in order to drive service growth and secure talent.
Kurly data analysts ensure data quality through a 6-step process ranging from requirement refinement to production/analytics separation and consistency validation.
Kurly's DevOps team introduced Terraform to address infrastructure management complexity caused by growing services, and shared their modularization and refactoring process.
A Kurly engineer shared how they applied DDD's Loose Coupling and High Cohesion principles to design MSA, along with its benefits.
Kurly successfully launched a gift-sending service built on a new order server while maintaining compatibility with its legacy monolithic system.
Kurly has released its 2020 development roadmap for PHP developers, introducing a development culture based on Modern PHP and Laravel.
A new hire on Kurly's LDD team shared their experience adapting to the team and development culture through Mob Programming and Code Review.
Kurly leveraged Slack Block Kit and the Java SDK to automate vacation notifications and delivery tip approval workflows.
Kurly's development team transitioned their complex SQL-based legacy order monitoring system to Kafka and the ELK Stack, improving query speed to around 1 second.
The Kurly team implemented a reward points expiration date calculator feature using the BDD pattern, improving both the readability and writing experience of test code.
Kurly adopted 4-person mob programming and achieved 3 months of issue-free operation and improved development efficiency.
Kurly renewed its tech blog to introduce PR-based code reviews and tutorials, linking it to developer recruitment.
Kurly analyzed a coupon-unusable error caused by cart price fluctuations and verified that the defense logic at the payment stage worked correctly.