You can't just use /images/name.png as the URL to the image, because that's not where the image lives. The image is located at /storage/app/media/images/name.png because the media library lives at /storage/app/media. You can use a helper like the | media filter recommended above so you don't have to care about where the library is, but no matter what, if you want the images to load the URL you use has to reflect where they live (or at least a way to get to it).
My guess as to what your techie probably did was to change the server configuration so that requests to /images/name.png get automatically forwarded to the /storage/app/media/images folder. There are a number of ways to do that, and I'm guessing he probably picked modifying some code that gets overwritten if the system is updated, which is obviously a terrible choice.
If you'd like to work with someone that is an expert in these matters, then feel free to shoot me an email at octobercms@luketowers.ca.