I admire your enthusiasm, try not to lose that quality and you could get far in life.
Here are a few advice I have, take them for what they're worth: - Choose your battles wisely. The bigger the company, the more chances there is to have someone with more power than you that will be intimidated by your results. The actions they take can be surprising. - Be certain to always take care of your primary responsibilities first before taking others. - Only get involved in other responsibilities if you can have a reasonable impact without burning yourself out. - When getting involved in other projects, like in your example, make sure your help is welcomed. And when it isn't, try to free yourself mentally of the success or failure of the project. - In situations such as the example you wrote, try not to take the credit for the solution yourself, try to make it look like the solution came from them and give them the opportunity to give you credit if they wish. It will have a better value and a bigger impact coming from your colleagues.
I often hear programmers saying Math is not important, and from my observations, it is often the programmers that are weak in Math.
Sure there are probably good programmers that aren't advance in Math, but when big critical, hard to solve problems occurs (field issues, bugs, etc), it is often those who are strong in Math that need to step up.
This does not even mention the fact that enhanced Math skills helps approach problems in different ways that sometimes leads to better success.
If you spent time explaining the history and mathematics behind certain concepts, something as simple as...
- Wooden Tower of Hanoi
- Rubik's Cube
- Pegopolis
- Sudoku, Kakuro,... puzzle books
Slashdot Mirror
I admire your enthusiasm, try not to lose that quality and you could get far in life.
Here are a few advice I have, take them for what they're worth:
- Choose your battles wisely. The bigger the company, the more chances there is to have someone with more power than you that will be intimidated by your results. The actions they take can be surprising.
- Be certain to always take care of your primary responsibilities first before taking others.
- Only get involved in other responsibilities if you can have a reasonable impact without burning yourself out.
- When getting involved in other projects, like in your example, make sure your help is welcomed. And when it isn't, try to free yourself mentally of the success or failure of the project.
- In situations such as the example you wrote, try not to take the credit for the solution yourself, try to make it look like the solution came from them and give them the opportunity to give you credit if they wish. It will have a better value and a bigger impact coming from your colleagues.
Duct tape, cheap webcam and cheap digital picture frame with video input.
I often hear programmers saying Math is not important, and from my observations, it is often the programmers that are weak in Math. Sure there are probably good programmers that aren't advance in Math, but when big critical, hard to solve problems occurs (field issues, bugs, etc), it is often those who are strong in Math that need to step up. This does not even mention the fact that enhanced Math skills helps approach problems in different ways that sometimes leads to better success.
If you spent time explaining the history and mathematics behind certain concepts, something as simple as... - Wooden Tower of Hanoi - Rubik's Cube - Pegopolis - Sudoku, Kakuro, ... puzzle books