<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Moses Mpho Matsepane on Medium]]></title>
        <description><![CDATA[Stories by Moses Mpho Matsepane on Medium]]></description>
        <link>https://medium.com/@mphocastry?source=rss-ef76b567a0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xEg6aTfiEsHzre_2aKfUGA.jpeg</url>
            <title>Stories by Moses Mpho Matsepane on Medium</title>
            <link>https://medium.com/@mphocastry?source=rss-ef76b567a0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:05:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mphocastry/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Microservices Architecture: A Double-edged Sword. -written by ChatGPT-3]]></title>
            <link>https://medium.com/@mphocastry/microservices-architecture-pitfalls-for-low-to-medium-complexity-solutions-written-by-chatgpt-2de7e2ee1115?source=rss-ef76b567a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2de7e2ee1115</guid>
            <category><![CDATA[monolithic-architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[microservice-architecture]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <dc:creator><![CDATA[Moses Mpho Matsepane]]></dc:creator>
            <pubDate>Wed, 18 Jan 2023 11:40:03 GMT</pubDate>
            <atom:updated>2023-01-21T18:44:40.778Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*X9QtuasQK_MW_FZ_g2LXpQ.png" /></figure><p>Microservices architecture is a popular design pattern for building cloud-based solutions, but it may not be the best fit for low to medium complexity systems. This architecture is based on the idea of breaking down monolithic applications into smaller, independent services that can be developed, deployed, and scaled independently. While this approach has many benefits, such as increased scalability and flexibility, it also introduces new challenges and potential issues that should be considered before adopting it for low to medium complexity systems.</p><p>One of the main pitfalls of microservices architecture is the complexity it introduces. With a monolithic application, all the code and dependencies are contained in a single codebase, making it easier to understand and manage. With microservices, the codebase is split into multiple services, each with their own dependencies, which can make it difficult to understand how everything fits together and how to troubleshoot issues. Additionally, microservices require a lot of coordination between different teams, which can lead to delays and communication issues. This added complexity can be overwhelming for systems that do not require the added scalability or flexibility that microservices provide, and can lead to increased development and maintenance costs.</p><p>Another pitfall of microservices architecture is the increased risk of service failures. With a monolithic application, if one component fails, the entire application may fail. With microservices, individual services can fail without affecting the entire system, but this also means that there are more points of failure, which increases the risk of service outages. Additionally, microservices require more monitoring and management to ensure that each service is running correctly and to troubleshoot issues when they occur. This added complexity and risk can be unnecessary for systems with low to medium complexity.</p><p>Another issue with microservices architecture is the increased complexity of testing and deployment. With a monolithic application, testing and deployment can be done as a single unit, but with microservices, each service must be tested and deployed separately, which can be time-consuming and error-prone. This added complexity can be a significant burden for systems with low to medium complexity, and can lead to increased development and maintenance costs.</p><p>Another concern with microservices architecture is the increased latency caused by service-to-service communication. With a monolithic application, all the components are in the same process, so communication is fast and efficient. With microservices, communication between services requires network calls, which can add latency and slow down the system. This added latency can be a problem for systems with low to medium complexity, as it may not be necessary to incur the added latency for the benefits of microservices.</p><p>Lastly, Microservices architecture requires a lot of resources to build, operate and maintain. The increased number of services, need for service discovery and load balancing, service registry and API gateways, and service monitoring and logging can add significant cost and operational overhead. This added cost and operational overhead can be a significant burden for systems with low to medium complexity, and may not be worth the added scalability or flexibility that microservices provide.</p><p>In conclusion, while microservices architecture can offer many benefits, such as increased scalability and flexibility, it also introduces new challenges and potential issues. These include complexity, increased risk of service failures, increased complexity of testing and deployment, increased latency, and increased operational overhead. Therefore, it is important to carefully consider the trade-offs and weigh the costs and benefits before adopting microservices architecture for low to medium complexity cloud-based solutions. It may be more beneficial to stick with a monolithic architecture for these types of systems, as it can offer simpler development, testing, and deployment, lower risk of service failures, and lower operational overhead.</p><p>This article was written 100% by ChatGPT. You will notice that it becomes a bit robotic when it attempts to make multiple points, and I was tempted to edit it in order to give it a human touch, but I stopped myself. I want the reader to treat this as an authentic AI publication without human intervention. Let me know what you think.</p><p><a href="https://chat.openai.com/chat">https://chat.openai.com/chat</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2de7e2ee1115" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[System and Software Architecture Overview (Written by Chat-GPT3)]]></title>
            <link>https://medium.com/@mphocastry/system-and-software-architecture-overview-written-by-chat-gpt3-b4041be13e58?source=rss-ef76b567a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4041be13e58</guid>
            <category><![CDATA[system-architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-design]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Moses Mpho Matsepane]]></dc:creator>
            <pubDate>Sat, 17 Dec 2022 07:54:59 GMT</pubDate>
            <atom:updated>2022-12-17T07:56:43.333Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*LuPsUXgqD688GsQvO1CVFw.png" /></figure><p>Software architecture refers to the high-level structure of a software system and the way it is designed to meet the specific goals and requirements of an organization. It involves the selection of specific components, the relationships between them, and the design patterns that will be used to connect them.</p><p>System architecture, on the other hand, refers to the overall design of a system, including both hardware and software components. It defines the structure, behavior, and interactions of the system as a whole.</p><p>There are several different architectural styles that can be used in software and system design, each with its own set of benefits and trade-offs. Some common architectural styles include:</p><ul><li>Monolithic architecture, where all components are tightly coupled and built as a single unit. This can be easy to develop and maintain, but can be inflexible and difficult to scale.</li><li>Microservices architecture, where the system is broken down into small, independent services that communicate with each other through APIs. This can be highly scalable and flexible, but can be more complex to develop and maintain.</li><li>Client-server architecture, where the system is divided into client and server components, with the client making requests to the server and the server responding with the requested data or functionality. This can be a scalable and flexible approach, but can be more complex to design and maintain.</li><li>Service-oriented architecture (SOA), where the system is made up of independent services that communicate with each other through a common interface. This can be highly scalable and flexible, but can be more complex to develop and maintain.</li><li>Event-driven architecture, where the system is built around the concept of events and event-driven processing. This can be highly scalable and flexible, but can be more complex to design and implement.</li></ul><p>The choice of software and system architecture will depend on the specific goals and requirements of an organization, as well as factors such as scalability, maintainability, reliability, and cost.</p><p>In terms of compatibility with programming languages, most architectural styles can be implemented using a variety of programming languages. For example, a monolithic architecture can be implemented using languages such as Java, C#, or Python, while a microservices architecture could be implemented using languages such as Java, Go, or Python.</p><p>However, certain programming languages may be better suited to certain architectural styles due to their inherent characteristics. For example, languages like Java and C# are often used in enterprise applications due to their strong support for concurrency and scalability, while languages like Python and Ruby are often used in web development due to their simplicity and ease of use.</p><p>Ultimately, the choice of programming language will depend on the specific goals and requirements of the project, as well as the skills and expertise of the development team. It is important to carefully consider all factors when choosing an architecture and programming language to ensure that the resulting system is effective, efficient, and maintainable.</p><p>This article was written 100% by Chat-GPT-3, my only contribution was the heading nothing else. Let me know what you think.</p><p><a href="https://chat.openai.com/chat">https://chat.openai.com/chat</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4041be13e58" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Programming Language Generations (Written by Chat-GPT3)]]></title>
            <link>https://medium.com/@mphocastry/programming-language-generations-written-by-chat-gpt3-6e3723523ba?source=rss-ef76b567a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e3723523ba</guid>
            <category><![CDATA[code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[programming-languages]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Moses Mpho Matsepane]]></dc:creator>
            <pubDate>Fri, 16 Dec 2022 19:05:24 GMT</pubDate>
            <atom:updated>2023-01-21T18:39:52.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>An Overview of Programming Language Generations: From First to Fifth (Written by Chat-GPT3)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Il8RipqRNoU5MkFDBP4nw.jpeg" /></figure><p>Programming languages have come a long way since their inception in the 1950s. These languages are used to write software, build websites, create mobile apps, and more. They allow humans to communicate with computers in a way that they can understand, using a specific set of rules and syntax.</p><p>There have been several generations of programming languages, each with its own unique features and capabilities. Here is a brief overview of the different generations of programming languages:</p><p>First-generation programming languages (1GL)</p><p>First-generation programming languages, also known as machine languages or assembly languages, are the lowest-level languages that are used to write programs for computers. They consist of a series of binary digits (ones and zeros) that the computer can understand and execute. While these languages are fast and efficient, they are also difficult for humans to read and write, as they do not use natural language.</p><p>Second-generation programming languages (2GL)</p><p>Second-generation programming languages, also known as low-level languages, are a step up from machine languages. They are still close to the hardware and use a symbolic representation of machine language instructions. These languages are easier for humans to read and write than machine languages, but they are still not as user-friendly as higher-level languages. Examples of 2GL languages include COBOL and FORTRAN.</p><p>Third-generation programming languages (3GL)</p><p>Third-generation programming languages, also known as high-level languages, are more abstract and use English-like syntax. They are easier for humans to read and write than low-level languages, and they are also more portable. This means that programs written in 3GL languages can be run on different types of computers without requiring significant modifications. Examples of 3GL languages include C, C++, and Java.</p><p>Fourth-generation programming languages (4GL)</p><p>Fourth-generation programming languages are even higher-level than 3GL languages and are designed to be used for specific tasks. They are often used to build database systems, create user interfaces, and generate reports. These languages are easy for humans to read and write and are often used by non-programmers. Examples of 4GL languages include SQL and Visual Basic.</p><p>Fifth-generation programming languages (5GL)</p><p>Fifth-generation programming languages are a type of artificial intelligence language that is used to create expert systems. These systems are designed to solve complex problems in specific domains, such as medical diagnosis or financial forecasting. 5GL languages are designed to be used by non-programmers and do not require detailed knowledge of programming. Examples of 5GL languages include Prolog and LISP.</p><p>As you can see, there have been several generations of programming languages, each with its own unique features and capabilities. While first-generation languages are fast and efficient, they are also difficult for humans to read and write. On the other hand, fifth-generation languages are easy for humans to use, but they are specialized for specific tasks. The choice of programming language depends on the specific needs and requirements of the task at hand.</p><p>This article was written 100% by Chat-GPT-3, including the title. Let me know what you think.</p><p><a href="https://chat.openai.com/chat">https://chat.openai.com/chat</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e3723523ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Investigating the Reality of Photos of Distant Planets: The Science Behind the Images.]]></title>
            <link>https://medium.com/@mphocastry/fake-images-of-distant-planets-d6945b22d731?source=rss-ef76b567a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6945b22d731</guid>
            <category><![CDATA[planets]]></category>
            <category><![CDATA[solar-system]]></category>
            <category><![CDATA[astrophysics]]></category>
            <category><![CDATA[astronomy]]></category>
            <category><![CDATA[exoplanets]]></category>
            <dc:creator><![CDATA[Moses Mpho Matsepane]]></dc:creator>
            <pubDate>Thu, 14 Oct 2021 11:10:24 GMT</pubDate>
            <atom:updated>2025-01-28T11:25:37.167Z</atom:updated>
            <content:encoded><![CDATA[<p>If a survey targeted at the general public was to be conducted asking everyone about the number of exoplanets(planets outside our solar system) discovered to date. It is safe to say that without ‘Googling’, there is a high likelihood that most people will not know the approximate number. However, if the survey was to be reframed by asking whether we have photographs or detailed images of exoplanets. Most people would say we do without “Googling” anything.</p><p>This article will delve into the reasons why so many members of the general public believe that we have detailed images of the exoplanets that have been discovered thus far. The image below is what a typical exoplanet would look like if we imaged it directly and took a photograph. This is the level of detail that is common when we image exoplanets. The small bright dot is the image of a planet, and this is also only possible if the conditions are right such as if the exoplanet is large and very hot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/0*MzNMbrxxUuHZdN_-.jpg" /><figcaption>Directly Imaged Exoplanet</figcaption></figure><h3>Nasa</h3><p>Is there at least one detailed photograph of an exoplanet that we are in possession of? The short and simple answer is no. There are no detailed exoplanet images. To clarify this point further, here is what Nasa has to say regarding the imaging of <a href="https://www.nasa.gov/feature/goddard/2021/hubble-watches-how-a-giant-planet-grows">Exoplanets</a>:</p><blockquote>Though over 4,000 <a href="https://exoplanets.nasa.gov/">exoplanets</a> have been cataloged so far, only about 15 have been directly imaged to date by telescopes. And the planets are so far away and small, they are simply dots in the best photos. The team’s fresh technique for using Hubble to directly image this planet paves a new route for further exoplanet research, especially during a planet’s formative years.</blockquote><p>If there are no detailed images of exoplanets, why does the general public believe otherwise? Perhaps it’s the methods used to report interesting planet discoveries. But before exploring the reasons, it is only appropriate to briefly explain how exoplanets are detected.</p><h3>Exoplanet Detection Methods</h3><p>There are about 8 methods that may be used to detect exoplanets namely; Radial Velocity, Transits, Microlensing, Imaging, Timing Variations, Orbital Brightness, Modulation and Astrometry, there could be more in future but these are the most established and well-documented methods currently.</p><p>Out of the over 4000 exoplanets discovered thus far, there are two methods responsible for the majority of these discoveries. These methods are the Transit method and the Radial Velocity method as seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/0*P7h9jv_QF9VpavpU.png" /></figure><p>Once an interesting exoplanet is discovered, the data captured regarding the planet would be extremely boring for the general public. Therefore, organisations such as Nasa, ESA, etc will use an artist’s impression to make the discovery relatable to the general public.</p><p>The diagram below illustrates a typical transit graph for a planet detected passing in front of its host star. This transit graph is usually compiled using data from telescopes such as Spitzer, Kepler, and many other telescopes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/0*rqXSPOVeLnMEX2o1.png" /><figcaption>Transit Graph</figcaption></figure><p>Once a transit has been confirmed, there are usually multiple other validations to ensure that it is indeed a planet and not just noise. Sometimes a couple of research papers are published if the discovery is significant enough. Then media-friendly data is generated to enable the journalists to communicate the findings with the general public. At this point is where everything becomes the Wild Wild West.</p><p>The narrative and the entire reporting process can sometimes give the public an overly optimistic spin on the data. Headlines such as this one from ‘the guardian’; “<a href="https://www.theguardian.com/science/2015/jul/23/nasa-closest-twin-to-earth-kepler-452b">Earth 2.0: Nasa says scientists have found ‘closest twin’ outside solar system</a>” give the public the impression that a new “Earth-like” planet has been discovered.</p><h3>Artist’s Impression</h3><p>A newly discovered ‘Earth-like’ planet would not be interesting if the public was shown an image of a transit graph. The common tools used to communicate these new discoveries with the public are beautiful 3D renders and animations illustrating an exotic-looking planet. The image below illustrates on the left a 3D model of Earth and on the right, Kepler-452b commonly referred to as Earth 2.0 upon its discovery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-4uds9pLDDewUEP4.jpg" /><figcaption>This artist’s concept compares Earth (left) to the new planet, called Kepler-452b, which is about 60 percent larger in diameter.</figcaption></figure><p>When images such as the one above are shown, there is usually a disclaimer or a brief mention that it is an artist’s impression of the planet. One could argue that there is nothing wrong with artistic impressions for scientific discoveries since this practice is ubiquitous in other fields as well.</p><p>In our solar system, the public including children can readily identify images of our 8 planets, the confusion begins with exoplanets. Ask anyone to describe what Proxima Centauri b(the nearest exoplanet to us)looks like, most certainly no one will know the answer. However, if you show them a 3D render or animation of Proxima Centauri b, most members of the public will accept the illustration below as real or derived from a real image of the planet without any reservations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9EXVjbIXbLd66FN_.jpg" /><figcaption>Proxima Centauri b</figcaption></figure><h3>Distances and Scales</h3><p>As humans, we struggle to wrap our heads around the scales of objects that are being captured by our fantastic telescopes such as Hubble, Keppler, Spitzer, and others. The distances and scales are vast and incomprehensible.</p><p>The most common question that comes up regarding the question of distant planets is; “How is it possible to see images of galaxies billions of light-years away, and yet we cannot even capture an image of an exoplanet only 4 light-years away”. That is actually a very good question when coming from those without any background in this field.</p><p>In my youth, I thought we had telescopes powerful enough to directly image distant exoplanets. It never crossed my mind that we do not have the capability to capture detailed images of such planets. I always just assumed like most people that we have lots of images. This assumption stopped when I started to gain some understanding of optics and astrophotography. It took some time until I realised that capturing high-resolution images of exoplanets was an insurmountable scientific and engineering feat, even for the nearest exoplanets. The best images we can get with the technology that we possess at present are illustrated below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*HkwnTmk17symgycd.jpg" /></figure><blockquote><a href="https://www.eso.org/public/news/eso2011/"><strong>The European Southern Observatory’s Very Large Telescope (ESO’s VLT) has taken the first ever image of a young, Sun-like star accompanied by two giant exoplanets. Images of systems with multiple exoplanets are extremely rare, and — until now — astronomers had never directly observed more than one planet orbiting a star similar to the Sun. The observations can help astronomers understand how planets formed and evolved around our own Sun.</strong></a></blockquote><h3>Conclusion</h3><p>The technique that was used to capture the solar system above will not work on capturing planets similar to the ones on our solar system. The planets on our solar system are relatively cool when compared to these young, hot, and large planets.</p><p>Therefore, in conclusion, it is not possible to capture detailed images of exoplanets with the current generation of telescopes. So next time when you see a newly discovered “home away from home” “Earth-like” planet, keep in mind that the image is not real. We do not possess the technological capability to capture detailed images of exoplanets.</p><p>References:</p><ul><li><a href="https://www.nasa.gov/press-release/nasa-kepler-mission-discovers-bigger-older-cousin-to-earth">NASA&#39;s Kepler Mission Discovers Bigger, Older Cousin to Earth</a></li><li><a href="https://www.eso.org/public/news/eso2011/">First Ever Image of a Multi-Planet System around a Sun-like Star Captured by ESO Telescope</a></li><li><a href="https://en.wikipedia.org/wiki/Kepler-22b">Kepler-22b - Wikipedia</a></li><li><a href="https://www.universetoday.com/107854/super-sensitive-camera-captures-a-direct-image-of-an-exoplanet/">Super-sensitive Camera Captures a Direct Image of an Exoplanet - Universe Today</a></li><li><a href="https://britastro.org/node/16553">Exoplanet Transit Imaging and analysis Process | British Astronomical Association</a></li><li><a href="https://en.wikipedia.org/wiki/Astrophotography">Astrophotography - Wikipedia</a></li><li><a href="https://en.wikipedia.org/wiki/Proxima_Centauri_b">Proxima Centauri b - Wikipedia</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6945b22d731" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Intersection of Form and Function: A Look at Design and Aesthetics in Heavy Industry.]]></title>
            <link>https://medium.com/@mphocastry/design-and-aesthetics-in-heavy-industries-d3bd8ddee96d?source=rss-ef76b567a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3bd8ddee96d</guid>
            <category><![CDATA[industrial-design]]></category>
            <category><![CDATA[aesthetics]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Moses Mpho Matsepane]]></dc:creator>
            <pubDate>Tue, 15 May 2018 10:17:01 GMT</pubDate>
            <atom:updated>2023-01-21T18:36:37.444Z</atom:updated>
            <content:encoded><![CDATA[<p>Why is there an aesthetic disparity between industrial and consumer products?</p><p><strong>Introduction</strong></p><p>Human emotions are evoked by a multitude of external factors, one of those being aesthetics — the beauty in things. The appreciation of elegance in products is so subjective that fields of art, philosophy, engineering, architecture etc. and sometimes psychology hold very different views on this subject. This leads to the question: how can something so plain and intuitive create so much confusion? In fact the prevalence of aesthetics in the minds of consumers has let to its expectation not only in products, but in retail outlets, graphics design, billboards, thus suggesting that we are in an era of beautification. Hence the word Design is usually synonymous with aesthetics, whereas aesthetics result from a good design, but design is not aesthetics.</p><p>Thus far no school of thought has come up with an all encompassing definition the true value of aesthetics in products, more especially in heavy industry such as logistics, aviation, mining and manufacturing. All these industries always favoured design choices such as functionality, safety, durability and other attributes over aesthetics for many years. This brings up the question; Is there a significant role that aesthetics play in the overall design of a product for the general user? The answer to this question is obvious in the consumer products space, but very murky on the heavy industry side. Why?</p><p><strong>History</strong></p><p>If we to go back in history to the time just before the industrial revolution. It quickly becomes very clear that the function of design and manufacturing was exactly the same. In fact the product was often designed and made by the same person(or family), using skills and trades that have been passed on from generation to generation. This resulted in designs and product expressions that are very localised and locked to the specific maker. After the industrial revolution, it became possible to separate designs from the manufacturing process. This resulted in the capability to produce items that are generic in form while still able to meet the needs of many consumers.</p><p>This is the same era where a lot of great Industrial designers came into the scene. Designers such as Raymond Loewy who is said to have designed for business, Henry Dreyfuss for people and Dieter rams for behaviour. All these men have made significant contributions to the field of industrial design and their philosophies influenced many of the designs that we see in modern products.</p><p><strong>Raymond Loewy</strong></p><p>Raymond Loewy kicked off his industrial design career in 1929. He is one of the few mavericks that can be called the ‘father of modern industrial design’. He lived by a principle famously known as MAYA(Most Advanced Yet Acceptable). His portfolio was the most diverse in design history, having worked on heavy industries and consumer products. This makes him and ideal person to understand the role aesthetics play across industries. In 1975 the Smithsonian institute showcased his designs on a four month exhibit that was coined, “the man who changed the face of industrial design.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mfVjz-3bKZZVIJH_." /><figcaption>Source: fastcodesign</figcaption></figure><p>His most notable work include the following:</p><p><em>GG1 and S1 locomotives</em></p><p><em>Interior design of Saturn I, Saturn V, and Skylab</em></p><p><em>Studebaker Avanti, Starliner Coupé,</em></p><p><em>Logos for Greyhounds bus company, Shell, Exxon</em></p><p><em>Lucky Strike cigarette packaging</em></p><p>What stands out the most from him is the following statement; “The adult public’s taste is not necessarily ready to accept the logical solutions to their requirements if the solution implies too vast a departure from what they have been conditioned into accepting as the norm.” That is how a combination of the above statement and the MAYA principle, gives us a clue on how he managed to conjure up such revolutionary work during his time.</p><p><strong>Henry Dreyfuss</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/0*MAn4thrD8rvpWhlC." /><figcaption><strong>Source: IDSA</strong></figcaption></figure><p>Henry Dreyfuss was the man behind the form factor of the table top telephone as we know it today, he started developing it in the 1930’s. His design was so successful, that it ended up being the most commonly used phone design between 1955 and 1995. The early versions of that design were from a competition he won at Bell labs called “phone of the future”. In 1941 he collaborated with Raymond Loewy to design strategy rooms for joint chief of staff. Dreyfuss had different philosophies to his predecessor Raymond, but both men always had the needs of the users as a centerpiece in their thinking and philosophies. Dreyfuss stressed that good design was for everyone. He felt that “products of the applied arts are part of everyday living and working”.</p><p><strong>Dieter Rams</strong></p><p>When we speak of design and refer specifically to artifacts such as buildings, furniture or just general non-electronic tools that we use on a daily basis. One major characteristic of these items is that their purpose lies in their function and less in their design. The general public will always perceive a chair as a sitting instrument, it is less likely to be mistaken for anything else, same applies to buildings and other general furniture and tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*0SzjTxSKc0KefixC." /><figcaption><strong>RT 20 tischsuper radio, 1961, by Dieter Rams for Braun- Source:vitsoe</strong></figcaption></figure><p>Dieter Rams arrived in the scene when electronics were becoming ubiquitous in the consumer space. And one thing about electronic products such as a radio or television sets is that, functionality is more abstract than in other design artifacts. A button on a radio can be used for multiple functions such as on/off, volume, tuning, etc. Dieter Rams was the evangelist of simplicity, he spent 40 years at Braun designing some of the most legendary products there. In that time he extrapolated the design philosophy of “less is more” into ten Design principles that are still used religiously by some of the largest consumer electronics companies in the world. One of the most apparent ones being Apple, as their Chief Design Officer Jonathan Ive mentioned several times that he draws most of his design inspiration from Dieter Rams.</p><p><strong>The Contemporary Era</strong></p><p>The late 70’s well into the early 80’s was the beginning of an era of Personal computing, and because of software housed in them, the gap between functionality and form increased by orders of magnitude. This also increased complexity of the design process for modern electronic systems. The amount of information that needs to be taken into consideration during the design process is now astronomical. However, one thing very clear in the current era of design, especially for consumer electronics is that aesthetics and simplicity are more favourable over other characteristics such as configurability.</p><p>As much as Raymond Loewy demonstrated in the past that artistic expression and design in heavy industries was taken seriously in the early 20th century. That was an era when most organisations realised that design was not exclusive to engineering. Other areas of design had to be incorporated to enhance the user experience. If one was to look at Raymond Loewy’s locomotive designs vs modern locomotives with the exception of passenger trains. It becomes very clear that if aesthetics are not intertwined to a function(i.e aerodynamics), they usually get dismissed.</p><p>What lead to the elimination of aesthetics in heavy industry whilst the rest of the consumer industry expects aesthetics as standard? Why do we appreciate the so-called “futuristic” designs in film, whereas in reality we are happy with objects and machines that look like relics? This same problem has trickled down to design philosophies of industrial software products. The software for heavy industry looks like it was made for machines and not for man, it is boring, it looks dull and is not fun to use especially without rigorous training.</p><p><strong>Design Decision Making Process</strong></p><p>Now one thing that most people in the product design space agree on is just how intricate it is to take a product from inception to the hands of users. The source of complexity in product development/design is the shear amount of metrics monitored throughout the life-time of the product in order to measure its viability. One metric that carries more weight than any other is commercial viability obviously. The product needs to demonstrate that, it will at some point return the capital that was invested by the organisation to bring it to market. That is the crux of what drives the decision making process for products that you see in the market today.</p><p>This makes one wonder whether aesthetics add any significant value to the end product in heavy industries. Were the fathers of industrial design wishful thinkers by adding aesthetics to huge machines such as the Saturn rockets? Usually during the design process, the easy decision is to eliminate aesthetics all together in order to cut costs. The fundamental flaw in that decision making process is the assumption that a product can be treated as an equation, where sum of components Xn and/or features and characteristics Yn translate to overall value Zn. Value being cost, ease of manufacturing, environmental footprint etc. Therefore the supposed equation is often used to eliminate components, features or characteristics that are deemed low priority or “nice to have”. Those who pursue this rationale often say this is the only way one can improve the commercial viability of the product without compromising the overall perceived value of the product.</p><p><strong>Linear and Non-linear Outcomes</strong></p><p>The main reason some of these decision makers think this way, is because they are not familiar with the linear and nonlinear outcomes in product design decisions. If one is operating from a purely linear perspective, product optimisation by elimination and addition of components makes perfect sense. But very often the response from customers or the market tends to be nonlinear. There are cases where customers love or hate your product because of the font that was used on the product name. It is not a straightforward exercise to predict some of these non-linear responses, because there is virtually an infinite number of ways a product can be configured.</p><p><strong>Via Negativa</strong></p><p>A deterministic approach where one needs to predict the future in order to come up with the best design, rarely works. The best position to commence from, is with the assumption that the future is unknown and uncertain. Your customers or users may love an “aesthetic feature” today, and yet totally reject it tomorrow. Those are the realities that designers are faced with.</p><p>The process that brings one closer to an exceptional design is not the process of adding, but a process of removal. This does not imply the removal of features or functionality. This means the removal of everything about the product that doesn’t qualify it as a good design. The great minds of Dieter, Raymond, Henry and many others provided us with principles instead of manuals. The most rational thing to do is to rid your design of anything that doesn’t live up to those principles, and with the aid of “via negativa” philosophy you will most certainly know what a good design is not instead of attempting to predict whether your customers will like it. This thought process will embed the customer at the heart of all designs, whilst not predicting how they would perceive the product in the future.</p><p><strong>Conclusion</strong></p><p>At Castry we obsess about user centered design. We believe that complexity needs to be abstracted away from the user. We strive to embed process onto our products thus eliminating the need for extensive training for our users. Products that are designed well will always look fantastic and at the same time provide the customer with tremendous value. All the literature that we publish is based on the risks that we have taken and the principles that we have followed. Finally and most importantly, we believe in products that are aesthetically pleasing. Not for style or for the sake of beauty, but for our designs to be unobtrusive, where a diverse number of users can appreciate aesthetics of the products without that being the centre of attention. We believe that all products should evoke the emotion of pleasure when the customer looks at them, including all products in the heavy industry.</p><p>In summary: A good design is unobtrusive, most advanced yet acceptable.</p><p><a href="https://play.google.com/store/apps/details?id=com.Muchiniwam">Muchiniwam - Apps on Google Play</a></p><p>References:</p><p><a href="https://www.oreilly.com/library/view/understanding-industrial-design/9781491920381/ch01.html">Understanding Industrial Design</a></p><p><em>Designing for People — Henry Dreyfuss, Skyhorse Publishing,1955</em></p><p><a href="https://www.raymondloewy.com/"><em>https://www.raymondloewy.com/</em></a></p><p><a href="http://www.idsa.org/content/henry-dreyfuss-fidsa"><em>http://www.idsa.org/content/henry-dreyfuss-fidsa</em></a></p><p><em>Beautiful Beings: Aesthetics in Industrial Design and Cultural Studies Prasad Boradkar, Assistant Professor Arizona State University</em></p><p><a href="https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/industrial-design"><em>https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/industrial-design</em></a></p><p><em>Design. History, Theory and Practice of Product Design Published on Aug 28, 2015 , Benhard.E Burdek</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3bd8ddee96d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>