disappointing to see this grey, because i think there's a lot of truth in here. i think a lot of developers are used to wielding great power with technology, g

disappointing to see this grey, because i think there's a lot of truth in here. i think a lot of developers are used to wielding great power with technology, getting immediate visceral feedback, shipping, and whatever else. this gives them an impression that fixing people problems is just as easy - the equivalent of opening up the ol' IDE and rocking out for 8 uninterrupted hours, getting an MVP up. the differences, though, are crucial. the compiler doesn't lie to you - you missed a semicolon; that's not the case with people. the in memory database doesn't have another agenda; again, not the case with people. the UI doesn't aspire to be something greater, or protect itself; managers often do. i really appreciate that individuals try - i just don't think it's really worth it, if the org is > 15 or so people.