Hard Work Does not Pay off - Revision history

Kevlin: Hard work does not pay off moved to Hard Work Does not Pay off

2009-08-06T13:51:20Z

Hard work does not pay off moved to Hard Work Does not Pay off

←Older revision

Revision as of 13:51, 6 August 2009

Olvemaudal at 13:20, 6 August 2009

2009-08-06T13:20:59Z

←Older revision		Revision as of 13:20, 6 August 2009
Line 5:		Line 5:
	Professional programming is usually not like running hard for a few kilometers, where the goal can be seen at the end of a paved road. Most software projects are more like a long orienteering marathon. In the dark. With only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.		Professional programming is usually not like running hard for a few kilometers, where the goal can be seen at the end of a paved road. Most software projects are more like a long orienteering marathon. In the dark. With only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.

-	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays educating yourself, therefore you cannot spend ~~all~~ your evenings, weekends, and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.	+	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays educating yourself, therefore you cannot spend your evenings, weekends, and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.

	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing, and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect, and change.		Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing, and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect, and change.

Kevlin at 10:01, 5 August 2009

2009-08-05T10:01:32Z

←Older revision		Revision as of 10:01, 5 August 2009
Line 3:		Line 3:
	The statement above may seem counterintuitive and even controversial, but it is a direct consequence of the fact that programming and software development as a whole involve a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid wasted work, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.		The statement above may seem counterintuitive and even controversial, but it is a direct consequence of the fact that programming and software development as a whole involve a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid wasted work, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.

-	Professional programming is usually not like running hard for a few kilometers, where the goal can be seen at the end of a paved road. Most software projects are more like a long orienteering marathon in the dark~~, with~~ only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.	+	Professional programming is usually not like running hard for a few kilometers, where the goal can be seen at the end of a paved road. Most software projects are more like a long orienteering marathon. In the dark. With only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.

	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays educating yourself, therefore you cannot spend all your evenings, weekends, and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.		In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays educating yourself, therefore you cannot spend all your evenings, weekends, and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.

Kevlin at 13:46, 11 July 2009

2009-07-11T13:46:50Z

←Older revision		Revision as of 13:46, 11 July 2009
Line 1:		Line 1:
-	As a programmer, working hard often does not pay off. You might fool yourself and a few colleagues into believing that you ~~contribute~~ a lot to a project by spending long hours at the office. But the truth is that by working less you might achieve more — sometimes much more. If you are trying to be focused and "productive" for more than 30 hours a week you are probably working too hard. You should consider reducing the workload to become more effective and get more done.	+	As a programmer, working hard often does not pay off. You might fool yourself and a few colleagues into believing that you are contributing a lot to a project by spending long hours at the office. But the truth is that by working less you might achieve more — sometimes much more. If you are trying to be focused and "productive" for more than 30 hours a week you are probably working too hard. You should consider reducing the workload to become more effective and get more done.

-	The statement above may seem counterintuitive and controversial ~~to some~~, but it is a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid ~~wasting energy~~, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.	+	The statement above may seem counterintuitive and even controversial, but it is a direct consequence of the fact that programming and software development as a whole involve a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid wasted work, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.

	Professional programming is usually not like running hard for a few kilometers, where the goal can be seen at the end of a paved road. Most software projects are more like a long orienteering marathon in the dark, with only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.		Professional programming is usually not like running hard for a few kilometers, where the goal can be seen at the end of a paved road. Most software projects are more like a long orienteering marathon in the dark, with only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.

-	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays ~~for~~ educating yourself, therefore you cannot spend all your ~~evening~~, weekends and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.	+	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays educating yourself, therefore you cannot spend all your evenings, weekends, and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.

	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing, and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect, and change.		Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing, and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect, and change.

Kevlin at 22:26, 4 February 2009

2009-02-04T22:26:37Z

