Hey, I have heard two different trains of thoughts regarding how you describe projects on a resume, with the only commonality between both paths of advice is "Don't use more then two bullets when describing each". I just want some people with experience reviewing resumes/interviewing people to just chime in on which is the better way to go.

1) Describe the project, not the work.

By that I mean I read people saying essentially "Don't waste lines saying you wrote this Android app in C# with Xamarin and the CocosSharp library, just say you wrote an Android app that is a game that does x y and z. Save describing how you made it for the interviews".

2) Describe the work, not the project.

This way they know if the experience is relevant to them and to give them an idea of how you did it. They are gonna hire you as a developer, not for your ideas.

Basically, don't describe what the app/website/computer software does, explain how you made it. Did you use a game engine? library? What JavaScript libraries did you feel were appropriate? Did you make it in native Java? etc.

Basically, I have heard people go both ways, explain WHAT the project is, or explain HOW the project was made.

If any people with hiring/resume reviewing experience can chime in, which way do you prefer and why?

EDIT: I guess I should throw in another thought. I have though of "What if you use one bullet point to describe the project, then the next to describe how it was made?", but then that contradicts how bullet points are intended to be used. When using bullets, every point is ideally suppose to follow the same flow of logic in a list. Changing them into Description/How bullets sort of defeats the purpose of bullets since it's two different trains of thoughts. I may be wrong about this though, that's just how I was taught to use them.