Displaying data in WordPress often involves more than just echoing. I mean, echo will work and display output just fine, but if you want to make sure your code is as secure as possible, it's always a good idea to attempt to clean whatever data you are using first.
I've built quite a few websites based on other people's designs, Along the way I've stumbled across a few common issues that have significantly slowed the overall design to development process. These are some of the things I think are important to look out for when designing for the web.
I work at a small studio with two other people, and more often than not, I work on projects where design and development cross paths. I’ve built a lot of sites on my own, inherited a lot of sites, worked on sites other designers have designed, worked on my own boilerplate code, finished half-finished sites done by other studios, interpreted designs on the fly (especially designs with no mobile versions) and worked on sites collaboratively with other developers.
Ever run into the problem of needing to output data from a PHP loop into separate wrapping divs? You could use the same loop twice to return data into two different divs. Or you could use this is a super handy technique to generate data *inside* multiple different elements using the same loop.
If you are serving a lot of images on a page, using srcset is a really handy way to effectively cut down page size. WordPress does a lot of heavy lifting with it's great image management and baked in srcset function, so much so you can forget about get_the_post_thumbnail() entirely.
These methods might seem simple and interchangeable, but for beginners it can be confusing and hard to understand where to use these tags appropriately. Personally, understanding how these two methods work helped me write more understandable and resilient code.