HN user
(project author here) That is pretty close to the approach this project has taken, although my motivation was not so much avoiding IP as exploring the line between hardware acceleration and software.
This reminds me of the old Yogi Berra quip "Nobody goes there anymore, it's too crowded."
I read the book "Why Nations Fail." I found it to be poorly organized and repetitive. But the biggest problem I had with it was that it suffered from the fallacy of the single cause. The authors tried to attack every other theory about the prosperity of nations in favor of their one thesis. Their arguments against other theories seemed weak and poorly supported. While I think there is truth to their hypothesis that economic prosperity is related to inclusiveness of a society, and they presented some sound arguments for it, trying to say it is the only cause is a bridge too far in my opinion.
They abandoned the atom concept for ELF & PE/COFF for the reason you described.
https://llvm.cc/t/llvmdev-lld-improvement-plan/274
"The atom model is not the best model for some architectures The atom model makes sense only for Mach-O, but it’s used everywhere. I guess that we originally expected that we would be able to model the linker’s behavior beautifully using the atom model because the atom model seemed like a superset of the section model. Although it can, it turned out that it’s not necessarily natural and efficient model for ELF or PE/COFF on which section-based linking is expected."
Yeah, the title (and contents) of the story are total clickbait, but they did helpfully attach the full contents of the FOIA dump. As you point out, there is ambiguity (which is why I used a lot of qualifiers :), but seeing the internal communications around the issue is interesting.
Vice published emails via FOIA that suggest he had made concerns known before leaking: https://news.vice.com/story/exclusive-snowden-tried-to-tell-... This suggests it is at least a little bit true
"Appearing to genuinely care" is different than being empathetic. The former implies the person doesn't really care, the latter is by definition concern for another person.
My comment on HR people caring was a more general statement on my interactions with HR in a variety of situations. As a manager, I often see both sides of HR/employee interactions.
This seems negligent on the part of HR (as well as genuinely awful).
In California, all managers are required by law to take three hours of sexual harassment training every other year. One thing that stood out to me is that there is no need to make a formal harassment claim: when anyone mentions they have experienced harassment to a manager, even in a private conversation, the manager is required to report it and investigate. If the employee says they want to keep the conversation in confidence, the manager is supposed to say they can't do that. If a manager doesn't follow up, they can be personally liable.
Several companies I've been at also have a mandatory "managers and the law" training class. I didn't talk to anyone for several days after taking it. :)
IANAL, but my understanding is that one job of HR is to protect the company. One reason they investigate is to produce evidence that could be used in the event of a lawsuit to prove they took the allegation seriously. Trying to argue with the employee that it didn't happen would put them in a really bad position if they were sued, because it could be used to demonstrate a hostile work environment.
I've seen complaints happen a few times in my career (not involving me directly), and, in those cases, HR took it gravely seriously. They talked to everyone involved and documented the crap out of it. Most of the people I've met in HR seem to genuinely care. I disagree with advice that HR should not be trusted, but my advice for someone who is in a situation where they are uncomfortable is to document everything. Keep emails of all interactions with your manager and HR and send follow up email to summarize conversations you had in person.
One thing that I think is important, and I've struggled with, is making 'fault' be a synonym for 'control'. There's this broken thought pattern where any perceived failure is either:
1. My fault (I failed)
2. Out of my control (I'm powerless/helpless).
Both are pretty shitty ways to feel. I think many people who advise/coach/mentor forget this when they give this sort of advice. I remember listening to one well-meaning coach talk through the "victim vs. owning mentality" and I walked out of the session thinking about everything that was wrong at work and how it was because I was incompetent.
Feeling inadequate is common and natural in a highly competitive environment. It's not our fault, we're human beings.
Bear in mind, everyone who works at the company contributes to this culture. When you say "it's by design," you're implying there's some elite group of people at the company who are doing this out of malice. Even the execs who we might cast most of the blame for this on (who are also human beings) are probably feeling inadequate too.
But at the same time, we have the ability to recognize these thoughts and challenge them. So there is hope to rise above it, even though we will probably always struggle with it to some degree.
"And you still manage to prove that your system is 100x more reliable than human driver."
That's the rub: how do you prove that? If your software stack is 30 million lines of code that was written by god knows who, I would argue it's nigh impossible without releasing it and seeing what happens, which seems morally irresponsible and legally negligent. If you follow strict rules in coding conventions and algorithms, it's easier to statically verify code is probably correct.
I think for many people nowadays, privacy is a quaint, antiquated notion, like Victorian modesty. Things like social media and YouTube have encouraged people to make their lives public, so having the government gather data seems fairly minor.
I find this all very disturbing, but, having grown up without the Internet, perhaps I'm just a relic from a bygone area. Still, I can't shake the uneasy feeling that this all will lead to a very bad place...
Increasing H1Bs certainly isn't Trump's stated position. While he hasn't mentioned it directly, he had Disney workers who were replaced by H1B workers speak at a rally:
http://www.computerworld.com/article/3039215/it-industry/lai...
His website suggests his policy will prioritize protecting American workers:
https://www.donaldjtrump.com/policies/immigration/?/position...
"Establish new immigration controls to boost wages and to ensure that open jobs are offered to American workers first."
The middle managers are given directions by the CEO. The CEO needs to meet profit targets, or she'll be fired by the board. The board is beholden to the shareholders. There's always someone to pass blame to.
When you go to work, you don't give up your moral agency.
There are lots of offices above the retail spaces on University Ave in Palo Alto, and have been plenty of small companies there for decades. I don't think people were upset about that. I suspect impetus for this ban is Palentir. More egregiously, they turned a huge retail/commercial space into their cafeteria. There are big windows in the front where you can see employees eating. Honestly, it's weird.
I think they broke an unwritten social contract: small companies on University Ave. are okay, but you need to move out once you grow up. You can't try take over and push everyone else out.
Do you think lisp being a bit of a niche specialization makes it easier or harder to find people for your roles?
A while back, as spent 3 months sourcing my own candidates as an engineering manager and it was enlightening. I spent a while on each candidate, finding their github repo, personal webpages, and the roles they had held, then wrote a personalized note explaining who I was, what I was doing and why I thought their experience was useful. Out of hundreds of emails I sent, I got a handful of responses. I had a few takeaways:
- People with really good information on-line get tons of responses. Someone from LinkedIn confirmed that a small number of profiles get most hits.
- Most public information about engineers is total crap. Most LinkedIn profiles have no detail to determine if someone is a fit. I looked at the profiles of some of my coworkers who I thought were really good and there was nothing interesting in them. Most github repos have not substantive or interesting projects. Looking at github was a big waste of time.
- Being a recruiter is hard work. It's exhausting looking through profiles and dismaying to get rejected and ignored all the time, especially when you've spent time researching people.
- Often you need to contact people several times before they will respond, even if they are interested. I've found this even when I've been contacted by recruiters: I think "interesting, I'll get back to them" and forget about it.
Recruiting is a volume game. Carpet bombing is the only effective strategy in my experience, which is why recruiters do it. It's simply not worth doing that much research up front.
Also, bear in mind that the recruiting staff is usually divided into recruiters and sourcers. The latter are who are doing a lot of the contacting, and their job is mainly to find lots of profiles, not do deep research. Once they get a response, the recruiter takes over and does more of the relationship building and candidate vetting. Given low response rates, this is also a more effective strategy.
"The only problem is that electric cars won't do anything directly to mitigate global warming, because they will still be powered largely by fossil fuel."
But electrical generation is more efficient than an internal combustion engine in terms of carbon output. According to PG&E:
"Additionally, from well to wheel, electric vehicles emit approximately 66 percent less carbon dioxide (CO2) compared with internal combustion vehicles. CO2 is the principal gas associated with global warming."
https://www.pge.com/en_US/residential/solar-and-vehicles/opt...
hopefully! :)
My electric bill went up by about $80 the first month I got my electric car. Computing the cost is a bit tricky because I have tiered billing and I'm hitting the next higher tier since I got the car. My electric company (PG&E) does have an time-of-use billing plan tailored for EV, but, by my computations it didn't help a lot because we use A/C during the day:
https://www.pge.com/en_US/residential/solar-and-vehicles/opt...
If you charge at night and aren't home during the day, and your electric company has an EV plan, this might help.
I've had a Leaf for going on a year now and one thing I love about it is that I never need to worry about the inconvenience of stopping at a gas station. :)
But I'm with you that I don't really see the point of public charging stations. All the places I drive during the day are within my ~100 mile range (putting a charger at a grocery store, as they mention in the article, makes little sense given that). If I needed to drive somewhere that was not in my range, I sure as heck wouldn't gamble on one of the few charger stations being available.
"decided he wanted to implement a rasterizer (I'd gotten my fill)"
I see what you did there. :)
I'm trying to be charitable in my interpretation, but "always" is a strong word:
https://en.wikipedia.org/wiki/Plaza_Rakyat
http://gizmodo.com/the-sad-fate-of-the-worlds-six-tallest-un...
But rather than split hairs: I interpreted the underlying assertion being that construction is more predictable and reliable than software. I've heard this in other contexts as well. And that didn't pass the gut check for me, because I can think anecdotally of many construction projects (and home renovations) that were way over budget and took longer than expected.
"I mean, have you ever heard of a building project going 3x over budget and then not actually delivering a building at all?"
Construction projects go over budget and are late all the time. Remember the big dig? https://en.wikipedia.org/wiki/Big_Dig
The Sydney Opera house was 10 years late and 1475% over budget: https://en.wikipedia.org/wiki/Sydney_Opera_House#Completion_...
Anyone who's had renovations done to their house can also probably sympathize.
Yeah, in the article he said the hospital was near the freeway exit and he drove manually the rest of the way, which kinda makes the story a bit less dramatic.
How would it know to do that? I assume if he had passed out it would have just continued driving on the highway until it ran out of battery, right?
The lightning port is fairly shallow and the pins are flush with the perimeter. I've found it pretty easy to clean out in my experience.
It's mainly a problem with phone calls: user is on a call, decides to unplug headset, call ends (if you didn't have delay). An edge case, to be sure.