# Coronavirus Published articles for Coronavirus. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## REPL Driven Design DevFeed: [REPL Driven Design]() Original publisher: [Read original article]() Published: 2020-05-27T00:00:00Z Content type: opinion Language: en Sources: [Robert C. Martin](), [The Clean Code Blog]() Topics: [Clojure](), [Test-driven development](), [Code](), [GitHub]() Tags: [bug](), [clojure](), [code](), [coronavirus](), [data](), [github](), [mocking](), [tdd](), [tests]() ### AI overview The article reflects on using REPL Driven Design while developing a Clojure program that processes daily Coronavirus statistics from the Johns Hopkins GitHub repository. The author found REPL experiments and tests fast and confidence-building, and real production data reduced the need for mocks and fake data. However, a later design change exposed weak verification, delayed the change, and ultimately allowed a bug into production that was discovered four days later. ### Source excerpt If you follow me on facebook you know that I've been publishing daily CoronaVirus statistics. I generate these statistics using the daily updates in the Johns Hopkins github repository. At first I just hand copied the data into a spreadsheet. But that became tedious quite rapidly. Then, in late March, I wrote a little Clojure program to extract and process the data. Every morning I pull the repo, and then run my little program. It reads the files, does the math, and prints the results. Of course I used TDD to write this little program. But over the last several weeks I've made quite a few small modifications to the program; and it has grown substantially. In making these adaptations I chose to use a different discipline: REPL Driven Design. REPL Driven Design is quite popular in Clojure circles. It's also quite seductive. The idea is that you try some experiments in the REPL to make sure you've got the right ideas. Then you write a function in your code using those idea. Finally, you test that function by invoking it at the REPL. It turns out that this is a very satisfying way to work. The cycle time - the time between a code experiment and the test at the REPL - is nearly as small as TDD. This breeds lots of confidence in the solution. It also seems to save the time needed to mock, and create fake data because, at least in my case, I could use real production data in my REPL tests. So, overall, it felt like I was moving faster than I would have with TDD. But then, in late April, I wanted to do something a little more complicated than usual. It required a design change to my basic structure. And suddenly I found myself full of fear. I had no way to ensure that those design changes wouldn't leave the system broken in some way. If I made those changes, I'd have to examine every output to make sure that none of them had broken. So I postponed the change until I could muster the courage, and set aside the dedicated time it would require. The change was not too painful. ## Kotlin Mumbai: Dagger and Jetpack Navigation DevFeed: [Kotlin Mumbai: Dagger and Jetpack Navigation]() Original publisher: [Read original article]() Author: Siddhesh Patil Published: 2020-04-05T10:03:09Z Content type: article Language: en Sources: [Sid Patil - Android Engineer and Kotlin Advocate]() Topics: [Kotlin](), [Dagger](), [navigation](), [Android]() Tags: [akshay-sawant](), [android-development](), [best-android-developer-groups-in-india](), [coronavirus](), [dagger](), [dagger-2-for-android](), [developer-communities-in-mumbai](), [jetpack-navigation](), [jetpack-navigation-components](), [kedarnath-naik](), [kotlin](), [kotlin-user-group-mumbai](), [kug](), [meetup]() ### AI overview A report on moving the March 2020 Kotlin Mumbai meetup online during coronavirus lockdowns. The event covered Dagger 2 dependency injection and the Jetpack Navigation component, using tools including OBS, YouTube livestreaming, Google Meet, and Telegram. ### Source excerpt With the current situation and lockdowns due to coronavirus, we had to roll up our sleeves and prepare for a fully online meetup. ## Espressif February 2020 Newsletter Covers Remote Work, ESP32-S2, and IoT Partnerships DevFeed: [Espressif February 2020 Newsletter Covers Remote Work, ESP32-S2, and IoT Partnerships]() Original publisher: [Read original article]() Author: John Lee Published: 2020-02-27T00:00:00Z Content type: news Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [ESP32](), [Esp32 S2](), [Internet of things]() Tags: [blog](), [china](), [coronavirus](), [esp32](), [esp32-s2](), [espressif](), [instagram](), [iot](), [newsletter](), [work]() ### AI overview Espressif's February 2020 newsletter discusses how its IT systems supported remote work during the coronavirus outbreak, upcoming chips and product features, ESP32-S2 production, and IoT partnerships. ### Source excerpt Hi everyone, We expect that all of you will have heard by now the news about the novel coronavirus epidemic in China and beyond. These are tough times indeed, but luckily, at the time of the outbreak, Espressif had already structured its IT system in such a way that has enabled the vast majority of staff members to work from home. As Espressif's Founder and CEO, Teo Swee Ann, mentioned in a recent message he posted on our website: "the disruption to our operations will be minimal. ## A CEO's Experience During the nCoV Crisis -- Part II : On the Ground DevFeed: [A CEO's Experience During the nCoV Crisis -- Part II : On the Ground]() Original publisher: [Read original article]() Author: John Lee Published: 2020-02-12T00:00:00Z Content type: opinion Language: en Sources: [Blog on Developer Portal]() Topics: [FIRST](), [Espressif]() Tags: [blog](), [ceo](), [ceo-blog](), [china](), [coronavirus](), [covid](), [espressif]() ### AI overview Espressif CEO Teo Swee Ann describes conditions in Shanghai during the coronavirus crisis, including reduced traffic, staff returning to work, business operations, and quarantine-related restrictions. ### Source excerpt As Espressif is a company with their main offices in China, the recent coronavirus outbreak has affected us as well. CEO Teo Swee Ann gives an update of the situation in Shanghai. After I landed in Shanghai from Singapore on 10 Feb, the first thing I did was to get to the company. Thirty of our staff are reporting for work today. Along the way, I noticed that the traffic has been greatly reduced. ## A CEO's Experience During the nCoV Crisis -- Part I: Safety First DevFeed: [A CEO's Experience During the nCoV Crisis -- Part I: Safety First]() Original publisher: [Read original article]() Author: John Lee Published: 2020-02-09T00:00:00Z Content type: opinion Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [Processes]() Tags: [blog](), [ceo](), [ceo-blog](), [china](), [company](), [coronavirus](), [coronaviruses](), [esp-rainmaker](), [esp32](), [espressif](), [outbreak](), [safety](), [work]() ### AI overview Espressif CEO Teo Swee Ann describes how the coronavirus outbreak affected the company and explains the initial safety considerations and decision to delay the company's start date. ### Source excerpt As Espressif is a company with their main offices in China, the recent coronavirus outbreak has affected us as well. Even though there is an obvious impact on the way we work, the blow is cushioned because we have offices outside of China. Additionally, the way our IT is structured allows most of our staff to work from home, and even for the jobs that do need people to be at the office, there are ways to work around the current issues. ## CEO Letter: Feb 2020 DevFeed: [CEO Letter: Feb 2020]() Original publisher: [Read original article]() Author: John Lee Published: 2020-02-08T00:00:00Z Content type: opinion Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [ESP32](), [Vulnerabilities](), [Security](), [Hardware](), [Internet of things](), [SDK]() Tags: [blog](), [ceo](), [ceo-blog](), [coronavirus](), [esp32](), [espressif](), [hardware](), [iot](), [sdk](), [security](), [vulnerabilities]() ### AI overview Espressif's February 2020 CEO letter reviews the company's 2019 IPO, ESP32-S chip launches, security work including hardware vulnerability fixes in ESP32v3, its IoT developer ecosystem, planned 2020 chips, and operational measures related to the coronavirus epidemic in China. ### Source excerpt Dear all, 2019 has been an eventful year for Espressif; we went IPO and we launched the new ESP32-S series of chips that enable making secure, connected devices with high performance at affordable cost. We also worked on improving the security of our existing systems. ESP32v3 (aka ESP32 ECO3, the updated version of ESP32) patched the hardware vulnerabilities that were uncovered by the works of our security consultants and later independently by "LimitedResults" (aka "LR").