128 reputation
7
bio website hammerproject.com
location Perth, Australia
age 29
visits member for 4 years, 2 months
seen Nov 12 '13 at 8:54

Enemy ships in sector 47..


Jul
24
comment What is the best practice for saving TimeZones in the database?
stackoverflow.com/questions/2532729/…
Aug
17
comment Are Domain Objects in Domain Driven Design only supposed to be write-only?
+1 for starting with the jucy bits. In addition: biting off just the CQS (skipping the 'events' part for now) could be a good place to start.
Jan
16
awarded  Autobiographer
Aug
16
awarded  Citizen Patrol
Aug
16
awarded  Scholar
May
11
awarded  Commentator
May
11
awarded  Student
Sep
30
comment What hat should a programmer not wear?
@tcrosley I think i get where you're coming from. The thing that jumped out at me from your answer was the inference or suggestion that since there are separate UI/UX/"human factors" people, a developer should not concern herself with the experience of the user. Maybe you're not even suggesting that. But it's a popular misguided belief. And sure lots of valuable software gets created from those who think that way. But great software comes when developers engage the users experience first and are thinking about what the user might want/need/think every step of the coding process.
Sep
30
comment What hat should a programmer not wear?
@tcrosley": "passed on to the programmer" mmm.. not really a fan of this either. Designers and developers should work together. Not in isolation. Ok to be fair, "passing something on" may not be considered isolated, but the definition should not be contained in a spec. The "spec" (if you must stick with that word) should evolve with the communication of the designer and developers working together. The idea that software can be created by this "pass the parcel" approach is ridiculous.
Sep
30
awarded  Critic
Sep
30
comment What hat should a programmer not wear?
Developers should not only design the UX/UI (with or without the aid of dedicated graphic/interaction designers) but it should be a priority over developing the functionality. Another way: the usability should be more important than the functionality (which is logical in that the worlds greatest hammer can't hammer nails without a handle).
Sep
30
awarded  Supporter
Sep
30
comment What hat should a programmer not wear?
+1 about being careful mentioning certain experience.