Recently referred a friend for an opening at the company where I work. He didn't even get an interview because someone from HR has decided that all developers should have a four year degree (he only has an associates degree despite 15+ years experience). Maybe this would be fine for entry level positions, but it is straight up age discrimination for senior level ones (since there are still talented people in the workforce who went to school when CS programs were much less common).
One theory I have is that HR depts are pushing back against the upward trend of developer salaries; if they create an onerous process that tries to make candidates feel inadequate, it might make it more likely that they can land a low ball offer with whoever is desperate enough to stick it out. Also, if the HR department itself is incompetent and not capable of attracting talent, they can always point to their tests etc to "prove" that there are just no qualified candidates in the workforce.
Also, what is with all the coding tests etc? That stuff is obviously useless. Why don't hiring managers just ask candidates to read some code that is similar to what they will be working on, and observe how they approach stepping through it and how quick they can understand it? That is far more similar to what real work looks like most of the time.
Many people correctly surmise that the benefits to individuals are temporary and will sunset, after which their taxes will be higher than when they started.
Also, provisions such as repealing the individual health insurance mandate lead to an increase in other expenses, though admittedly those are not federal taxes. I work for a health insurance company, and earlier this year the company filed with the state regulators to say there might be close to a 50% hike in premiums, depending on whether or not the individual mandate was repealed. Whatever your feelings are about that politically, the increase in premiums will be real and directly related to that bill, and the money is fungible so people can't be blamed if they consider it an increase.
One more thing, a deficit funded tax cut today means a tax increase tomorrow to pay for principal+interest. People could be thinking of that when they say their taxes will go up.
Fair enough, maybe it depends on your definition of "full bust".
But consider this... if the price were to go back to where it was just a year ago before the current mania (which is a common thing to happen when a financial bubble pops, after overcompensating to the downside) then it would be a 95% retracement from the highs (where, almost self-evidently, many people were buyers). And BTW a 95% retracement requires 20,000% gains to break even.
If you gave me a $1000 and I gave you $50 back, I think most people would say that I took all their money, even though technically they could still buy a couple pizzas or something.
So, again, it just depends on your definition of "full bust"
Bitcoin absolutely could go full bust. It is not a physical commodity, there is no utility outside of its perceived value. It is not a company, so it doesn't even have book value as its floor. And the technology is open source and well known, so there is nothing special or scarce about Bitcoin technology at this point. Even the companies that have capital investments in Bitcoin hardware could just repurpose that for a forked coin or possibly some other purpose altogether
> About one-third of internet users stream cable TV without paying for it by using credentials of someone they don't live with
There is no way this is true. Not saying that it isn't a problem, but statements like the above are approaching the same level of BS as when the ad industry says most people would prefer to trade their privacy for the privilege of being manipulated by targeted ads.
> "On the other hand, we still lack a decent high-quality JSON Schema language."
This turns data integration with JSON into a total nightmare. And to make matters worse, Swagger is a total shitshow. Combine the different flavors of JSON schema with OpenAPI/Swagger and you have are left with a regression from SOAP/XML that approaches the same complexity with with fewer features and no standards.
Even mf COBOL has a standard schema definition for data. For new projects I'm still cranking out XSD definitions and doing transformations to JSON if I have to. Even if they come out with a decent schema format I would probably skip it and jump straight to gRPC, Thrift, or some other IDL and just continue to treat JSON as an "also supports".
This should give the big Wall St banks the ability to muck with crypto prices however they choose, just like they can do with gold and silver and other commodities (for example, Goldman magically closed gold positions and sold short 2 days before historic 25% price drop in 2 trading days in 2013[0])
Hopefully people will read those contracts and understand how delivery actually works and realize that COMEX or whoever can halt delivery and settle in cash if they want to, etc.
That's what the insurance industry is for. Just make the companies liable, and they will seek insurance. Insurance companies will force them to take reasonable measures in order to carry a policy. Nothing new under the sun.
It is correct to hesitate to guess ethnicity based on names. Quite sure there are plenty of people of color named Smith and Johnson.
Also, even if these were Caucasian names, the article states that the system disproportionately targets people of color; looking at the 10 most common combinations proves nothing one or another with respect to the assertion in the article.
Critical thought often requires intentional effort, even by those who value it. And many people that I come across do not even seem to value critical thought, especially when it comes to politics... to the contrary, there exists a movement promoting the idea that thinking is a practice that makes you some sort of elitist.
The article you attribute to Adafruit is not written by them, they just linked to it from their blog, ostensibly as food for thought and discussion.
A couple of years ago I had the opportunity to interact with Limor and PT over email after they reached out to me in response to a project I'd posted on a forum. I found them to be gracious, supportive, and genuine, and based on the conversations we had I find your claim that they don't care about open-source hardware to be dubious.
True enough, I just think it is a bit misleading to act as if that is somehow the colloquial Model F Keyboard when really they are recreating a pretty obscure keyboard relative to the XT or AT Model f's.
- single character variable names - who cares, a symbol is a symbol
- variable declarations inside loops - more readable, no chance of referencing stale value outside of scope, and HotSpot will probably recompile anyhow
Article is a little misleading... you don't need "extensive modification" to use a Model F keyboard with a modern computer... the Model F AT keyboard can plug directly into a PS/2 port and be used as-is:
This article seems to be about a business that is actually re-engineering the Model F to be more modern... which is certainly interesting and impressive, but the article is a little misleading.
One really nice feature of these keyboards is that they use capacitance sensing to detect when a key is actuated, instead of a matrix of columns and rows, so there is no ghosting effect when multiple keys are pressed. If you disassemble the keyboard you can actually type right on the PCB with your fingers like a touchpad.
His father inherited his money from his own father, who moved to the Klondike in order to dodge the German draft and became wealthy by running brothels catering to gold prospectors.
One theory I have is that HR depts are pushing back against the upward trend of developer salaries; if they create an onerous process that tries to make candidates feel inadequate, it might make it more likely that they can land a low ball offer with whoever is desperate enough to stick it out. Also, if the HR department itself is incompetent and not capable of attracting talent, they can always point to their tests etc to "prove" that there are just no qualified candidates in the workforce.
Also, what is with all the coding tests etc? That stuff is obviously useless. Why don't hiring managers just ask candidates to read some code that is similar to what they will be working on, and observe how they approach stepping through it and how quick they can understand it? That is far more similar to what real work looks like most of the time.