←Older revision		Revision as of 22:26, 4 February 2009
Line 3:		Line 3:
	The statement above may seem counterintuitive and controversial to some, but it is a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.		The statement above may seem counterintuitive and controversial to some, but it is a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.

-	Professional programming is usually not like running hard a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are more like a long orienteering marathon in the dark, with only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.	+	Professional programming is usually not like running hard for a few kilometers, where the goal can be seen at the end of a paved road. Most software projects are more like a long orienteering marathon in the dark, with only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.

	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays for educating yourself, therefore you cannot spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.		In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays for educating yourself, therefore you cannot spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.

Olvemaudal at 20:26, 4 February 2009

2009-02-04T20:26:13Z

←Older revision		Revision as of 20:26, 4 February 2009
Line 3:		Line 3:
	The statement above may seem counterintuitive and controversial to some, but it is a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.		The statement above may seem counterintuitive and controversial to some, but it is a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.

-	Professional programming is usually not like ~~sprinting~~ a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are more like a long orienteering marathon in the dark, with only a sketchy map as guidance. If you just set off in one direction, running as ~~hard~~ as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.	+	Professional programming is usually not like running hard a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are more like a long orienteering marathon in the dark, with only a sketchy map as guidance. If you just set off in one direction, running as fast as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.

-	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend ~~your~~ evenings, weekends, and holidays for educating yourself, therefore you cannot spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.	+	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend evenings, weekends, and holidays for educating yourself, therefore you cannot spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.

	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing, and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect, and change.		Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing, and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect, and change.

Kevlin at 15:10, 4 February 2009

2009-02-04T15:10:27Z

←Older revision		Revision as of 15:10, 4 February 2009
Line 1:		Line 1:
-	As a programmer, working hard often does not pay off. You might fool yourself and a few colleagues into believing that you contribute a lot to a project by spending long hours at the office. But the truth is that by working less you might achieve more~~...~~ sometimes much more. If you are trying to be focused and "productive" more than 30 hours a week you are probably working too hard. You should consider reducing the workload to become more effective and get more done.	+	As a programmer, working hard often does not pay off. You might fool yourself and a few colleagues into believing that you contribute a lot to a project by spending long hours at the office. But the truth is that by working less you might achieve more — sometimes much more. If you are trying to be focused and "productive" for more than 30 hours a week you are probably working too hard. You should consider reducing the workload to become more effective and get more done.

-	The statement above ~~is counter-intuitive~~ and controversial to some, but it is ~~just~~ a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and hopefully find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.	+	The statement above may seem counterintuitive and controversial to some, but it is a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and, hopefully, find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.

-	Professional programming is usually not like sprinting a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are like a long orienteering marathon in ~~darkness~~ with a ~~very~~ sketchy map. If you just set off in one direction, running as hard as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you ~~must~~ adjust the course when you learn more about where you are and where you are heading.	+	Professional programming is usually not like sprinting a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are more like a long orienteering marathon in the dark, with only a sketchy map as guidance. If you just set off in one direction, running as hard as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you need to adjust the course when you learn more about where you are and where you are heading.

-	In addition, you always need to learn more about software ~~developement~~ in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques and learn about powerful tools that ~~simplifies~~ your job. As a professional programmer you must keep yourself updated in your field of expertise - just ~~like~~ brain surgeons and pilots are expected to keep themselves ~~updated~~ in their ~~field~~ of expertise. You need to spend your evenings, weekends and holidays for educating yourself, therefore you ~~can not~~ spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons ~~performing~~ surgery 60 hours a week, or pilots ~~flying~~ 60 hours a week? Of course not, preparation and education is an essential part of their profession.	+	In addition, you always need to learn more about software development in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques, and learn about powerful tools that simplify your job. As a professional programmer you must keep yourself updated in your field of expertise — just as brain surgeons and pilots are expected to keep themselves up to date in their own fields of expertise. You need to spend your evenings, weekends, and holidays for educating yourself, therefore you cannot spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons to perform surgery 60 hours a week, or pilots to fly 60 hours a week? Of course not, preparation and education is an essential part of their profession.

