Introduction In this post, I will share my experience regarding the greenfield vs brownfield projects. I asked on LinkedIn if greenfield deployment is easier than brownfield and received the following votes: Below I share my subjective opinion, feel free to reach out if you do not agree with me (I’m always eager to learn). Definitions Let’s start with brief definitions of the green- and brownfield deployments. Greenfield project According to Wikipedia, the greenfield project develops “a system for a totally new environment, without concern for integrating with other systems, especially not legacy systems.

Overview What is the difference between the PoC (Proof of Concept), PoV (Proof of Value), and MVP (Minimum Viable Product)? I will explain those terms using real-file examples and events from my personal life. I will use non-IT examples - hopefully, they are easier to understand for everyone. Once you understand the purpose of those concepts, you will know when to use the proper approach. PoC (Proof of Concept) The PoC (Proof of Concept) is exactly what it is called - you want to verify the feasibility of some concept.

The question What is the best answer to the following question: How to connect a fridge to the internet? The (short) answer Why would you like to do that? What do you want to achieve? The (long) answer There are multiple ways to connect a device (i.e. a fridge) to the internet (or, to be more precise, to some backed system). Let’s not start by listing all the ways to achieve that specific task.

I often speak about providing business value using IoT solutions. My code is running on the factory floor equipment, medical devices, and in other environments. But do I really understand the end users? When medical devices were saving the lives of my kids, I realized that a single firmware/software bug might impact that process. Not every connected device is life/mission-critical, but someone or something depends on it. How should your system behave when it can not gather the required data?

Overview AWS IoT Greengrass is an open source Internet of Things edge runtime and cloud service. It enables efficient management of a huge fleet of IoT devices (called Greengrass Core Devices) and remote deployment + execution of applications at the edge. To provide those capabilities, Greengrass needs to be authorized to access other AWS Services. In this post, I will present the minimal set of privileges required for the Greengrass Core Device to operate.

I know many people that promote the following approach: “Fake it until you make it!” I strongly disagree with that statement as it puts the customer and/or end consumer at a huge risk. When someone “fakes it” (pretends to have required skills, knowledge, experience, etc.) and hopes to learn everything during the development, the final product will “break” sooner or later. That is why I think it should be called: