bcg1
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.
House Votes to Require SEC Subpoena for Traders' Source Code
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.
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"
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.
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".
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.
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.
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.
The Latest App Coding Trend Is a Hacker’s Dream
- type annotations + HTML in comments - it is called javadoc
- 80 column limit - lowest common denominator for most people, also historically part of Sun code conventions for Java - http://www.oracle.com/technetwork/java/javase/documentation/...
- 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
https://deskthority.net/wiki/IBM_Model_F#IBM_Personal_Comput...
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.
I have no problem with Ruby or Node BTW, but let's be real.
Perhaps the worst assumption is that we have a capitalist economy/society and thus its ills can safely be attributed to capitalism. In America at least, we have a mixed economy in which the state is deeply influential in most industries through regulation and/or outright participation. Additionally, all income can potentially be taxed and interest rates and money supply are controlled by a quasi-governmental corporation (and since barter is rare, money is in general half of every transaction).
I would suggest that it is possible that many (or a majority?) of the "pointless" jobs exist because the income tax (if people aren't working, they aren't being taxed) and because of government laws and regulations (more laws and regs = more pointless paper pushing = more people being taxed). My theory has as much logical support as the author provides at least.
Also might want to look up the term "contrafreeloading"
I have a fork of NestedVM that I've been using with success but I don't have any simple examples for you:
https://github.com/bgould/nestedvm
Here is an example of compiling the Apache Thrift compiler to run on the JVM:
https://github.com/bgould/thrift/tree/nestedvm/contrib/neste...
And I have a version of the toolchain precompiled as a docker image:
https://hub.docker.com/r/bcg1/nestedvm/ https://github.com/bgould/thrift/blob/nestedvm/contrib/neste...
https://lists.gnu.org/archive/html/guile-devel/2017-03/msg00...
2) There is no perpetual license to worry about, only pay as long as you need your data.
3) Access allowed business people to muddle through creating database that IT hated to have to maintain... this is obviously different.