
Pulumi is an infrastructure-as-code (IAC) platform that allows developers and operators to define, deploy, and 
manage cloud resources using familiar programming languages like Python, JavaScript, TypeScript, Go, and C#.

![pulumi example](/images/blog/pulumi-1.png)

Pulumi has gained traction in the community for several reasons:

- **Familiar programming languages**: Pulumi supports popular, general-purpose programming languages, enabling 
  developers to leverage their existing skills and knowledge. This allows for a smoother learning curve and 
  improved productivity.

- **Code reusability and modularity**: Pulumi's support for general-purpose programming languages enables better code 
reusability, modularity, and organization. Developers can create custom abstractions, share code between projects, 
and apply software engineering best practices to infrastructure management.

- **Integration with existing tools and libraries**: Pulumi's language support allows for easy integration with 
  existing tools, libraries, and frameworks. This can help streamline development workflows and improve overall 
  efficiency.

- **Strong support for cloud platforms**: Pulumi provides support for a wide range of cloud providers, including AWS, 
Azure, Google Cloud, and Kubernetes. It also offers support for additional providers and services through its 
growing ecosystem.

- **Real-time feedback and preview**: Pulumi offers real-time feedback and preview capabilities, allowing developers to 
see the impact of their infrastructure changes before applying them. This can help catch potential issues early and 
improve overall reliability.

- **State management**: Pulumi manages state using its Pulumi Service, which simplifies state handling, locking, and 
consistency for users. This can lead to a more streamlined user experience compared to some other IAC tools.

- **Policy as Code**: Pulumi includes policy-as-code capabilities, allowing organizations to enforce best practices, 
security policies, and compliance requirements across their infrastructure.

- **Growing community and ecosystem**: Pulumi has been attracting attention from developers and organizations 
  looking for a modern approach to infrastructure management. This has resulted in a growing community, ecosystem, 
  and library of pre-built components.

## Differences between Terraform and Pulumi

Both of them are infrastructure-as-code (IAC) tools that help users automate and manage their cloud infrastructure.

Although they share a common purpose, there are several differences between the two tools:

#### Language Support

**Terraform**: It uses its own domain-specific language (DSL) called HashiCorp Configuration Language (HCL) for writing 
infrastructure configurations. HCL is designed specifically for defining cloud infrastructure and resources, making 
it easy to read and understand.

![terraform example](/images/blog/terraform.png)

**Pulumi**: It supports general-purpose programming languages like Python, JavaScript, TypeScript, Go, and C#. This 
enables users to leverage existing programming skills and use familiar constructs, libraries, and tools for 
infrastructure management.

![pulumi example](/images/blog/pulumi-2.png)

#### Ecosystem and Community

**Terraform**: Developed by HashiCorp, Terraform has a larger and more mature ecosystem with a broad range of supported 
cloud providers and services. It has a vast collection of pre-built modules and a large user community.

**Pulumi**: Pulumi is a newer and smaller player in the IAC space. Although it has a growing ecosystem and support for 
various cloud providers, its community and library of pre-built modules are not as extensive as Terraform's.

#### State Management

**Terraform**: It manages the state of infrastructure using a local or remote backend, which stores the current state 
of resources. Users must configure state backends and handle state locking and consistency.

**Pulumi**: It handles state management through its own Pulumi Service, which stores and manages the state by default. 
Pulumi automatically handles state locking and consistency, simplifying the user experience.

#### Pricing and Open Source

**Terraform**: It is an open-source tool, and its core functionality is free to use. HashiCorp also offers a commercial 
product called Terraform Enterprise that adds features like collaboration, governance, and enhanced security.

**Pulumi**: It offers a free tier with basic features and limited usage, but its advanced features and commercial 
support require a paid subscription. Pulumi's core is open source, but its service for state management is not.

#### Interoperability

**Terraform**: Terraform's HCL may have a learning curve for users who are not familiar with it. While Terraform has 
excellent cloud provider support, it can be more challenging to integrate with existing application codebases.

**Pulumi**: Since it uses general-purpose programming languages, Pulumi can more easily integrate with existing 
codebases, libraries, and frameworks, enabling developers to create reusable components and apply software 
engineering best practices to infrastructure management.

## Conclusion

That said, both Terraform and Pulumi have their strengths and weaknesses. The choice between them will depend on
factors such as the user's programming background, desired language support, existing tooling, and community support.

Despite being a newer player in the IAC space, Pulumi's unique approach of using general-purpose programming 
languages and its focus on developer experience has resonated with many in the community.

