Software has become too complex. The art of writing simple, effective, and fun computer programs has been lost. CI/CD pipelines, microservices architecture, enterprise application frameworks, Agile ceremonies, and compulsory unit testing are just some of the few impediments between us and yet-to-be-written, useful applications.
This is a compact Go reference based on unit testing assertions as opposed to print statements—usually the norm. Comments are kept to a minimum; the reader is assumed to be familiarised with C-style languages (Java, C#, C++, etc.)
This is a rather rough outline that contains key points relevant to the Amazon Certified Solutions Architect (Associate) exam. My source material was primarily the A Cloud Guru course and the AWS documentation.
I am an Excel monkey. What do monkeys have to do with pandas? If you are like me and tend to solve all problems that involve data and numerical calculation in Excel, you must have come across a dreaded moment in your life in which you had to decide between cleaning the data from scratch every time there was a change, writing a cryptic nested set of functions, or…. (drum roll) writing a VBA script.
These are the best statements I heard (or were shown on slides but not necessary verbalised) during the Cloud Native 2018 conference held between Wednesday, 26th and Friday, 28th September at CodeNode, London.
Every application proposal trying to win the heart of a Fortune 500 company today not only needs to claim to be Agile—oh, sorry, SAFe—but also based on a microservices architecture. After high-profile microservices disasters like Dell’s, we understand that a myopic microservices approach may not end up well. What if we could have all the benefits of a microservices architecture but none of the drawbacks?