-	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect and change.	+	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing, and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect, and change.
		+
		+	By [[Olve Maudal]]
		+
		+
		+	This work is licensed under a
		+	[http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]
		+
		+	Back to [[97 Things Every Programmer Should Know]] home page

Olvemaudal at 00:17, 9 January 2009

2009-01-09T00:17:54Z

←Older revision		Revision as of 00:17, 9 January 2009
Line 1:		Line 1:
-	As a programmer, working hard often does not pay off. You might fool yourself and a few colleagues into believing that you contribute a lot to a project by spending long hours at the office. But the truth is that by working less you might achieve more... sometimes much more. If you are trying to be focused and productive more than~~, say,~~ 30 hours a week you are probably working too hard. You should consider reducing the workload to become more effective and get more done.	+	As a programmer, working hard often does not pay off. You might fool yourself and a few colleagues into believing that you contribute a lot to a project by spending long hours at the office. But the truth is that by working less you might achieve more... sometimes much more. If you are trying to be focused and "productive" more than 30 hours a week you are probably working too hard. You should consider reducing the workload to become more effective and get more done.

	The statement above is counter-intuitive and controversial to some, but it is just a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and hopefully find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.		The statement above is counter-intuitive and controversial to some, but it is just a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and hopefully find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.

-	Professional programming is usually not like sprinting a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are like a long orienteering marathon with a very sketchy map. If you just set off in one direction, running as hard as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you must adjust the course when you learn more about where you are and where you are heading.	+	Professional programming is usually not like sprinting a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are like a long orienteering marathon in darkness with a very sketchy map. If you just set off in one direction, running as hard as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you must adjust the course when you learn more about where you are and where you are heading.

	In addition, you always need to learn more about software developement in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques and learn about powerful tools that simplifies your job. As a professional programmer you must keep yourself updated in your field of expertise - just like brain surgeons and pilots are expected to keep themselves updated in their field of expertise. You need to spend your evenings, weekends and holidays for educating yourself, therefore you can not spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons performing surgery 60 hours a week, or pilots flying 60 hours a week? Of course not, preparation and education is an essential part of their profession.		In addition, you always need to learn more about software developement in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques and learn about powerful tools that simplifies your job. As a professional programmer you must keep yourself updated in your field of expertise - just like brain surgeons and pilots are expected to keep themselves updated in their field of expertise. You need to spend your evenings, weekends and holidays for educating yourself, therefore you can not spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons performing surgery 60 hours a week, or pilots flying 60 hours a week? Of course not, preparation and education is an essential part of their profession.

-	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be ~~productive~~ and ~~just splash out code~~ 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect and change.	+	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be focused and "productive" 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect and change.

Olvemaudal at 00:10, 9 January 2009

2009-01-09T00:10:41Z

←Older revision		Revision as of 00:10, 9 January 2009
Line 7:		Line 7:
	In addition, you always need to learn more about software developement in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques and learn about powerful tools that simplifies your job. As a professional programmer you must keep yourself updated in your field of expertise - just like brain surgeons and pilots are expected to keep themselves updated in their field of expertise. You need to spend your evenings, weekends and holidays for educating yourself, therefore you can not spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons performing surgery 60 hours a week, or pilots flying 60 hours a week? Of course not, preparation and education is an essential part of their profession.		In addition, you always need to learn more about software developement in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques and learn about powerful tools that simplifies your job. As a professional programmer you must keep yourself updated in your field of expertise - just like brain surgeons and pilots are expected to keep themselves updated in their field of expertise. You need to spend your evenings, weekends and holidays for educating yourself, therefore you can not spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons performing surgery 60 hours a week, or pilots flying 60 hours a week? Of course not, preparation and education is an essential part of their profession.

