938 karma · joined August 6, 2011
Just because you can't always have an accurate estimate doesn't mean it's now worth it.
Also remember that estimates are based on resources. We were able to go to the moon in a decade but a lot of work was done before and the budget to get there was much higher than what most software development efforts ever get relatively speaking. It might not be going to the moon but that doesn't mean some projects aren't very complex either.
Fr example can u imagine telling a plumber no the bathroom is now going to be 30 feet to the left. The plumber says ok but that will cost u a week of work. How many people would say no, u have 1 day to do it and u will be held accountable for my estimate and not ur estimate because I don't trust u when u say a week. Now assume the walls are closed and it's only after u open them u learn there are other issues. Doesn't matter, one day. This is what most de s deal with. I assume ur not like this but this is how most devs have to work. It's frustrating. If u would be given the week then u would be fine, but instead ur told the timeline and/or cost. U may even be told no u can't use those tools they r too expensive, but u need to complete the task in the faster then even people who can use the tools.
My whole point is it's often not the change requests that are the issue, it's what it entails, in that the schedule and costs are not adjusted fairly.
There's concurrency issues, as in what happens if two technicians are accessing the same ticket. There's the backend system which will also include user details etc. there's the whole account management portion. And so on.
A prototype is great but there's still a good a lot of work left to productize something ;)
Basically all I'm saying is that it's not an easy problem and there are no easy and obvious answers :(
Ignoring that who will enforce it? If say a Russian owes taxes to the US how will they get the payment if the person doesn't want to pay?
But even then why should the taxes go to that country? All the infrastructure to allow your business to operate in the first place is in your country. The roads to get your employees to work etc.
That being said if your going to open factories or offices in another country than I believe you should be required to have a corporation in that country and pay taxes in that country for the revenues those entities make. But even that is challenging. It's honestly a very hard issue to resolve...
Another thing to realize, most credit cards have some kind of reward program that amounts to about a 1% payout. That's coming out of the transaction fees, which if you do the math is actually being paid for by the merchant. If the fees were 2% there would no longer be rewards programs. I find that interesting. The retail world is being taxed to pay the credit xard reward programs of their customers. Makes you think a bit doesn't it ;)
For those wondering how, if you do control backspace to erase a word etc igs very easy to miss, especially as you transition between word delete and single character delete.
The other common use case for errors is when u think you're in a field editing and you're actually not, bam, you just lost all your form data.
I also like the idea that backspace is for text editing and not for a second feature such as navigation. For enter yes but not backspace
Also not every source generates valid data files :(
And for those of you who say you would pay, how many subscriptions are you currently paying for? How many paywalls have you tried to bypass? Paying for content just doesn't work because people are too use to free :(
The other major benefit is that if something is successful and people want it such as a book you have a monetary incentive to publish it to pay the copyright fees. When it's not popular enough to make money with the copyright alone than that's a good signal that it's been copyrighted long enough