4 ms·
Very interesting article, something every manager who manages developers should read. However I think a lot of developers (Particularly startup ones) have mult
by bbody 12y ago
Very interesting article, something every manager who manages developers should read.
However I think a lot of developers (Particularly startup ones) have multiple roles, so interruptions and changing flow is a part of the job. How do you suggest to get around that? My only solution would be to split your day up into chunks for the different roles, minimizing context switching.
- bluedino 12y ago>> However I think a lot of developers (Particularly startup ones) have multiple roles, so interruptions and changing flow is a part of the job. That's how my last job was. Tasks varied as followed: * Work on upcoming project X (release date in the future) * Feature request on project Y (need done somewhat soon for a client on an already operating project) * Bugfix needs done NOW on existing project Z * Ops issue with servers, database, etc