Timeline for stuck on a programming problem solution
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2014 at 4:14 | comment | added | David Dimalanta | There is something I disagree about this useful answer not because I'm introverted and nothing to do in spite of professionalism in programming but you see my team leader only concerns about bigger picture (messaging, geofencing, etc.) over smaller picture (list item swapping for example). My team leader tell me it's just a listview swapping and he doesn't care for my help. After a few days of tasks and I'm still stuck. I explain it again for help my leader told me that I should ask for help more. This is why I go solo. I tried everything I could to seek attention for help. | |
| Jul 24, 2012 at 8:37 | vote | accept | maz3tt | ||
| Mar 21, 2011 at 22:44 | comment | added | HorusKol | I find that, half the time, just explaining the problem helps to frame it and provide solution without even needing a response from the person I'm discussing with. You can still use them as a sanity check on your new solution, too. | |
| Mar 21, 2011 at 15:25 | comment | added | bedwyr | +1 -- My coworkers and I typically sit in each others' cubes when discussing programming issues we're dealing with. Just getting up from my desk is enough to help me start thinking differently. | |
| Mar 21, 2011 at 14:45 | comment | added | Carra | Or just speak to your rubber ducky. | |
| Mar 21, 2011 at 13:34 | comment | added | Sparky | Another reason why it is good to talk to your coworkers in such a situation is that it helps to spread the knowledge around--both of what is to come (and why), and how things are presently done. | |
| Mar 21, 2011 at 12:26 | comment | added | oosterwal | +1 for reminding us that even the highest ranking members of a team can still learn from lower ranked members. | |
| Mar 21, 2011 at 12:05 | history | answered | Jan_V | CC BY-SA 2.5 |