Accenture

APRIL 10, 2019

If you are successful in implementing microservices, your organization will need to continuously develop and operate hundreds or even thousands of independent services. Although possible, achieving a high level of testing automation without addressing quality at the source – when the code is developed – is extremely wasteful.

Microservices 81

Microservices Technical Review Software Review Systems Review 81

MagmaLabs

AUGUST 26, 2021

Reading Time: 11 minutes Nowadays it is relatively easy to become a software developer, but being a truly professional one is not that simple. Learn here how to be the developer that every company and every client wants to have. Being a professional developer is crucial in the software industry. For example.

Software Review 52

Software Review Software Development Weak Development Team Systems Review 52

The Programmer's Paradox

MARCH 16, 2023

These two things tend to make agile an excellent fit for startups and an impossibly bad fit for large projects in large organizations. As a great example, Stand-ups always come to mind. A big problem in development, particularly when a lot of people are introverts, is communication. Mostly that is a bad idea.

Software Review 40

Software Review Systems Review TDD Agile 40

Apiumhub

MAY 31, 2022

Under this premise, we understand that quality is not manufactured, but is part of the development process. Reducing to the basics, within a current agile software team we can find three main roles: Business – Product owner: Captures the requirements requested by the client (stakeholders). What is BDD? Source: flatstack.com.

Software Review 52

Software Review Weak Development Team Technical Review Systems Review 52

Honeycomb

SEPTEMBER 20, 2023

