alt Hacker NewsThe 2nd most annoying thing about section 174 was all the time you had to spend classifying each engineer's time spent as R&D or 'internal software'. At my last company, every year, me and my engineering lead counterparts would spent almost a day reviewing each engineer's JIRA tickets to reconstruct how much of their time was spent on R&D vs internal software.
Replies
>was all the time you had to spend classifying each engineer's time spent as R&D or 'internal software'
> every year, me and my engineering lead counterparts would spend almost a day
This is quite funny. Not even a day, almost one.
Why would you waste time doing this when you could just make shit up?
And just to clarify, that has been the MO any time I've been told to do this. If it's actually important they wouldn't want your numbers
At a previous employer, they used to have this process where they would classify each project as being in active development or being in maintenance, and even the tiniest bit of development work required the "initiation" of a "project" with budget planning and approvals.
At the time I dismissed it as a bureaucratic process invented by the company; after all, they had no dearth of leaders adding bureaucracy to systems for the purpose of empire-building and, to a lesser extent, asserting self-importance. However, upon reading about Section 174, it made some sense, and I wonder whether they might just get around to removing these processes.