Moreover, for creative professions, including programming and engineering, the number of "worked" hours is emphasized only by incompetent managers who do not really know how to measure the productivity of the employees.

When competent programmers or engineers have a difficult problem to solve, they will think about it all the time, regardless whether they are "working" long hours in the office or they are doing any other activities, at home or on the street.

It is quite frequent to have the best ideas when you are not in the office "working". For things like programming or designing, the time required to type on a keyboard the solution is never a bottleneck.

At least for myself, the majority of the technical solutions to the problems on which I have worked have come to my mind at home, in the morning, immediately when waking up, and the "work" done in the office has always been mostly in typing whatever solution I already had in mind when arriving at the office.

Anyone who believes that a programmer or engineer who "works" e.g. a 50-hour week is more productive than one who "works" a 40-hour week is naive, to not use a more insulting word.

This is true regardless how competitive the company is believed to be. How many hours one stays in the office in the front of a computer, while being watched by a manager who believes that this is how you "work", has an extremely poor correlation with the amount of useful work that is actually completed.