695 karma · joined February 9, 2012
>I would much rather be able to buy one package of toilet paper for 50 dollars versus being able to buy zero for 5 dollars.
Yeah, because you have 50 dollars to spend on that. What's a person supposed to do who is only barely making ends meet? Do they forsake eating so they can wipe themselves? Underpay their rent? Go into debt so they can wipe their ass?
My point here is that this isn't an either/or situation. There's other alternatives, though some people won't like it.
Rationing - at least by stores if not by the government - is one that we don't like these days, but that has worked for us in historical times of trouble.
This law is meant to be another alternative. It's certainly not perfect - I'd have taken rationing initiated by stores over that - but it is an alternative to the "pay 50 for a roll or not have a roll at all" options.
Indeed, at that point I think rationing - either by the companies selling the product, or by the government (as we have done in times of crisis in the past) is in order. Would people be yelling about free markets like this if World War 2 happened today, and there was the kind of rationing we saw in those times? What would have happened to our country if people were so selfish back then?
I hope it doesn't reach that.
It sounds like this is built under an assumption that there is extra capacity available without significant or permanent costs. I don't know the level of capacity at which they are currently producing, but rationally speaking the mere fact that the shelves are empty due to demand would mean that intelligent companies would already have ramped up that capacity in response. So if the shelves remain empty, is that a sign that we've reached the level of demand where the cost of additional supply becomes more expensive/ongoing?
Are you sure? https://www.nytimes.com/2020/03/14/technology/coronavirus-pu...
"Mr. Colvin said he had posted 300 bottles of hand sanitizer and immediately sold them all for between $8 and $70 each, multiples higher than what he had bought them for. To him, “it was crazy money.” To many others, it was profiteering from a pandemic."
> This completely ignores the fact that the cost to produce a product is not a fixed amount, but rather that higher prices induce producers to make more product sooner.
How will they make more product sooner? By expanding their businesses - making new factories, procuring new manufacturing machinery, hiring new workers? What happens when demand reduces, and they're back to not only having a normal amount of demand, but having that further reduced by the glut of supply - supply of a nonperishable good in particular?
We have certainly fallen back on rationing during times of emergency in our society - even here in America. If it comes to that, I know many people will find it distasteful, but your point of:
> The higher price means that those who demonstrate a higher desire for an item (by their willingness to pay) end up getting it.
Is unfortunately the truth (though it's interesting that you chose to phrase "ability to pay" as "willingness to pay" - that discounts the fact that many people have a high desire for these items, but could be forced to choose between them and other items needed for basic survival), and left unchecked it will result in a pretty quick reversal of the "rising tide lifts all boats" argument for Capitalism if this situation continues long enough. It'll be pretty hard to argue that the free markets help all Americans when only people who can afford to do so can wipe their ass, or have access to basic health necessities.
So what you're saying is, they wouldn't have scaled production, so your entire proposition about why the price increase would be an effective means to alleviate the problem was false.
This situation is just as bad for the manufacturer as it is for the consumer.
There's two kinds of hoarding happening here: fear-alleviating and profit-seeking, which allows the profit seeking form of acquisition to be possible. Several weeks ago, it wouldn't have been feasible for someone to scoop up the entire market. Profit-seeking acquisition is however both a self fulfilling prophecy for the fake headlines about insufficient production, and a means by which the people seeking these products to alleviate fear have their fears justified.
So is your solution "good on them, they're taking advantage of people's fears to help make the rumors true?" Just what price do you think toilet paper should be right now in stores?
This is not a case of toilet paper suddenly costing more to produce. The price gouging law is not bringing toilet paper to levels where the producer of the product is taking some kind of operating loss or even reduction in profit of any kind. This is a case of consumers attempting to create small niches of artificial scarcity so that they can profit.
The free market arguments being made here are baffling, and willfully ignoring the aforementioned truths of this specific set of circumstances that have driven these specific laws. Have we lost all sense of humanity for the sake of our ideology?
We would be doing our entire society a severe disservice if our solution to this problem is simply "create so much toilet paper that people can't hoard it." The fuck are we going to do with that much toilet paper.
Granted, the context didn't really change what the fix needed to be, but it did provide a useful moment of reflection on the ways in which software can break through subtle changes over time that stack up, and it helped to know that the section of code that broke was indeed originally intended to work the way it did (and not that it was a bug from the very beginning).
If salary was determined based on the emotional and physical toll a job takes, I feel like a fast food worker would make more than I do as a software engineer.
I promise you, if they don't want to provide version control they aren't going to provide you with other benefits and necessities that you deserve.
Related questions to benefits and necessities:
* Are you getting healthcare? * How is your pay compared to other Jr. software engineers in your area? * Are they paying you hourly? If so, are they actually paying you for hours worked, or are they finding ways to reduce that number of hours? * What if you demanded that they used version control, and brought your best arguments: what would they say?
Consider the answers to those questions, and if you don't like the answers, I strongly urge you to leave. There's a complacency that can come with "settling" for a place that is a "known constant." Don't settle here, when you deserve more.
Put what you've done on a resume, and give it to a headhunter. They will find you a better job - maybe not an ideal job, but a step up. And your career will truly begin.
"Hey, we need someone of your skill level to come in and fly some test planes"
"...okay"
I should also note that I would trust numbers that indie developers are putting out. If things were working the way G2A claims, indie developers would be getting paid in the initial transaction and they wouldn't have a problem with key resellers to begin with. No incentive for them to lie in this situation.
(not that anyone is implying that they shouldn't trust indie devs: but in case anyone is wondering where a more credible source for information is, I feel like that's a good place to look given the lack of incentive for them to be lying about this)
Suddenly, keys were "generated" for money that no longer exists. The key hopefully gets deactivated at this point, but then someone buys one of those keys and it doesn't work. Support calls and angry customers ensue.
That combined with the easy to use WYSIWYG editor and the edit and continue functionality were, to me, what made it such an amazingly useful language for creating quick utilities or small programs. It was truly a "Rapid Application Development" language.
I also saw some nightmares in my days, though I don't blame VB as much as the people who created the app. The most notable one was a document management system that I'd been asked to port from VB3 to VB6 (so that it could run on win32 among other reasons) and to turn the system from a batch system for document processing facilities into a desktop DMS for home use. I will never forget when I opened up the project and there were 60 some-odd "forms" in it, and when I opened any one of them up not a single one defined a variable. They all - every last one - was defined as a global variable in a single globals.bas file. There were thousands of global variables. Every single one in the entire application declared there, and edited at will in any of the myriad forms wherever they fancied. My first task became "untangle the global variable mess."
I think named parameters don't actually help, because the underlying problem with the boolean (aside from the mystery about what it means when looking at code calling it) is that it implies a potential separate "mode" of operation for the function. That the single function might actually serve two different purposes. It doesn't always imply that I imagine, but it's pretty likely.
I'm guilty of this in my code, and I know that my code quality has suffered for it - for some reason, the way he put it in this article gave me a moment of introspection there, and it's something I'm going to try and take away from it and improve my own code with in the future.
Until then, if it's solving a business need and you're not pouring tons of effort/money into it, it's more about pride than a real problem. That is a lesson I had to learn the hard way, and still struggle with: accepting that sometimes a janky, hobbled-together solution that solves a business problem still solves that problem and might not be worth the cost of "fixing."