Articles

(Dec 12) #mobile #flutter

It's always exciting when new technology is used in a large scale production setting. It means that it's matured to the point of reliable use, where you probably won't have to spend days trying to fix a bug that no one has heard about or experienced before. In this article, Larry McKenzie, Corey Sprague, Andrew Chalkley and Jake Hall introduce the behind-the-scenes structure of the new eBay Motors app. They discuss the philosophy behind why they chose to use machine learning, the Flutter framework, and the backend-for-frontend design structure, and how they choices benefited the team in this specific circumstance.

(Dec 11) #cpp

Although C++20 is soon to be released, there are still plenty of features that can be explored in C++14 and C++17. A major part of these include constexpr things. Arne Mertz has written an article where he first implements a basic version of FizzBuzz, then goes on to implement it using constexpr. In the process, he shows how to overcome the lack of run time functionality for the compile time implementation. Specifically he replaces the tostring method with a toarray method that achieves the same thing and creates an aray concatenation function.

(Dec 09) #c #compilers

Assumptions make an ass out of u and me. No where is it as true as it is in programming. Making assumptions is ok as long as you make them explicitly clear to anyone and everyone who uses or looks at your code, but more often than not, these assumptions aren't very clearly conveyed. In this lengthy article, Jason Sachs highlights how making assumptions can lead to some big problems. First he explains a problem that arose at work at a code review, then jumps to a tragic death that resulted from assumptions made by Uber about jay walking pedestrians, then returns to his example from work to demonstrate the issues that arise from incorrect inline assembly code, and ultimately ends with how to do it right.

(Dec 11) #csharp #functional programming

Handling errors efficiently is important because improper handling can lead to a lot of wasted resources in the form of energy, processing, or human work hours. This is especially true if you're working with an older code base that employs more common error handling techniques like using exceptions. In this article, Zhengbo Li describes how he implemented discriminated unions, a functional programming concept, in the C# codebase he was working on to handle errors in a more resource and understandability friendly manner.

And that''s it for today! Discuss this issue at our subreddit r/morningcupofcoding.

Did you like what you read? Let us know by clicking one of the links below.

Liked - Disliked

I hope you enjoyed reading the latest issue of Morning Cup of Coding. If you did, consider supporting us by becoming a patron (Patreon) for perks like ad-free issues, or via a one-time donation via PayPal.

Interested in sponsoring our newsletter? Click here to send us an email.

Cheers,

Pek