I've worked as a Web Engineer, Writer, Communications Manager, and Marketing Director at companies such as Apple, Salon.com, StumbleUpon, and Moovweb. My research into the Social Science of Telecommunications at UC Berkeley, and while earning MBA in Organizational Behavior, showed me that the human instinct to network is vital enough to thrive in any medium that allows one person to connect to another.
M. David's articles
Higher-order functions can take other functions as arguments or return a function as a result. Learn how to use them and why they're useful.
M. David Green discusses pair programming, examining what it takes for two developers working together to achieve the productivity and quality improvements that come from pairing.
M. David Green presents tools, tricks, and practices for improving the remote working experience for yourself, your team, your manager, and your company.
The product backlog is one of the most controversial artifacts of an agile organization. Everybody seems to have an opinion about how it should work.
M. David Green reviews new features of modern JavaScript, such as classes and arrow functions, looking at when you should and perhaps shouldn't use them.
Error monitoring can save you when things start to fall apart. Learn how to get Airbrake working with your JavaScript web apps.
Read Grab Our Free Printable Functional JavaScript Cheat Sheet and learn JavaScript with SitePoint. Our web development and design tutorials, courses, and books will teach you HTML, CSS, JavaScript, PHP, Python, and more.
Functional code is often touted as easier to test. M. David Green examines that claim and demonstrates how to get started testing functional JavaScript.
In this episode of the Versioning Show, Tim and David are joined by Sarah Drasner, a teacher, author, consultant and staff writer at CSS-Tricks.
In this episode of the Versioning Show, Tim and David are joined by Donovan Hutchinson, a developer, teacher and proprietor of CSSanimation.rocks.
In this exclusive book excerpt from Scrum: Novice to Ninja, we take a look at troubleshooting Scrum and how to overcome obstacles in the process.
velocity is how a scrum team measures the amount of work they can complete in a typical sprint. By tracking the number of story points the team can
Declaring a story to be done is a means of verifying that all of its critical aspects have been completed based on the way each team works.
One of the most basic artifacts of scrum for web and mobile work is the story that describes a feature to be worked on.
If the daily standup is one of the most iconic rituals of scrum, the sprint retrospective may be the most representative of the agile philosophy.
M. David Green uses filtering to limit a data set & chaining to combine the results with map/reduce. The result—clean code that performs complex operations.
A scrum team doesn't work in a vacuum. There's usually an organization that exists around scrum, and that supports the efforts of the scrum team
At the end of the sprint, everything that was worked on for the current sprint is demonstrated for the team, the product owner, and observers.
In this article, we will talk about Daily Standup, the objective, and the benefits from using it.
In this article, you will learn what is Sprint Planning. Sprint planning is hosted by the scrum master, but the person responsible for most of the content that goes into a sprint planning is the product owner.
In this article, you will learn about Scrum Rituals. Each ritual is a face-to-face gathering in real time, which takes people away from the work they’re doing, and offers them the opportunity to have targeted communication with each other about the context of that work.
In this article, we will talk about Product Owner. A product owner usually belongs to a department such as Product or Customer Support, and spends time working with customers.
In this chapter, we’ll go over the critical roles of scrum master, product owner, and team member.
Scrum is one of several techniques for managing product development organizations, lumped under the broad category of agile software development.
In this episode, Tim and David are joined by Glenn Goodrich, aka Ruprict, a developer by day and SitePoint's Ruby Channel editor by night.
David and Tim are joined by Hampton Catlin, creator of Sass, Haml and other tools and services such as Wikipedia Mobile, Tritium and Moovweb.
In this episode, David and Tim are joined by Ethan Marcotte, a well-known designer who coined the term Responsive Web Design.
In this episode, Tim and David are joined by Rachel Andrew, co-creator of Perch CMS and leading expert on CSS Grid Layouts.
In this episode, Tim and David are joined by Alex Fitzpatrick, Deputy Tech Editor for Time Magazine.
Tim and David are joined by Ken Wheeler, a Formidable JavaScript programmer well known for open-source projects like Slick Carousel.