#softwareegineering — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #softwareegineering, aggregated by home.social.
-
From the Laws of Software Engineering:
Cunningham's Law
The best way to get the correct answer on the Internet is not to ask a question, it's to post the wrong answer.😂
-
From the Laws of Software Engineering:
Cunningham's Law
The best way to get the correct answer on the Internet is not to ask a question, it's to post the wrong answer.😂
-
From the Laws of Software Engineering:
Cunningham's Law
The best way to get the correct answer on the Internet is not to ask a question, it's to post the wrong answer.😂
-
From the Laws of Software Engineering:
Cunningham's Law
The best way to get the correct answer on the Internet is not to ask a question, it's to post the wrong answer.😂
-
From the Laws of Software Engineering:
Cunningham's Law
The best way to get the correct answer on the Internet is not to ask a question, it's to post the wrong answer.😂
-
I receive this question many times:
- Marcos, should I take a certification on AWS? -
This is something really important, to take very seriously, because we have to target our efforts properly when we talk about our careers.
As happens on many occasions, it depends… but not completely.
There is a way for you to know if what you want is a certification in a technology.
And you can figure this out by subscribing to my newsletter, because tomorrow I will send an email to more than 1.4K software engineers and share the solution to that puzzle
I have a very clear answer for you, get it now 👇🏻
-
I receive this question many times:
- Marcos, should I take a certification on AWS? -
This is something really important, to take very seriously, because we have to target our efforts properly when we talk about our careers.
As happens on many occasions, it depends… but not completely.
There is a way for you to know if what you want is a certification in a technology.
And you can figure this out by subscribing to my newsletter, because tomorrow I will send an email to more than 1.4K software engineers and share the solution to that puzzle
I have a very clear answer for you, get it now 👇🏻
-
I receive this question many times:
- Marcos, should I take a certification on AWS? -
This is something really important, to take very seriously, because we have to target our efforts properly when we talk about our careers.
As happens on many occasions, it depends… but not completely.
There is a way for you to know if what you want is a certification in a technology.
And you can figure this out by subscribing to my newsletter, because tomorrow I will send an email to more than 1.4K software engineers and share the solution to that puzzle
I have a very clear answer for you, get it now 👇🏻
-
These are my MUST-HAVE steps for a pipeline to build a piece of software 👇🏻
🟢 Build: Whatever build means for your application.
🟢 Test: Run all tests that make sense on the Continuous Integration stage. Nice to have: Create a report that could be visible by the pipeline runner tool you are using.
🟢 Quality Gates: Ensuring that your code follows the right standards. Things like SonarQube checks and others are in this stage.
🟢 Publish: Here, you have to package your application and publish it into an artifact repository, like Artifactory or AWS Elastic Container Registry, so it’s available for shipping to production.
🟢 Deliver: This stage will update your GitOps repository or the configuration that rules the version of your applications, with the new version. That change of version should trigger another pipeline to deploy the application in production
Would you add or remove something?
I wrote a post about what a CI/CD pipeline should look like and how to make it in a way that could be reused by all your dev teams, no matter what coding language they are using for their applications
You can read it here 👉🏼 https://newsletter.optimistengineer.com/p/how-to-achieve-a-golden-cicd-pipeline?r=nw9bj&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false
#softwareegineering #leadership #SoftwareDevelopment #coding #CICD
-
These are my MUST-HAVE steps for a pipeline to build a piece of software 👇🏻
🟢 Build: Whatever build means for your application.
🟢 Test: Run all tests that make sense on the Continuous Integration stage. Nice to have: Create a report that could be visible by the pipeline runner tool you are using.
🟢 Quality Gates: Ensuring that your code follows the right standards. Things like SonarQube checks and others are in this stage.
🟢 Publish: Here, you have to package your application and publish it into an artifact repository, like Artifactory or AWS Elastic Container Registry, so it’s available for shipping to production.
🟢 Deliver: This stage will update your GitOps repository or the configuration that rules the version of your applications, with the new version. That change of version should trigger another pipeline to deploy the application in production
Would you add or remove something?
I wrote a post about what a CI/CD pipeline should look like and how to make it in a way that could be reused by all your dev teams, no matter what coding language they are using for their applications
You can read it here 👉🏼 https://newsletter.optimistengineer.com/p/how-to-achieve-a-golden-cicd-pipeline?r=nw9bj&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false
#softwareegineering #leadership #SoftwareDevelopment #coding #CICD
-
These are my MUST-HAVE steps for a pipeline to build a piece of software 👇🏻
🟢 Build: Whatever build means for your application.
🟢 Test: Run all tests that make sense on the Continuous Integration stage. Nice to have: Create a report that could be visible by the pipeline runner tool you are using.
🟢 Quality Gates: Ensuring that your code follows the right standards. Things like SonarQube checks and others are in this stage.
🟢 Publish: Here, you have to package your application and publish it into an artifact repository, like Artifactory or AWS Elastic Container Registry, so it’s available for shipping to production.
🟢 Deliver: This stage will update your GitOps repository or the configuration that rules the version of your applications, with the new version. That change of version should trigger another pipeline to deploy the application in production
Would you add or remove something?
I wrote a post about what a CI/CD pipeline should look like and how to make it in a way that could be reused by all your dev teams, no matter what coding language they are using for their applications
You can read it here 👉🏼 https://newsletter.optimistengineer.com/p/how-to-achieve-a-golden-cicd-pipeline?r=nw9bj&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false
#softwareegineering #leadership #SoftwareDevelopment #coding #CICD
-
These are my MUST-HAVE steps for a pipeline to build a piece of software 👇🏻
🟢 Build: Whatever build means for your application.
🟢 Test: Run all tests that make sense on the Continuous Integration stage. Nice to have: Create a report that could be visible by the pipeline runner tool you are using.
🟢 Quality Gates: Ensuring that your code follows the right standards. Things like SonarQube checks and others are in this stage.
🟢 Publish: Here, you have to package your application and publish it into an artifact repository, like Artifactory or AWS Elastic Container Registry, so it’s available for shipping to production.
🟢 Deliver: This stage will update your GitOps repository or the configuration that rules the version of your applications, with the new version. That change of version should trigger another pipeline to deploy the application in production
Would you add or remove something?
I wrote a post about what a CI/CD pipeline should look like and how to make it in a way that could be reused by all your dev teams, no matter what coding language they are using for their applications
You can read it here 👉🏼 https://newsletter.optimistengineer.com/p/how-to-achieve-a-golden-cicd-pipeline?r=nw9bj&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false
#softwareegineering #leadership #SoftwareDevelopment #coding #CICD