Re:Software firms across US facing tax bills that threaten s...
by rcme on Tuesday April 18, 2023 @04:23PM
(#35619513)
How is fixing a bug in the interest of a new product?
[ Parent
| on HN ]
Re:Software firms across US facing tax bills that threaten s...
by oldmanhorton on Tuesday April 18, 2023 @04:39PM
(#35619733)
It's a bit strained, but car or TV companies often put out a new model that's identical to the old model +- some but fixes. There's a line somewhere but the law does not specify the line, it seems
Re:Software firms across US facing tax bills that threaten s...
by crazygringo on Tuesday April 18, 2023 @05:30PM
(#35620526)
Exactly. v4.2.34 is a new product compared to v4.2.33.
Not defending this, but in the eyes of the law there's no distinction between products and features and bug fixes.
Re:Software firms across US facing tax bills that threaten s...
by whitemary on Wednesday April 19, 2023 @01:18AM
(#35624522)
Precisely. The difference with software is that the production process is so iterative that experimentation becomes a relatively rational tactic for getting things done.
Re:Software firms across US facing tax bills that threaten s...
by ajmurmann on Tuesday April 18, 2023 @06:07PM
(#35621035)
Leaving arguments about new patch releases out, how could we practically track this? Would every engineer log the time they work and track feature work separately from bug fixes?
Re:Software firms across US facing tax bills that threaten s...
by paulddraper on Tuesday April 18, 2023 @06:58PM
(#35621651)
There are already tax credits available to "new development" that doesn't include fixes.
So this isn't a new thing to track
Re:Software firms across US facing tax bills that threaten s...
by rodgerd on Tuesday April 18, 2023 @07:24PM
(#35621919)
I see that you are blessed to work in an environment where your day is not a stream of Jira tickets linked to timesheets.