Content
@
0 reply
0 recast
2 reactions
grin
@grin
what's some programming advice that's considered common sense or that you hear often, but is actually bad advice?
15 replies
7 recasts
16 reactions
Cameron Armstrong
@cameron
Situational, but “it doesn’t need to look pretty, it just has to work” is pretty bad advice for stuff that needs feedback from nontechnical people. Bad/ugly UX and “it’s just a mock-up” things like dummy data is often very confusing and will often derail user interviews in strange ways
3 replies
0 recast
4 reactions
typeof.eth 🔵
@typeof.eth
💯💯💯 The only type of software dev I don’t vibe with are the ones who are blind to the fact that we’re building products for end users. The most elegant code isn’t worth shit if no one is using it.
2 replies
0 recast
3 reactions
Phil Cockfield
@pjc
Related is: "if you're not embarrassed of it, you shipped to late." same same ↑ (there's a time and place where that is totally true, but still...)
0 reply
0 recast
0 reaction
Phil Cockfield
@pjc
Oh man, I was just about to come in and say something to that effect. The amount of damage the "MVP" (Minimum Viable Product) concept has wrought through engineers having a free pass to say "fuck it, doesn't have to look good" thereby causing all sorts of false-negatives on the product concept to wrack up from testing
1 reply
0 recast
0 reaction
