Remove Meeting Remove Scalability Remove Team Building Remove Test-Driven Development
article thumbnail

Forward Thinking Tech Leaders at IO Seeking Big Data Engineer

CTOvision

If you are, or know of anyone who is, interested in this position (and if you can meet most of their qualifications) please connect with IO right away, they want to talk with you like right away. Modular code, test-driven development, quick iterations involving stakeholders. Driven by pursuit of elegant solutions.

Big Data 107
article thumbnail

AoAD2 Practice: No Bugs

James Shore

Test-Driven Development. Test-driven development is your defect-elimination workhorse. To enhance the benefits of test-driven development, support energized work, and use pairing or mobbing to bring multiple perspectives to bear on every line of code. Test-Driven Development.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Velocity 2019 will focus on the rise of cloud native infrastructure

O'Reilly Media - Ideas

The Cloud Native Computing Foundation (CNCF) defines cloud native as a set of technologies designed to: empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. For many developers, these changes are simply hard to implement.”.

article thumbnail

20 Deadline Management Tips Scrum Masters Should Consider

Codegiant

And the very first question I shot their way was: “What are some of your biggest software development nightmares?” You’d be shocked to know that delayed feature releases, multiple bug occurrences, late fixes, and the inability to meet the deadlines topped the list. Deadlines are any software development team’s biggest nightmare.

SCRUM 52
article thumbnail

20 Deadline Management Tips Scrum Masters Should Consider

Codegiant

And the very first question I shot their way was: “What are some of your biggest software development nightmares?” ” You’d be shocked to know that delayed feature releases, multiple bug occurrences, late fixes, and the inability to meet the deadlines topped the list. Let’s dive in straight away.

SCRUM 52