As a Developer

Keeping your eye on the screen while coding in a High contrast settings in you screen and applications is bad for your eyes in the long term - so you can't code More ;) .

So try some of these Visual Studio Programmer Themes which will help,some are low contrast , and others are colorful ..

 "It's unbelievable to me that a company would pay a developer $60-$100k in salary, yet cripple him or her with terrible working conditions and crusty hand-me-down hardware. This makes no business sense whatsoever. And yet I see it all the time. It's shocking how many companies still don't provide software developers with the essential things they need to succeed."..read it here

When Speaking about the developer's REAL working hours we will come to know that any of the developers work which involves engineering will be in a single-minded work time in other words for that particular work ( design, architect, modeling or coding ) he would sit down and be committed focusing on working and completing that part and that part only..for that he have to be in a state of deep mindfulness where he becomes unaware of the passage of time.." Oh ! Three hours passed already ,..Man  we just started !". That state is called Flow. and that's  when you really do work!

Unfortunately you can't turn ON flow like a Switch.It takes about fifteen to twenty-minutes of concentration and uninterruption before that state is locked in.  during this period a person is so sensitive to noise, so non-quite environments makes it impossible to reach the flow state. Interruptions that is focused on the person him self like a phone call or his Boss shows off for a chat or a colleague asking a question will take him back to the awareness of his surroundings and take him additional fifteen minutes to return to flow..and during these fifteen minutes you are not doing work..!

Some people do a "Personal Productivity Matrix" which measures the number of interruptions per hour IPH. So you can tell for example if you got a rate of 0.25 IPH that would mean that you can have a maximum number of One Interruption in four hours to stay Productive.! So if the average of  these interruptions is ten minutes PLUS your fifteen minutes . getting into flow will cost you twenty-five minutes of flow time (work time!) So..a couple of these a day might take the half of it !

And Believe me a few days like that and somebody will start thinking."I really accomplish work After office hours !", Doesn't Office work have to be done IN Office hours!! when such things happen Managers have to know that there is something wrong in there office environment that needs to be fixed ASAP.

This is my first blog post in the OryxDev.NET Community and I thought to start with something that will push people -coders\developers- to a fact that is "There aren't a guy that knows everything and the learning curve for IT people is a bit Longer!" so..work HARD!

this is a part of a Foreword in the book titled "Coder To Developer" by Mike Gunderloy :

"...What drives me crazy is that most software developers don't realize just how little they know about software development.

Take, for example, me.

    When I was teenager, as soon as I finished reading Peter Norton's famous guide to programming the IBM-PC in Assembler,I was convinced that I knew everything there was to know about software development in general. Heck, I was ready to start a software company to make a work processor, you see, and it was going to be really good. My imaginary software company was going to have coffee breaks with free donuts every hour. A lot of my daydreams in those days involved donuts.

    When I got out of the army, I headed off to collage and got a degree in Computer Science.Now I really knew everything, I knew more than everything, because I had learned a bunch of computer-scientific junk about linear algebra and NP completeness and frigging lambda calculus which was obviously useless, so I thought they must have ran out of useful things to teach us and were scraping the bottom of the barrel.

    Nope. At my first job I noticed how many things there are that many Computer Science departments are too snooty to actually teach you. Things like software teamwork. Practical advice about user interface design. Professional tools like source code control, bug tracking database, debuggers, and profilers. Business things. Computer Science departments in the most prestigious institutions just won't teach you this stuff because they consider it "vocational," not academic ... I can sort of understand that attitude. After all, many prestigious undergraduate institutions see their goal as preparing you for life, not teaching you a career, least of all a career in a field that changes so rapidly that any technologies you learn now will be obsolete in a decade.

... You're probably going to have to learn how to do software development on your own. If you're really lucky, you've had some experience working directly with top notch software developers who can teach you this stuff, but most people don't have that opportunity ... Being a software developer means you can take a concept, build a team, set up state of the art development processes, design a software product, the right software product, and produce it. Not just any software product: a high-quality software product that solves a problem and delights your users. With documentation. A web Page. A setup program. Test cases.Norwegian version.Bokmal and Nynorsk ... And then, one day, finally, perhaps when it's too late, you'll wake up and say, "Hmm. Maybe I really don't know what it really takes to develop software." And on that day only, and not one minute before, but on that day and from that day forward, you will have earned the right to call yourself a software developer..." 

- Joel Spolsky Founder, Fog Creek Software