@Avanis Engineering productivity cannot always be measured in number of hours
Especially when the task demands some creative problem solving. Sometimes the mind cannot be pushed to instant solutions in an 8 hour time frame. The answers often come at home after an evening or weekend of thinking about the problem.
Engineering productivity cannot always be measured in number of hours....8Hrs of work life per day only brings more discipline into your life. I believe productivity is more a function of non linear aspects like passion and motivation for work rather than hours especially for start ups.
Many of us who are in startups routinely put in 12+ hour work days and it has become the norm. Silicon Valley in general has many engineers who routinely work long hours into the evening.
In many big name companies that have fitness rooms, yoga sessions, cafeterias, etc., long hours at office does not necessarily mean long 'productive' hours! I would argue that one can get the same throughput by focussed and targeted work hours in eight-hour day and do everything else like yoga, fitness, away from office or at home.
@RDC IP I have had consecutive F2F meetings scheduled in buildings separated by 5 miles, one of which I have had the pleasure(?) of waiting at a railroad crossing several times during my tenure at that company! I don't know how people who schedule meetings don't get the fact that if one meeting ends at 3:00PM, another one 5 miles away can not start at 3:00PM if a required attendee has to attend!
Regarding your comment on dev plans, six sigma, etc., I have led many successful implementations of them. Many meetings scheduled were working meetings, often "standing only" type meetings where people realized the wisdom of getting to the point quickly!
@Reverse Engineer: But silly cost cutting and management interference (especially with schedules and resources) is worse than ever.
Back in 2001 I worked for a startup not far from Silicon Valley. Most of engineering was working 50-60 hour weeks when management asked us for a detailed schedule of all remaining work. After we delivered the schedule, they compressed what we had supplied into 80 hour weeks and gave it back to us with the instruction that we were to work 12 hour days, 7 days a week until all work was completed. The result was total rebellion. From that day forward, roughly 95% of the engineers started working strict 40 hour work weeks and the company soon went out of business.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.