3 ms·
It's not to win an argument but rather to share it with other developers (and get feedback). So your request to the boss will sound like "I'm hesitant if this p
by AlexanderZ 14y ago
It's not to win an argument but rather to share it with other developers (and get feedback). So your request to the boss will sound like "I'm hesitant if this piece of code is the best way to do it, can I show it to the world?"
- jiggy2011 14y agoWell, saying that might sound like you are suggesting you don't know what you are doing. Besides it's unlikely that you are going to get meaningful feedback based on one chunk of code without the context of all the other stuff it interacts with. If that level of peer review is really important to you , then you would be best off releasing the source to your entire app.
- AlexanderZ 14y agoHave you been following all the Ruby discussions in the past few days? A single action from a complex controller in Basecamp would be enough for me to understand how 37 Signals are handling the not so skinny controller stuff. It would be much more useful than seeing another 'create user and send email' stuff, which I see in almost every article about controllers.
- jiggy2011 14y agoNot really, but I don't think seeing a bunch of code with calls to hidden function would be all that useful. It is simple enough to distill your approach down into some fictional code that can be easily understood. I do it all the time when I'm posting questions on Stack Overflow and don't want to stick the real code on there. It might be nice to see some of their production code, but it doesn't really offer any value to them other than being able to fire a shot in an internet war.