-	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be productive and just splash out code 60 hours a week is not a sensible thing to do. Act like a professional: prepare, observe, reflect and change.	+	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be productive and just splash out code 60 hours a week is not a sensible thing to do. Act like a professional: prepare, effect, observe, reflect and change.

Olvemaudal at 21:47, 8 January 2009

2009-01-08T21:47:28Z

←Older revision		Revision as of 21:47, 8 January 2009
Line 1:		Line 1:
-	As a programmer, working hard often does not pay off. You might fool yourself and a few colleagues into believing that you contribute a lot to a project by spending long hours at the office. But the truth is that by working less you might ~~achive~~ more... sometimes much more. If you are trying to be productive more than, say, 30 hours a week you are probably working too hard. You should consider reducing the workload to become more effective.	+	As a programmer, working hard often does not pay off. You might fool yourself and a few colleagues into believing that you contribute a lot to a project by spending long hours at the office. But the truth is that by working less you might achieve more... sometimes much more. If you are trying to be focused and productive more than, say, 30 hours a week you are probably working too hard. You should consider reducing the workload to become more effective and get more done.

-	The statement above is counter-intuitive and controversial to some, but it is just a direct consequence of the fact that programming and software ~~developement~~ is a continuous learning process. As you work on a project you will understand more of the problem domain and hopefully find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your ~~behaviour~~ accordingly.	+	The statement above is counter-intuitive and controversial to some, but it is just a direct consequence of the fact that programming and software development is a continuous learning process. As you work on a project you will understand more of the problem domain and hopefully find more effective ways of reaching the goal. To avoid wasting energy, you must allow time to observe the effects of what you are doing, reflect over the things that you see, and change your behavior accordingly.

-	Professional programming is usually not like sprinting a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are like ~~running~~ a long orienteering marathon with a very sketchy map. If you just set off in one direction, running as hard as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you must adjust the course when you learn more about where you are and where you are heading.	+	Professional programming is usually not like sprinting a few kilometers, where the goal can be seen in the end of a paved road. Most software projects are like a long orienteering marathon with a very sketchy map. If you just set off in one direction, running as hard as you can, you might impress some, but you are not likely to succeed. You need to keep a sustainable pace and you must adjust the course when you learn more about where you are and where you are heading.

-	In addition, you always need to learn more about software developement in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques and learn about powerful tools that simplifies your job. As a professional programmer you must keep yourself updated in your field of expertise - just like brain ~~surgents~~ are expected to keep themselves updated in their field of expertise. ~~If you can't~~ spend your evenings, weekends and holidays for ~~that~~, ~~then~~ you ~~must do it during day time - at work~~. Do you really expect brain ~~surgents~~ performing surgery 60 hours a week, or pilots flying 60 hours a week? Of course not, ~~preparartion~~ and education is an essential part of their ~~job~~.	+	In addition, you always need to learn more about software developement in general and programming techniques in particular. You probably need to read books, go to conferences, communicate with other professionals, experiment with new implementation techniques and learn about powerful tools that simplifies your job. As a professional programmer you must keep yourself updated in your field of expertise - just like brain surgeons and pilots are expected to keep themselves updated in their field of expertise. You need to spend your evenings, weekends and holidays for educating yourself, therefore you can not spend all your evening, weekends and holidays working overtime on your current project. Do you really expect brain surgeons performing surgery 60 hours a week, or pilots flying 60 hours a week? Of course not, preparation and education is an essential part of their profession.

-	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing and adapt your ~~behaviour~~. Avoid ~~embarassing~~ yourself, and our profession, by behaving like a hamster in a cage ~~running~~ the wheel. As a professional programmer you should know that trying to be productive and just splash out code 60 hours a week is not a sensible thing to do. Act like a professional: prepare, observe, reflect and change.	+	Be focused on the project, contribute as much as you can by finding smart solutions, improve your skills, reflect on what you are doing and adapt your behavior. Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel. As a professional programmer you should know that trying to be productive and just splash out code 60 hours a week is not a sensible thing to do. Act like a professional: prepare, observe, reflect and change.