The document serves as a guide for developers looking to contribute more significantly to their organization beyond their current roles. It suggests actionable steps such as identifying technical problems, proposing solutions, addressing technical debt, and teaching teammates. The emphasis is on taking initiative, sharing knowledge, and seeking continuous improvement within projects and processes.

1. A developers guide to contributing to your organization beyond
your current job
@iRomin

2.  You come to work
 You do your job
 But you are itching to do more
 You want to understand how you can go above and
beyond your job and contribute BIG TIME to the
organization
 Bonus : All of that while still doing your job !
 Extra Bonus : Actual things you can do … devoid of
any jargon !

5.  In your current project:
 List top 3 technical problems you are facing
 Propose a solution
 Lead the initiative to implement that solution

6.  Every project has “Technical Debt”
 Put yourself in charge of addressing that

7.  Come up with 3 ideas for your client
 3 ideas that they are not paying for
 3 ideas that they are not expecting
 3 ideas that will DELIGHT them

8.  Make your teammate as good as you are
 Teach him some tips/tricks daily
 Demonstrate him/her a software technique

9.  C’mon … all projects have an issue in one, two or all of
the above areas.
 Work in any of the above 3 areas
 Propose solutions to the above 3 areas

10.  If there is a process in your project that is not working
well, propose how you will fix it.
 Work on the fix.
 Find a tool that could fix it. Demonstrate it to the
team.
 Examples:
 A logging service
 Code Review tools
 Analytics

11.  Read something interesting of late?
 A blog post, viewpoint, news item or even a book
 Share your notes with the team
 Socialize it on the Intranet
 Even Better : Talk about it on various platforms across
the organization : Tech Events, Tech Talk, Hands-on
session and more

12.  Find out what can take you to the next level
 Continuous Integration ?
 Code Reviews?
 Refactoring your code?
 Pursue it !

13.  Go on and make a difference !
 Talk to your Manager !
 Thank You !