Contributed by Alex Verdurmen, Managing Director Hifyre
Every developer knows there is nothing more frustrating than completing a project only to...
For further actions, you may consider blocking this person and/or reporting abuse
Ugh. Yes! I've been trying to preach "Design Before Develop" to my engineering team for over a year now and it always results in an eye roll and a brief silence before someone changes the subject. This post brings up the exact points that I try to use in my ploys. Great post, thank you for sharing it!
Our team loves it! It's an effort for the transition initially, but everyone wins in the end.
I have a hard time adopting any of these habits and/or processes. Thanks for the post/resources.
Are you speaking in the context of front end & UI development or project overall? When planning I try to focus on the domain and then the tangibles (inb4 MVP, MVVM layered architectures). When it comes down to it though, in my experience wireframes are a great way to go like you said it removes ambiguity and focuses on results.
Project overall. A lot of our work invollves custom software that ties into the front end design enough that it's pretty important to consider the moving parts up front.
Haven't done much UI work that's why I asked. I'd expect it to be even more important recently with heavier in-browser clients