The Daily Build - Responsive design ground rules

Welcome to the CodeProject Daily Build Read online version Tuesday, July 09, 2019 Image Classification Challenge: Winners Announced! Congratulations to the winners and a huge thank you to all those who participated in the challenge. First Prize: Daniele Fontani Keras UI: A GUI to Manage Image Classification Second Prize: Allister Beharry Using Image Classification and Azure Cognitive Services to Build a Digital Forensics Tool Third Prize: Thomas Daniels A Tic Tac Toe AI with Neural Networks and Machine Learning Integrate and Automate Security in the DevOps Lifecycle GitLab Kubernetes Architecture and Cloud Native Development. A Single Application with Everything You Need for End-to-End Development and Operations. Learn More Headline article Responsive design ground rules   (0 votes) by Kent Sharkey (updated 2 hours ago) Creating a responsive design can be intimidating. There are many moving parts, things might lay out in ways you didn't expect and keeping all various viewports in mind when laying out a design can be daunting. With these ground rules, your responsive designs will be more robust and predictable. New Articles, Tech Blogs and Tips Code Generation Advent Of Code – Probably a Fire Hazard – Puzzle 6   (3 votes) by Member 14516258 (updated 20 hours ago) Hello ! I’m Xavier Jouvenot and here is the sixth part of a long series on Advent Of Code. You can find the previous part here. For this new post, we are going to solve the problem from the 6th December 2015, named "Probably a Fire Hazard". Libraries Intel Performance Primitives in 2019   (1 votes) by Jeffrey T. Fritz (updated 17 hours ago) In this video, Jeff shows you two samples that demonstrate how you can work with images using these libraries. © 2019 The Code Project.  All rights reserved. This email was sent to vutunglampro@gmail.com. To stop receiving The Daily Build click Unsubscribe. CodeProject 503-250 Ferrand Drive, Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100 Please do not reply directly to this email. It was sent from an unattended mailbox. For correspondence please use webmaster@codeproject.com