Posted on

Herding Code 108: Jin Yang and Nathan Bowers on Web Design

This episode of Herding Code continues a discussion / argument that Jon started with Jin Yang and Nathan Bowers on Twitter a few weeks ago after reading a post he liked from a product designer at Quora about how they don’t use Photoshop in their design process. What’s the role of visual design in the web design process? Can designers and developers ever be friends? Are HTML and CSS the lingua franca of designers and developers, or just an implementation detail? Do designers need to know HTML to be good web designers? Listen as Jin and Nathan set Jon straight.

  • Jon tries to get Jin and Nathan upset, but they both start by agreeing
  • Nathan mentions that Photoshop is a production tool, not a design tool
  • Jin and Jon talk about the value of wireframes, and how the transition from wireframe
  • Nathan talks about how different clients have different demands – Quora can prototype rapidly for their own product, but some clients will require high quality graphic deliverables
  • Kevin asks developers and designers work together in HTML based design – who does the HTML?
  • Jon talks about how moving the discussion from images to a client accessible stage / demo server early in the project helps everyone communicate
  • Jon asks both which sorts of sites work better for HTML based design because they’re mostly textual
  • Jon asks Jin how he works on StackExchange proposals
  • Nathan talks about how the site focus dictates the design process, and how he’s mostly done with Photoshop
  • Kevin asks if there’s a place for a tool that’s somewhere between the purely visual Photoshop world and HTML: Nathan says it’d be nice, Jon says the generated HTML is always horrible, and Jin says that’s why he thinks designers need some HTML smarts
  • Nathan brings up Jon’s post on the Designer / Developer Workflow Crisis, and Jin talks about his post on Web Designers and Coding
  • The talk moves to a visual-first design focus can end up with a website that doesn’t provide the information the users actually want, and some favorite XKCD and The Oatmeal links are shared
  • Jin and Jon talk about how your clients aren’t really the end customers of your design, the users are
  • Nathan asks Jon about how he thinks the design / developer workflow should be
  • Nathan, Scott K, Jon, and Jin Jin talk about how developers can involved in the development process after the "design handoff"
  • Jin talks about how developers should be part of the design process, and Jon and Scott K talk about how important it is for the whole team to know the context of what they’re doing
  • Kevin mentions that his wife is a web designer who doesn’t do HTML, and every hastily backpedals
  • Jon and Jin talk about how the background reasons for wanting designers to know HTML can still be met by the designer knowing the constraints of the web medium really well
  • Kevin talks about how today’s Ajax heavy sites aren’t really just HTML anymore
  • Jon talks about how he hates the new trend towards single page applications
  • Kevin says that he thinks that saying designers should know HTML is like saying developers should know how to design, but Jin says that HTML isn’t programming, it’s the medium that both designers and developers are producing for
  • Jon says that he thinks developers should try to learn more design
  • Scott K asks how developers can learn design, and Jin and Nathan share tips
  • Jon mentions some great talks by Robby Ingebretsen on design fundamentals for developers
  • Kevin asks how much of design is just natural talent
  • Jon talks about how he likes design discussions among the whole dev team, and Nathan says that it’s important for the team to be able to communicate about the business and strategy for their project as well
  • Nathan talks about the book Mindfulness which shows how working through a lot of ideas helps you come up with great ideas
  • Jon talks about how a process that allows for continuous change throughout the project allows you to continue to shape the design as you go, and Scott K accuses him of being agile
  • Jon asks Jin how he interacts with a team who develops on Windows when he’s on a Mac, and they discuss how Firebug (and similar tools) allow for cross platform development
  • Jon asks what sites should be designed using Photoshop / visual design first
  • Jin asks Nathan about his thoughts on 960.gs, and Jon rants about how grid systems fight semantic design
  • Scott K talks about the Flex Box Model will make it easier to design with grids without giving up on semantic markup
  • Jin mentions HTML5 shims, but Scott K says that doesn’t work as well for mobile
  • Jin talks about how the real challenge in StackExchange design is in creating an emotional reaction, and Kevin says that’s the result he cares about a lot more than HTML

Show Links:

Jin’s link list for developers who want to learn more about design

Download / Listen:

Herding Code 108: Jin Yang and Nathan Bowers on Web Design

[audio://herdingcode.com/wp-content/uploads/HerdingCode-0108-Jin-Yang-and-Nathan-Bowers-on-User-Experience-Design.mp3]

Posted on

Herding Code 107: Apple Subscription fees, Nokia, Reflector, Mono, Watson, CardSpace, and IE9 RC

In this episode of Herding Code, the guys talk nonsense for over an hour.

  • Topic: The Apple Store 30% fee for App Subscriptions – who’s surprised, what apps will it affect, etc.
  • The conversation shifts to Kindle, and whether content focused apps can move to HTML only.
  • Topic: Windows Mobile deal with Nokia – will it help?
  • K Scott thinks it’s very late for both parties.
  • Jon doesn’t think there’s much loyalty in the smartphone market since people get a new phone every few years.
  • There’s some discussion about where this leaves the enterprise phone market. Kevin thinks that Microsoft should just have focused on the enterprise.
  • Topic: Reflector – was free, was going to be free forever, but now it’s not.
  • Kevin and K Scott talk about how bad it is from a community perspective.
  • Kevin wonders how many developers or updates are required to keep Reflector going?
  • Jon, K Scott, and Kevin talk about what they use Reflector for.
  • The guys talk about open source alternative – IL Spy, Cecil based disassemblers, JetBrains’s new decompiler.
  • Kevin and Jon talk about why a $35 cost is a bigger problem than it sounds like.
  • Topic: Mono 2.10 and Moonlight 4 Preview 1 released – what does it mean?!
  • Topic: Watson plays Jeopardy. Jon asks if it just called into Wolfram Alpha, and K Scott wonders if has a Sean Conery mode.
  • Topic: CardSpace 2.0 won’t be shipped. Nobody but Jon cares.
  • Scott K talks about the LastPass. Jon asks how that work on different computers, mobile, etc.
  • Topic: Internet Explorer 9 RC is out
  • Jon talks about how IE9RC works better with Visual Studio now.
  • Jon likes the simplified UI, but talks about a few of the annoyances he’s run into.
  • Jon and Kevin talk about the tab UI handling.
  • Jon talks about how some sites break on JavaScript
  • Scott K brings up the blog post from Mozilla asking if IE9 is a modern browser.
  • The guys talk about IE9 supported features, general HTML5 support across browsers, etc.
  • Kevin says that the biggest problem with IE is the slow ship cycle. Kevin and Scott K discuss the possibility of splitting out an enterprise browser.
  • Kevin talks about the GPU acceleration in IE9 and how he thinks it’s overblown.
  • Jon talks about the lack of XP support for IE9.
  • The guys talk about how they wish there was an IE6 standalone.

Show Links:

Download / Listen:

Herding Code 107: Apple Subscription fees, Nokia, Reflector, Mono, Watson, CardSpace, and IE9 RC

[audio://herdingcode.com/wp-content/uploads/HerdingCode-0107-Apple-Subscription-fees-Nokia-Reflector-Mono-Watson-CardSpace-IE9-RC.mp3]

JetBrains code coverage tool for .NET apps and Silverlight, dotCover, will soon get an update with improved filtering, reporting, and presentation of unit test coverage results. Get a 30-day trial and a fair price at jetbrains.com/dotcover. By the way, buying dotCover entitles you for a full year of free upgrades.