Deno took a step in a good direction, but it was an opportunity to go much further and meaningfully address the problem, so I was a bit disappointed that it just controlled restrictions at the process level.
6,302 karma · joined July 11, 2012
Deno took a step in a good direction, but it was an opportunity to go much further and meaningfully address the problem, so I was a bit disappointed that it just controlled restrictions at the process level.
This also means that you cant write a client without loads of branches, harming performance.
I find it odd that grpc had a reputation for high performance. Its at best good performance given a bunch of assumptions about how schemas will be maintained and evolved.
I've no idea whether in this case it directly copied someone else's work, but I don't think that it writing good unit tests is evidence that it did - that's it doing what it was built to do. And you searching and failing to find a source is weak evidence that it did not.
One thing that you definitely can't trace in the DNA is "that group of people tried to genocide my grandparents", but that seems like an important "ethnic group" distinction to you.
This is not to dispute your main point which I take to be that you stop fighting over "ethnic" distinctions by giving people a new unifying identity, but I still find myself thinking that something is lost in the process, even if it is a proven approach.
You can see how this played out in England, a relative latecomer to the increasing year start consensus. Up until the Calendar (New Style) Act of 1750, the year was considered to start on the 25th of March. This means that historical documents in England containing dates in January or February have what we would consider to be the 'wrong' year number on them. Pretty inconvenient, but at least the roman numbered months would have made some sense to a person living in England before 1750.
Given the fantastic iteration speed that the Web platform had (and still does to some extent) I didn't really miss a compiler for catching errors. The main improvement is that IDEs find it easier to support big refactoring.
I also worked on a mid sized scala codebase a little later on. Scala is probably better now than it was then, but despite (perhaps because of?) the cleverer type system, everything was so slow that it actually took longer for many bugs to be highlighted by the compiler than they would have been found by hitting f5 in a browser window with a good js codebase. That was when I realised that as a developer I care a lot about when an error is highlighted in wall clock time and not at all about which compiler phase it was discovered in.
My experience of bigcorp is that they need lots of servers (http is the modern bailer twine) and want developers to act as far as possible as indistinguishable resource. They will have rotating, high churn, globally distributed teams of vendors, contractors, consultants, internal staff and the teams will encompass a vast range of skill levels and abilities.
Some languages amplify skill level disparity, some attenuate it.
I think maybe the more common, but less helpful comparison of go vs rust comes from the fact that they are both part of a new wave of languages and that they both default to producing staticly linked binaries.
If I don't trust them to represent me and the team, then obviously that suggestion wouldn't work, but I'm trying to express the difference between someone pointing out a problem as if the problem is just yours or offering to help take responsibility for the problem as part of a team with you.
I've worked with people who made it a point of pride to always bring a concrete, workable suggestion whenever they brought me a problem. We didn't always go with their suggestion, but they were fantastic to work with.
Thankfully, I've never had to worry about keeping good people on my team down out of fear they'd take my job.
To give good feedback to anyone you need to understand something about the pressures and challenges that they are facing. And remember that everything is a trade off. For example, perhaps they're incredibly busy, and would like to spend more time with new hires, but are struggling to find time because they aren't getting enough blocks of concentration time to work out clear priorities and they have been told they need to give their trusted colleague more opportunities to grow so they delegated it to someone.
Most likely, if you think something is a problem then they do too. They don't need to be told that or criticised for it, they need help solving the problem that causes the problem.
Imagine the difference between "I want to give you feedback that you aren't spending enough time with new hires" vs "I know you've been wanting to spend more time with the new hires, why don't you take them for lunch and send me to your status meeting over Tuesday lunch time this week."
As I started doing more leadership, I became aware that a lot of the things I might previously have cited as predictable examples of leadership incompetence causing problems were not surprises to leadership. They knew that this course of action would cause problems. The reason that they went ahead anyway was because they believed that the problems caused by the other courses of action available to them would be worse.
Of course, there are situations this advice does not apply, maybe the leader genuinely is clueless or evil or mistaken about the severity of a problem, but a good leader when presented with a problem elsewhere needs to start from a position of respect and learning and if you want to give advice to a leader you should start by trying to model good leadership yourself.
Most things of any value are abstractions. You take a country by persuading everyone you've taken a country, the implementation details of that argument might involve some grassy hill tops, some fields and farm buildings, but its absolutely not the case that an army needs to control every field and every grassy hill top that makes up "a country" in order to take it. The abstraction is different to the sum of its specific parts.
If you try to invade a country by invading every concrete bit of it, you'll either fail to take it or have nothing of value at the end (i.e fail in your objective). The only reason it has ever been useful or even possible to invade countries is because countries are abstractions and it's the abstraction that is important.
> The real work is made up of specifics: buildings, roads, trees, ditches, rivers, bushes, rocks, fields, houses.
Specifics are important - failing to execute on specifics dooms any steps you might make to help achieve your objective, but if all you see is specifics you won't be able to come up with a coherent objective or choose a path that would stand a chance of getting you there.
I'm not sure which of them are evs, but you could work it out fairly easily. Even if many of them are, it still looks to me like tesla is doing poorly by this metric.
While the linked article is playing up the tesla angle (and so may be thought to be manipulative) the underlying study does not seem to be unusually focused on tesla, it's simply listing the results of a fairly straightforward analysis. I also have no reason to doubt it as I more or less expected tesla to have bad fatality rates compared to class (although I guess I wouldn't have expected them to be quite this bad - I thought they'd be bad compared to other luxury vehicles of similar weight size and price, not absolutely bad compared to most cars).
But you can find the underlying numbers and critique them if you have reason to think they might be wrong. E.g. if you believed the claims that autopilot was safer than human drivers and was saving lives, you might have expected to see a sign of that in this data (I didn't).
People do of course care about their pets, but John Wick used the death of a pet as its instigating event because it was different, not because it was a remotely usual way to respond to a pets death.
I think probably that on balance you've got away with it though because the people commenting seem to be safely outside the other side of their psychosis and are able to answer interestingly without being harmed by the question.
I'd be quite surprised if objects this precious didn't also have a mini industry of people talking about them, selling them and telling you how to use them properly, even in the bronze age.
The bronze age spanned thousands of years. We went from computers to agile consultants in much less time.
Are these the numbers reported by tesla, or by some third party?