HelloWorld's professionals keep an eye on innovative solutions like Pulumi and Terraform, so they can use the right 
technologies and tools for the challenging problems they have to tackle every single day. Cheers!!


Pulumi vs Terraform

Twelve-factor processes are stateless and [share-nothing](https://en.wikipedia.org/wiki/Shared-nothing_architecture).

Any data that needs to persist must be stored in a stateful [backing service](https://12factor.net/backing-services),
typically a database.

The twelve-factor app never assumes that anything cached in memory or on disk will be available on a future request 
or job – with many processes of each type running, chances are high that a future request will be served by a 
different process.

Even when running only one process, a restart (triggered by code deploy, config change, or the execution environment 
relocating the process to a different physical location) will usually wipe out all local (e.g., memory and 
filesystem) state. Cheers!!


Processes: Execute the app as one or more stateless processes


Progressive Web Apps (PWAs) are a modern approach to web development that combine the best of web and mobile app 
experiences. They are built using standard web technologies, such as HTML, CSS, and JavaScript, and can be accessed 
through a web browser or installed on a user's device. Here are several reasons why websites should consider 
becoming PWAs:

- **Improved user experience**: PWAs offer a more engaging and seamless user experience, with features like offline 
support, push notifications, and full-screen mode. These features help create a more app-like experience, 
increasing user satisfaction and retention.

- **Faster load times**: PWAs leverage modern web technologies, such as service workers and caching, to ensure fast load 
times and improved performance. This can lead to higher user engagement and conversion rates, as users are less 
likely to abandon a site that loads quickly.

- **Offline access**: PWAs can work offline or on low-quality networks, thanks to service workers and caching. This 
enables users to access content even when they have poor or no internet connection, making your website more 
accessible and useful in a wider range of situations.

- **Search engine optimization (SEO)**: PWAs are indexable by search engines, which can lead to better search rankings 
and increased visibility for your website. Improved SEO can drive more organic traffic to your site and help grow 
your user base.

- **Push notifications**: PWAs support push notifications, allowing you to engage with users even when they're not 
actively using your website. This can help drive user engagement, boost retention, and keep your audience informed 
about updates, promotions, or other relevant information.

- **Installable on the home screen**: Users can install PWAs on their devices' home screens, making them more accessible 
and convenient to use. This also increases the likelihood that users will return to your site, as it becomes more 
integrated into their daily routines.

By adopting a PWA approach, businesses can enhance their web presence and deliver an exceptional user experience, 
ultimately driving user engagement, retention, and growth. Cheers!!


Create a Modern Website: Make the website a Progressive Web App


In the context of modern software engineering, DevOps is a complementary counterpart, much like the concept of 
Yin and Yang. These two concepts, originating from Chinese philosophy, represent the interconnectedness and 
interdependence of seemingly opposite forces in the natural world.

The traditional approach tech companies followed for many years often separated development and operations teams, 
creating silos and communication gaps. This separation could lead to inefficiencies, delays, and lower-quality 
software. DevOps brings these two functions together, integrating them into a seamless whole.

Just as Yin and Yang symbolize harmony and balance in nature, DevOps aims to harmonize the software development 
life cycle by fostering collaboration, shared goals, and continuous improvement, allowing organizations to deliver 
software faster, more reliably, and with higher quality.

Here are some key aspects that highlight the importance of DevOps culture for modern software products:

- **Faster time to market**: DevOps practices, such as continuous integration and continuous deployment (CI/CD), enable 
organizations to release software updates and new features more frequently, allowing them to stay competitive and 
respond quickly to market demands.

- **Improved collaboration**: DevOps culture encourages cross-functional teams, breaking down silos between development, 
operations, and other stakeholders. This improved collaboration leads to better communication, faster 
  decision-making, and increased innovation.

- **Higher quality**: By automating testing and deployment processes, DevOps helps reduce human error and increases the 
overall quality of the software. This results in fewer bugs, improved stability, and better user experiences.

- **Increased efficiency**: Automation and streamlined processes in DevOps eliminate manual, time-consuming tasks, 
allowing team members to focus on more valuable work, such as feature development or innovation.

- **Better resource management**: DevOps practices, such as infrastructure as code (IAC), enable more effective 
management of resources, leading to cost savings and reduced waste.

- **Enhanced scalability**: DevOps enables teams to build and deploy software using cloud-native architectures and 
technologies, making it easier to scale applications up or down as needed.

- **Continuous learning and improvement**: DevOps culture emphasizes a continuous learning mindset, encouraging teams to 
regularly assess and improve their processes, tools, and skills. This constant feedback loop helps organizations 
stay agile and adapt to changes in the market.

In summary, adopting a DevOps culture is crucial for modern software products as it helps organizations stay 
competitive, deliver better quality software, and respond more effectively to market demands. It fosters 
collaboration, efficiency, and continuous improvement, making it a key aspect of successful software development 
and IT operations.

Cheers!!


Engineering without DevOps is like Yin without Yang


The twelve-factor app uses strict separation between the build, release, and run stages.

For example, it is impossible to make changes to the code at runtime, since there is no way to propagate those 
changes back to the build stage.

Every release should always have a unique release ID, such as a timestamp of the release (such as 2011-04-06-20:32:17 )
or an incrementing number (such as  v100 ).

Releases are an append-only ledger and a release cannot be mutated once it is created.

Any change must create a new release. Cheers!!


Build, release, run: Strictly separate build and run stages


Favicons and share images through meta tags are important elements to include when developing a website for the 
following reasons:

- Branding and Recognition: A favicon, also known as a site icon, is a small image that appears in the browser tab or 
bookmark bar when someone visits your website. It helps users identify and remember your brand, even when they have 
multiple tabs open. A well-designed favicon can enhance the user experience and make your website stand out.

- Credibility and Professionalism: When someone shares your website on social media platforms like Facebook, Twitter, 
or LinkedIn, a share image is displayed along with the link preview. A well-designed share image can make your 
website look more professional and trustworthy, increasing the likelihood of people clicking on the link and 
visiting your site.

- User Engagement: When someone shares your website on social media, the share image can also encourage users to 
engage with your content. For example, if the share image features an eye-catching photo or an interesting graphic, 
it may entice people to click through and read the article or explore your website.

- SEO Benefits: Including a favicon and share image with proper meta tags can also provide SEO benefits. Search 
engines like Google use this information to understand your website's content and improve its visibility in search 
results. A well-optimized share image can also improve click-through rates and drive more traffic to your website.

Overall, favicons and share images through meta tags are important design elements that can enhance the user 
experience, increase engagement, and improve the visibility of your website. Cheers!!


Create a Modern Website: Add favicons and share image


The code for a twelve-factor app makes no distinction between local and third party
services. To the app, both are attached resources, accessed via a URL or other
locator/credentials stored in the config.

A deploy of the twelve-factor app should be able to swap out a local MySQL database
with one managed by a third party (such as Amazon RDS) without any changes to the
app’s code.

Likewise, a local SMTP server could be swapped with a third-party SMTP service (such
as Postmark) without code changes.

In both cases, only the resource handle in the config needs to change.


Backing services: Treat backing services as attached resources


The routing system of a website refers to the way in which URLs are mapped to specific pages or content within a 
web application. It determines how a user's request is processed and which content should be returned to them.

In simpler terms, the routing system is the mechanism that allows a web application to interpret the URLs entered 
by users and decide what action to take in response. For example, if a user types in "www.example.com/about", the 
routing system will determine that they are requesting the "about" page of the website and return the appropriate 
content.

The routing system is important because it allows for efficient navigation and organization within a web 
application. It makes it possible to create intuitive and user-friendly URLs that are easy to remember and 
understand. It also allows for the creation of complex and dynamic web applications that can handle a wide range of 
user requests and interactions.

In addition, the routing system plays a crucial role in search engine optimization (SEO). A well-designed routing 
system can help search engines understand the structure and content of a website, making it easier for them to 
index and rank its pages. This can lead to increased visibility and traffic for the website. Cheers!!


Create a Modern Website: Create the routing of all project pages


The twelve-factor app stores config in environment variables (often shortened to env vars or env).

Env vars are easy to change between deploys without changing any code; unlike config files, there is little chance 
of them being checked into the code repo accidentally; and unlike custom config files, or other config mechanisms 
such as Java System Properties, they are a language- and OS-agnostic standard.

Env vars are granular controls, each fully orthogonal to other env vars. They are never grouped together as 
"environments", but instead are independently managed for each deploy. This is a model that scales up smoothly as 
the app naturally expands into more deploys over its lifetime.


Config: Store config in the environment


As we explained in our [previous post](Discovery-Phase-what-it-is-and-why-we-start-projects-with-it) the Discovery 
Phase of a new project is an important part of the project planning process. It involves researching 
and gathering information about the project to determine its feasibility, scope, and potential challenges.

### Typical Deliverables

The most typical deliverables of a Discovery Phase can include:

- **Project Charter**: The project charter is a high-level document that outlines the purpose, scope, and objectives of 
the project. It also includes information about the project's stakeholders, timelines, and budgets.

- **Business Case**: The business case is a document that provides a detailed analysis of the project's costs, 
  benefits, and risks. It helps to determine whether the project is worth pursuing and provides a framework for 
  decision-making.

- **Feasibility Report**: The feasibility report assesses the technical, operational, and financial feasibility of the 
project. It identifies potential risks and challenges and provides recommendations for how to mitigate them.

- **Requirements Document**: The requirements document outlines the functional and non-functional requirements of the 
project. It helps to ensure that everyone involved in the project has a clear understanding of what needs to be 
delivered.

### UX-related Deliverables

HelloWorld teams focus a lot on the usability and the usefulness of any new product having constantly the end-user in 
mind, so apart from the above they run a thorough UX analysis to help stakeholders evaluate their idea and steer the 
wheel towards the right direction before the Development Phase starts.

These are the UX-related deliverables HelloWorld experts work on during the Discovery Phase:

- **Personas analysis**: Personas analysis is a user-centered design technique used to develop a better understanding of 
  the intended users of a product or service. Personas are fictional characters that represent different user types 
  or user groups, based on data and research.

- **User-flow diagrams**: A user flow diagram is a visual representation of the steps a user takes to complete a task or
  achieve a goal within a product or service. It maps out the user's journey from start to finish, including all the
  touchpoints and interactions they have with the product or service.

- **User stories**: User stories are a tool used in Agile software development to describe a feature or functionality 
  of a product or service from the perspective of the user. User stories are short, simple, and focused on the end 
  goal of the user, and they are typically written in a specific format that follows the formula:

  "As a [user], I want [goal], so that [reason]."

  The user story format helps to ensure that the focus remains on the user and their needs, rather than on the
technical details of the feature or functionality.

- **Low fidelity clickable prototype**: A low fidelity clickable prototype is an early-stage design prototype that is 
  created using simple and rough sketches, wireframes, or other low-fidelity design tools. The prototype is designed 
  to be clickable, which means that the user can interact with it and simulate the experience of using the final 
  product.

  Despite their simplicity, low fidelity clickable prototypes can provide valuable insights into the user experience 
  of a product or service. By testing the prototype, stakeholders can identify potential issues and dead-ends early 
  enough and use this useful information to evaluate even better whether their idea worths pursuing or not and even 
  have a better picture about the end result.

### Conclusion

Overall, the deliverables of the Discovery Phase provide a solid foundation for the project. They help to ensure 
that everyone involved in the project is on the same page and that there is a clear understanding of the project's 
goals, objectives, and requirements.

Apart from that, deliverables such as the User Stories or the Clickable Prototype, prepare the ground for the next 
phases of the project, since they help professionals that will be involved down the road, grasp fast what we are 
trying to build and why.

By completing these deliverables, we can help to ensure that a new project is well-planned, feasible, and has the 
best possible chance of success while minimizing risk.

Cheers!!


Discovery Phase: deliverables


In our [previous post](discovery-phase-what-it-is-and-why-we-start-projects-with-it) we explained why the 
Discovery Phase is important and how much it affects projects' success. One thing we didn't mention though is that 
the Discovery Phase helps the team to evaluate the feasibility of a project in order to determine if it's worth 
pursuing in the first place.

Here are some crucial reasons why a Discovery Phase might lead us to abandon a project:

- One reason to consider abandoning a project during the Discovery Phase is if it doesn't align with the company's 
  goals or values. If the project doesn't fit into the company's long-term plans, it's better to move on early and 
  focus on projects that will help the company grow. Additionally, if the project goes against the company's values 
  or mission, it could harm its reputation and lead to negative consequences.

- Another reason to abandon a project during the Discovery Phase is if it's not financially viable. During the 
  Discovery Phase, the team should be conducting research to determine the potential Return On Investment (ROI) of 
  the project. If the projected ROI isn't high enough, it's not worth pursuing the project. Focusing on projects 
  that will generate a better ROI and help the company grow is better.

- Finally, if the team encounters significant roadblocks during the Discovery Phase that can't be overcome, it may 
  be time to abandon the project. This could include issues such as technical limitations or market saturation. If 
  the team can't find a way around these obstacles, it's better to cut their losses and focus on other projects.

In conclusion, deciding not to continue with the development of a new project during the Discovery Phase is a 
difficult decision, but sometimes it's the best one for the company. By staying objective and considering all 
factors, the team can make an informed decision about whether to continue or abandon the project. Ultimately, the 
goal is to focus on projects that align with the company's goals and values, have a high potential ROI, and can be 
completed successfully.

One of the core objectives of HelloWorld teams, throughout the Discovery Phase, is to help stakeholders evaluate 
products and projects so they can understand whether it's worth pursuing them.

Cheers!!


Discovery Phase: decide whether a project or a product is worth pursuing


A twelve-factor app never relies on the implicit existence of system-wide packages. It declares all dependencies,
completely and exactly, via a dependency declaration manifest.

Furthermore, it uses a dependency isolation tool during execution to ensure that no implicit dependencies "leak in"
from the surrounding system.

The full and explicit dependency specification is applied uniformly to both production and development.


Dependencies: Explicitly declare and isolate dependencies


Starting a new project can be exciting, but it's important to take the time to plan and prepare. A Discovery Phase 
is a crucial step in any project that involves User Experience (UX), Engineering and DevOps. This phase involves research, analysis, and planning that will inform the project's design and development. In this blog post, we will discuss why a Discovery Phase is important and how to get started.

Here are the reasons why a Discovery Phase is extremely important and should take place before actual development:

- The first reason to start a project with a Discovery Phase is to gain a deeper understanding of the users and their needs. A Discovery Phase involves user research, which can include surveys, interviews, and observations. By understanding the users' needs, pain points, and preferences, we can create a more effective and user-friendly product. This knowledge will inform the project's design and development, leading to a better user experience.

- Another reason to start a project with a Discovery Phase is to identify potential roadblocks and opportunities. During this phase, we will analyze the data and identify trends and patterns. This analysis can help us identify potential issues and opportunities that may arise during the project's development. By identifying these roadblocks early, we can develop a plan to mitigate them, ensuring that the project stays on track.

- The Discovery Phase is also an opportunity to establish a clear project vision and strategy. By gathering data and analyzing it, we can develop a project plan that is aligned with the core business goals and user needs. This plan will help guide the project's design and development, ensuring that everyone involved is working towards a common goal.

- Finally, a Discovery Phase can save time and money in the long run. By investing time in research and planning at the beginning of the project, we can avoid costly mistakes and redesigns later on. By establishing a clear project vision and strategy, we can ensure that everyone involved is working towards the same goal, reducing the risk of miscommunication and delays.

In conclusion, starting a project with a Discovery Phase is an essential step for any project that involves UX, Engineering and DevOps. By gaining a deeper understanding of the users and their needs, identifying potential roadblocks and opportunities, establishing a clear project vision and strategy, and saving time and money in the long run, we can ensure that the project is successful.

HelloWorld highly advises its customers to start all new projects with a Discovery Phase, so we collaborate closely to plan, analyze and prepare the core business needs and ensure that we are about to create a successful and user-friendly product.

Cheers!!


Discovery Phase: what it is and why we start new projects with it


A twelve-factor app is always tracked in a version control system, such as Git, Mercurial, or Subversion.

A copy of the revision tracking database is known as a code repository, often shortened to code repo or just repo.

There is only one codebase per app, but there will be many deploys of the app.

A deploy is a running instance of the app. This is typically a production site, and one or more staging sites.

Additionally, every developer has a copy of the app running in their local development environment, each of which also qualifies as a deploy.


Codebase: One codebase tracked in revision control, many deploys


So you have to deal with a task that seems boring and dull and you keep pushing and pushing it till the very end of the milestone. In the end, you feel bad about your performance and you give in.

This is a typical occasion since we might have to deal with things that we don't consider cool and shiny from time to time throughout our careers. You know what? This is normal.

What is the solution? Break the task into small tangible steps so you make progress, ask for a pair programming session so you get some motivation from a teammate, and in general, don't let it take you down.

Procrastination is something that happens to all of us so you need to find ways to fight it.


Fight procrastination


Creating solid documentation for the applications we build is not an optional thing to do.

Through it, we ensure the continuity of the project and the maintainability of the codebase itself while the value and the quality of the deliverables increase hugely.

That said, engineering teams should take seriously the documentation process of an application to guarantee its longevity and extendability in the near future.


Documenting is an important part of engineering


DevOps is an Agile approach that helps modern tech teams ship value in an efficient way.

It is cross-functional by its nature (Development + Operations) facilitating greater collaboration.

This means, that it connects engineers and operations in a better and more transparent way that results in successful products.

That said, the gain of DevOps is frequent, streamlined, and high-quality software releases.


DevOps is a culture


Code reviews speak volumes about the team’s health and collaboration.

Through them, the team ensures that best practices are applied and that the definition of done criteria are met.

These are classless so that all engineers, no matter their seniority level can participate and share thoughts, question things and make proposals.

Because of all these, code reviews bring engineers closer, push them to grow even more, and help them collaborate in an efficient and healthy way with each other.


Enforce classless code reviews


Whenever you feel stuck or overwhelmed ask for help! Don’t hang around aimlessly.

Do your best, do some research, and if you hit a wall, ask around. Ask your teammates. Ask in the channels. Don’t let it take you down!

Asking for support is a healthy attitude that pays off.

After all, the team is responsible for a deliverable, not individuals.


Build a healthy environment where asking for support is welcomed


Starting our day with a well-established plan is quite beneficial.

Daily scrum meetings (or daily standups) give us the opportunity to take a step back, prioritize our workload and focus on the deliverables that should be done first.

That way, we avoid randomness, and we can even manage expedites within the day more efficiently.

If we don’t work with a plan, things will get chaotic fast, and this won’t end up that well in terms of our productivity and mental fatigue.


Prioritize your workload on a daily basis to avoid burnout


Code coverage is a great way to check whether an application is covered with tests in the first place.

On the other hand, this percentage might lead us to a false positive belief since it doesn’t tell us much about the quality of our test suite.

Do we test the most critical user journeys using integration tests?

If we don’t do so, then a high code coverage percentage is a highly misleading indicator.


Code coverage percentage does not reflect the quality of the tests


Agile enforces us to work in an incremental way. Splitting the workload that way is great as long as we don’t make random decisions down the road.

Moving into steps without following a proper architectural plan is going to bite us sooner or later.

Avoid starting any implementation without having a solid design document in place.


Do not forget to design first and implement afterward


The more complex problems we try to solve through technology, the more complex applications we build.

Complex applications require people with various skills or even various teams of specialized people to get involved.

Engineers should be able to collaborate and communicate with peers and business stakeholders to design and develop such applications.

That said, sharpening people skills seems more important than ever before.


The myth of the lone wolf software engineer is dead


A tested application means that we ship an application that is solid and functional.

A testable application means we ship an application that can be tested, extended, and maintained easily.

If we don’t write tests from the very start, then we miss the opportunity to structure our code in a way it can easily get tested and extended in the near future.

Such an approach reduces the value of the delivered codebase and opens the door for technical debt.


Stop leaving tests for the end


Stop ignoring technical debt and start treating it with respect.

Create stories with a refactoring goal in mind 🧠♻️, put them into the backlog , and prioritize them accordingly 😉


Treat technical debt with respect


Keep engineers and business stakeholders as close as possible!!

Separating engineering and business teams can lead to uncertain results.

Bring these 2 worlds together, to minimize risk and ship solutions that solve actual problems 🏆


Keep engineers and business stakeholders as close as possible


Define what is considered done!!

The "Definition of Done" is a collection of quality standards a story should meet, so it can be considered done.

Through DoD, teams establish a common language when shipping a new increment of value so everyone is on the same page ✅


Define what is considered done


Avoid premature over-optimization of your code!

Always remember the "Rule Of Three":

- Does code exist that looks identical?
- Does the code repeat the same knowledge and logic?
- If yes, wait until you have at least three code duplicates before you make an abstraction 😎


Avoid premature over-optimization of your code. Always remember the Rule Of Three


Small and repeating iterations help a team stay focused and constantly ship value.

Such iterations force business and engineering people to work closely and minimize risk.

That way, we can move together towards our high goal while evaluating decisions all way long in order to ship something really useful in the end 😎


Publications about "engineering"

By HelloWorld PC

Pulumi vs Terraform

By HelloWorld PC

Processes: Execute the app as one or more stateless processes

By HelloWorld PC

Create a Modern Website: Make the website a Progressive Web App

By HelloWorld PC

Engineering without DevOps is like Yin without Yang

By HelloWorld PC

Build, release, run: Strictly separate build and run stages

By HelloWorld PC

Create a Modern Website: Add favicons and share image

By HelloWorld PC

Backing services: Treat backing services as attached resources

By HelloWorld PC

Create a Modern Website: Create the routing of all project pages

By HelloWorld PC

Config: Store config in the environment

By HelloWorld PC

Discovery Phase: deliverables