Some of these things are related to cost/benefit tradeoffs, but most are about weak telemetry, instrumentation, and tooling. If you have only instrumented your software with metrics, for example, you have no way of verifying that a spike in api_requests and an identical spike in 503 errors are for the same events (i.e.,

Weak Development Team 52

Weak Development Team Software Review Development Artificial Inteligence 52

Code Simplicity

MAY 10, 2014

Today there was an interesting discussion between Kent Beck , Martin Fowler , and David Heinemeier Hansson on the nature and use of Test-Driven Development (TDD), where one writes tests first and then writes code. ” Example. Well, let’s take some examples to make it clearer. What do I mean by all of this?

Test-Driven Development 40

Test-Driven Development Software Review Weak Development Team Testing 40

Marcusoft

MARCH 11, 2024

For example, the true meaning of words and phrases. According to Dave Farley it’s a common mistake he sees for teams to adopt user stories effectively. The reasons we want to make the stories small are plentiful; it’s easier to manage, implement, fix, deploy, and test… just about anything we do as a software development team.

Software Review 52

Software Review Systems Review TDD Weak Development Team 52

David Walsh

MARCH 19, 2019

What’s more, I teach based on these opinions — thousands of developers in different companies all over the world — which affords me the opportunity to deeply vet my opinions through myriad discussion and debate. So that perspective just makes me feel dumb/inferior as a developer. Why do I suck so much at this?”

Software Review 108

Software Review Weak Development Team Technical Review Tools 108

Modus Create

SEPTEMBER 30, 2020

Another thing that is very important in Agile development practices is exploratory testing. Tests that should not be automated: Test cases that are newly designed and not executed manually at least one time, except when you have TDD or BDD styles. You should run automated tests all the time or as many times the team deems necessary.

Testing 76

Testing Software Review How To Continuous Delivery 76

Apiumhub

JANUARY 6, 2020

Many developers say that they use feature flags or feature toggles, but this year we have realised that there is some confusion around the term that still persists. As software teams seek higher agility, the tools and techniques for software development and delivery continue to evolve every year.

Software Review 70

Software Review Weak Development Team Technical Review Continuous Delivery 70

James Shore

MAY 26, 2021

This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. For many teams, releasing their software is the same as deploying their software.

Software Review 64

Software Review Technical Review Systems Review Test-Driven Development 64

Storm Consulting

MAY 3, 2018

I savoured that simple act of leadership by example. Although it didn’t always work-out that way in the case of C++, these improved languages resulted only in fractional increases in developer productivity. The divide between business and development teams could have been healed by Agile, but it hasn’t worked that way.”.

Software Review 56

Software Review Industry SCRUM Software 56

Codegiant

AUGUST 15, 2021

While producing this blog post, I collaborated with our in-house software development team. And the very first question I shot their way was: “What are some of your biggest software development nightmares?” Deadlines are any software development team’s biggest nightmare. Trust me?—?new

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Marcus Blankenship - Podcasts

JUNE 11, 2020

How can we train teams to consistently produce quality code without negatively impacting productivity? David Green, discuss Agile Dojos and how they can make teams more effective. Dojos provide a six-week training ground where teams focus on recognizing and replicating value by pairing, mobbing, and swarming. Episode 46.

Agile 59

Agile Software Review SCRUM Weak Development Team 59

Apiumhub

JULY 23, 2019

As you may already know, Apiumhub team is software architecture-oriented and reads books for software architects on a weekly basis. Also, it will be a perfect time to list down the most painful issues that are encountered related to bad decisions in Software Architecture as well as possible solutions. It democratizes architecture.

Software Review 53

Software Review Technical Review Software Systems Review 53

Codegiant

AUGUST 15, 2021

While producing this blog post, I collaborated with our in-house software development team. And the very first question I shot their way was: “What are some of your biggest software development nightmares?” Deadlines are any software development team’s biggest nightmare.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Codegiant

AUGUST 15, 2021

While producing this blog post, I collaborated with our in-house software development team. And the very first question I shot their way was: “What are some of your biggest software development nightmares?” Deadlines are any software development team’s biggest nightmare.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Openxcell

APRIL 10, 2023

In this article, we will cover the best practices for React development, including component structure, state management, and performance optimization. Scaling up with React Best Practices Following best practices in React development is crucial for building scalable, maintainable, and performant applications.

Software Review 52

Software Review Technical Review TDD Weak Development Team 52

James Shore

MAY 26, 2021

This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. For many teams, releasing their software is the same as deploying their software. Programmers.

Software Review 52

Software Review Technical Review Systems Review Test-Driven Development 52

Silk and Spinach

JANUARY 22, 2015

But is that coupling good or bad? I can use that model to help me prioritise the Refactor step in my TDD cycle: Connascence of Value is a serious problem, and should be fixed before I do anything else. Not in this case, and a new team member might not pick that up. The only question is: how? Does it have business significance?

Software Review 40

Software Review TDD Testing Weak Development Team 40

Modus Create

AUGUST 24, 2021

Any developer can quickly look at your tests and know the purpose of your functions. For example, one test case shouldn’t be a prerequisite for another to run. They enable you to catch bugs early in the development process. Bear in mind that fixing bugs without running tests could also introduce new bugs into the system.

Testing 40

Testing Software Review Quality Assurance Systems Review 40

Marcus Blankenship - Podcasts

MARCH 4, 2020

Drawing on his 40 years in the software industry, GeePaw’s solution is to develop a thick culture in which certain standards are established across the industry. How the doubling rate resulted in a lack of leaders that can develop an industry discipline (6:34). Developing a common language of change in the trade (24:24).

Software Review 59

Software Review Software Technical Review Culture 59

LaunchDarkly

MAY 28, 2020

And the [inaudible 00:04:10] actually gives you just good and bad in every, pros and cons in every one of those approaches. People think you can only run it before production and say oh, no, that’s the QA, that’s another team. inaudible 00:16:15] for example is like, why not class. And so let’s pick something.

Machine Learning 59

Machine Learning Artificial Inteligence Testing Software Review 59

Marcus Blankenship - Podcasts

AUGUST 8, 2019

Announcer: Welcome to the Programming Leadership Podcast where we help great coders become skilled leaders, and build happy high performing software teams. Progressed, eventually, to leading test teams, and managing testers, and then moving more into agile roles and team coaching. Links: Sponsor: GitPrime. Transcript.

Weak Development Team 40

Weak Development Team Technical Review Software Review CTO Coach 40

James Shore

APRIL 26, 2021

This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. The secret behind successful Delivering zone teams, therefore, is that they never stop designing.

Software Review 83

Software Review Technical Review Systems Review Weak Development Team 83

James Shore

JUNE 4, 2021

This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. Testers, Whole Team. But nobody’s perfect, and teams have blind spots. Ries 2011] (p.

Software Review 75

Software Review Systems Review Test-Driven Development Technical Review 75