skysight-inc/HackerNews huggingface dataset:
Digital Twin Example for Engineers
Of course AEB is available when autopilot is off, as it’s available on all Model 3, even those without autopilot.
>One is reproducible builds. The standard answer is lock files which is extra bloat and leads to merge conflicts.

You can’t have your cake and eat it too
> Put enough smart people in a room and they’ll figure it out.

Or start a religious war about something or other (which language, framework, architecture, etc). Efficient self-organisation is far from inevitable.
> What is the difference between a diamond and an expensive handbag or other accessory?

They're technically equivalent, but not equal.

Both are artificially scarce, don't have a high intrinsic or practical value relative to other products that serve equivalent practical purposes. Both are produced by very large, sometimes monopolistic entities.

Diamonds are different because:

1. Normal fashion -vs- concerted De Beers ad campaign

Demand for bags is largely governed by fashion, which—while it may confound some, and is certainly artificially controlled/steered by large commercial entities—is at least a somewhat organic thing that:

- (a) has a long human tradition

- (b) has some variance over time

- (c) at least slightly various across the general mainstream population according to personal taste

Demand for diamonds on the other hand is a recent, deliberate invention by a single entity and is quite consistent across the relative diversity of individuals in (western) mainstream populations.

2. Scale of external social pressure

Social pressure to have a fashionable, authentic, labelled bag is relatively high for a certain subset of the population, it pales in comparison to multiple generations of family members relentlessly obsession over the most important day of your life on your behalf.
Notifications. Not for people, but for machines: "checkout is complete on X, and you're subscribed to this event, now do something based on that." If you publish on any event, it's the client's responsibility to choose which it wishes to subscribe to.
Localingual: Listen to voices from around the world
No difference between a diamond and an expensive handbag, inherently. Diamonds are just a very illustrative & extreme example of that.

For example, engagement rings. The custom puts an alarming number of people into financial bother for no "real" reason. The fact that both the custom and the value of the gem are "fake" or at least fictional is easier to demonstrate for diamonds than it is with gold, Gucci handbags or Harvard education.

Gold is at least valuable in the money sense. It has a market price. Diamond pricing is much more opaque. The custom was also invented in recent memory, unlike the custom of costly weddings which can also be an unreasonably burdensome but non-negotiable bit of culture. Both are customs. Both are invented. Both can be bad. Both (as industries) have a get-in-debt economic norm fattening it. But the diamond example is just more illustrative. More fake.

Lots of industries have horrible labour practices in countries where they can, but diamonds are an illustrative case for this too..
Loss avoidance is a pretty strong instinct, so threatening to take away the earned balance might be a good motivator for especially onerous tasks like picking up all these lego pieces everywhere.
I'm optimistic that their strategy will fail. People buying diamonds to show off to others will still buy the artificial ones since they're indistinguishable.
Resale value?
Because it's the only time we see it in action. The speech recognition of my Amazon Echo is still subpar (and it feels like it's getting worse each week) and ad targeting also hasn't really improved. Of all those claims that came with deep learning, Go was the only time where you really saw a result. I'm not sure which version of Android will bring the improved battery life (and which manufacturers) but I wouldn't be surprised if the 30% were a bit optimistic.

I get that a lot of services we use on a daily basis make use of deep learning to accomplish tasks. But I don't really see what has fundamentally changed over the past 5 years in the way I use services. Siri was introduced 7 years ago and while we have clearly made progress in voice recognition, it's nowhere close to what many had hoped.
When it comes to basic price central ducted HVAC system installation you'd be surprised! At least in Australia.
There's a difference between software sandboxing of native code and not being able to run native code at all. WA being an intermediate representation, it's a different story.

I'm not saying there may not be flaws in WebAssembly or what Cervus delivers.
> petabytes and petabytes of flops

Why not petaflops of bytes then?
Cone receptors saturate when you look at the same hue for a period of time and loose sensitivity for a while. It's known as retinal fatigue or cone fatigue and causes after images. It's normal and used in several optical illusions.
What I've mostly noticed is that when people show up with cynicism or actual anger towards Agile-with-an-A, perhaps nine times in ten, Scrum was involved (edit: though this might be sample bias, as Scrum is by far the most popular methodology).

I'm sure it's working really well for some folks. A large fraction of the magic of any agile system is the folks involved and their familiarity and experience with it. I work for Pivotal, our wheelbarrow is XP with Lean trimmings. I've seen it up close for 4 years in both consulting and large product development and -- summarising -- it works.

But no small part of it working is the context. Our context is that we hire carefully and that the entire organisation is interested in, and supportive of, the way we work. It is fantastically easier to do agile well in an environment where it is already done well (which is why we ask our clients to come work in our office).

If I had to pick the most destructive part of Scrum, it's the sprint commitment. Yes, it's called forecasts now, but folks are held to it anyhow. All it does is create a dynamic which generates either waste or burnout. Software should be releasable at all times, not once every two weeks. New features should be presented to a Product Manager as they are done done, not according to what is an essentially coincidental cadence chosen because two weeks is easy to mark on a calendar.

At Pivotal the closest we came to sprints was setting up a quarterly release cycle for our flagship product, PCF. The first few were a mess and we massively overshot our planned dates several times. We switched to something much closer to our normal way of working: release trains. Every quarter we make a release. If a component product has a feature ready at that time, the feature gets shipped. If it doesn't, it doesn't. And that's that.

We already have a lot of our customers who've adopted automation to update their PCF platforms for patches on a rolling basis. My fond secret hope is that one day, we'll be able to drop the quarterly release cycle as well and just ship things when they're ready to ship.
Deep Recession ‘18
I could be wrong but I think you read the comment backwards.
Yeah that might be it, I always hibernate my machines because I like to continue where I have left off.
Jupyter Notebooks are the de facto standard for scientific computing in Python.

http://jupyter.org/
Qt 5.12 to Support Vulkan on MacOS via MoltenVK – Phoronix
My biggest beef with Scrum (and why I think it's a scam) is that they renamed everything, all the processes.

Historically, there are three important sides, and roles, for each project. Product management - takes care what the customer wants to have build. Project management - takes care of what is delivered is on schedule and that there is enough material/personnel to build it. Architect/engineering lead - takes care of whether the thing is technically feasible, what technologies are used and what technical trade-offs are made.

And there was a vast literature and discussion about how these three sides affect the result of the project, and how to solve these problems.

Unfortunately, Scrum, renaming everything, acts as if the history of project management doesn't exist. And if you forget history, how are you supposed to learn from it? That makes it easy to sell snake-oil. I frequently hear, for instance, that scrum master is not a project manager, despite him having some responsibilities in this area.

And as the blog post also expounds, there is no recognition for these three different sides of each project in Scrum (ironically, there is some recognition of that in Scrum derivatives such as Scaled Agile Framework, for instance, modulo nonsensical renaming of the roles).
I've been wondering for a while as to why nobody was trying to run an entire VM at ring 0, the benefits would be significant. I was just not aware that's what Singularity/Midori were doing.

I'm glad more people are picking up on it.
No you purchase the diamond because of De Beers marketing techniques influencing people around and peer pressure.
Its manufactured status symbol for the purpose of enriching exploitative diamond industry that strives to maintain its monopoly at all cost. The reality of diamond industry is far less polished than their PR material:
https://en.wikipedia.org/wiki/Child_labour_in_the_diamond_in...
I'm in Poland, and I know three couples that got engaged the past year. All of them have diamond engagement rings. It's a small reference point, but clearly some people care in Central Europe, and they all seemed excited to "see the ring".
Glimpse into the Future of AI Customer Service: The Next Frontier of Support Ops
They collect virtually everything you do on your phone. They probably notice that you scroll a long way after typing cat and so perhaps surmise the quality of search results was low.
> "Unsafe Zig Is Safer Than Unsafe Rust"

Yes, I've seen that blog post. Definitely a useful analysis, but it doesn't strike me as a fundamental difference, i.e. adding this check (as a warning) to rustc doesn't look too hard and wouldn't break existing code.

Also, as pointed out in the title, that's code explicitly marked as `unsafe` in Rust, so it might not be an entirely fair comparison :)

> "Containers should provide some way to not panic on failed allocations" https://github.com/rust-lang/rust/issues/29802

Definitely a problem, but it's not what people usually call "memory safety". The problem you mention is that of "fallible allocation". A typical definition of "memory safety" is that you can never get a memory access error.

Rust's behavior is indeed to panic in case of failed allocation, letting the developers catch the error at higher level. Barring any bug in rustc, that behavior is memory-safe.

Now, this behavior is quite opinionated and it turns out that it doesn't match all applications, so handling failed allocations is indeed being "bolted on as an afterthought". Just not memory safety :)

(especially since it's pretty hard to get a memory access error in Rust without deactivating safety checks, and it doesn't seem to be nearly as difficult in the current version of Zig)
But the essential difference is that process applied to manufacturing is about repeatability, quality, reliability etc. where process in software is more about communication.

Eventually, maybe, a software process will be more like a manufacturing one but the variation in technologies, techniques and general fashion make that hard - even in limited areas such as CRUD web apps. I think you'd get the same outcomes with a manufacturing process as we currently get with software if every year you changed the engines, materials, electronics and transmissions.
Thank you. There seems to be some serious overdesign in the original article and a many of the follow up comments. Design should follow specific classes of user’s goals and intent, not an attempt to craft a universal solution for everyone, across all time.

Form follows function. If the concept of “10 AM on Saturday” is important to your users, model the software in line with that domain knowledge. All problems are bounded by context, and knowing the boundaries makes designs simplier and easier to manage.
> What annoys me is that when people say "Machine Learning" these days they almost invariably mean deep learning, ignoring all the rest of AI.

But that's not people's fault. Companies only say AI if they mean deep learning. I've yet to hear a company advertising AI if they accomplished it with a linear regression. Maybe experts should stop talking about AI and use specific terms instead (Deep Learning in the case of this article).
If I had to do it over a Jupyter notebook might be cool. It would make the graphing and equations easier. Although, I think simulation graphics are probably better with html5 js canvas.
HashLife: An Algorithm for Compressing Space and Time (2006)
Has he really been learning anything at all?
Scrum didn't rename any of them. They added the roles of scrum master and product owner but those are roles that can be assigned to people with traditional titles in addition to their normal roles.
Quality can be pretty subjective. If you're making a saw-blade that needs diamond tips, synthetic could be even better, as you rightly mention. If, for whatever reason, you value that the rock has been dug from the ground, then on this dimension the synthetic has worse quality.
I know I will get a hell of downvotes for this, but "Brainwashed" term can also be applied to people trading Bitcoins? Some people agreed that it is valuable and gave some tokens a huge value and its a market now.
Not sure why you're shitting on this idea, this does actually get done:

https://nlp.stanford.edu/courses/cs224n/2012/reports/report....

http://sentic.net/radical-embeddings-for-chinese-sentiment-a...

https://github.com/nieldlr/hanzi
> The speed of the solver is not a problem in any other package management system I've seen.

The package manager in YaST (Suse Linux's sysadmin tool) was notorious for its slow solver (and slow everything-else, for that matter) around 2006, when I started using Linux. It improved a lot in the openSUSE 11.x series around 2007/8 when they switched from a homegrown solver to a standard SAT solver package.
What are the benefits of doing so?
> Finally we have this self-organised, cross-functional, non-hierarchical, essentially amorphous development team. They are meant to be self organising, with no one telling them how to build the product backlog. However, they have limited or no say over what is top of the product backlog, pressure to deliver something sprint-after-sprint, and no-one with the authority to balance the product owner and advocate for developing with higher quality.
In fact, the whole way Scrum views the development team is completely flawed given how real organisations operate.

Setting up the scene to fail, and then, surprise, it fails. Blame it on scrum.
This is a great article.
If you spike the brakes at the wrong time on snow/ice, you will lose control of your vehicle and end up in a far worse situation than if you manually brake.
Could be, but isn't. Even with modern cruise control, you're just freed from the accelerator; there's still plenty of driving tasks to keep you alert ("what is that opposite vehicle's intent? Is there something in that shadow, threatening to enter my path? Which of the three closely consecutive exits do I take?"). With the promise of "it drives itself", you're prone to leaving the driver's seat, figuratively speaking (although there are people that have done literally that).
Veblen goods
Classic Whataboutism/Tu quoque.
At least with a Chanel bag you can often sell it for the price you paid (with inflation) if you keep good care of it for years. I know this anecdotally. Since there is no scarcity in diamonds you are lucky if you get 50% back.
" I.e. they take time to learn or practice their skills outside of work projects" translated means "I don't want to invest in people's time or training, I want them to do on their own time."

Seems like you're suffering from same problem as the rest of organization, unwillingness to invest in your employees, just with a slight variation.
Status symbols are always an unspoken tax on the people who want them.

Weddings could be casual ordeals without frills and rigid formalities but they function as a status symbol of sorts.
Good thing you’re not actually in charge of anything.
It's the same as someone who says:

"But you only turn 18 once!"

Which is true for every birthday.
"no-one with the authority to balance the product owner and advocate for developing with higher quality"

In a functional scrum team everyone on the team should be empowered to advocate this. In turn the product owner should be receptive to technical improvement because it is in the interest ultimately of the overall project success.
Maybe he has a problem in finding smart people in sufficient quantity, so he has backtracked to the "process".
Ruby's magical Enumerable module
> That's life. It's fine throwing money away sometime.

Sure if you have the money. The problem is that most people don’t and spend what would be a down payment on a house on complete bullshit. It’s a terrible way to start a marriage and likely leads to higher rates of divorce.
Demo video is very easy to understand
> De Beers has produced synthetic diamonds for years through a subsidiary called Element Six, but it has limited their use to industrial applications.

I'm guessing "industrial applications" includes scientific research, so I doubt too much will change.
Diamond prices are artificially inflated by a single organization. Bitcoin is priced by the market.

(Yes, there is lots of manipulation in the latter, but it's still not comparable to diamonds.)
This is the result of marketing of the De Beers corporation, who ran large campaigns about "Diamonds are Forever" and how important an expensive engagement ring was. That stuck quite well.
https://en.m.wikipedia.org/wiki/De_Beers#Marketing
Oh dear yes, that was certainly something. At least diamonds didn't see that type of rabid frenzy.
GDPR, China and data sovereignty are ultimately wins for Amazon and Google
I can tell you many reasons why this is only practicable with printed text. There are much better solutions for anything digital.
Here's my one piece of feedback: It's all well and good if you look at places where Scrum has failed, but if you don't look at places where Scrum has succeeded, and offer an analysis there, the research is meaningless.

Currently it feels like you're limiting your scope of research to places where Scrum has failed. Is it any surprise, then, that your research has supported your thesis?
For chess, the future possibilities are so vast, you can't call them "perfect knowledge" with a straight face.
Media for Thinking the Unthinkable (2013)
You are right, for me calf is the natural word to use for a young whale. So using the word baby seems to be to trigger an emotion in readers to set a state for the rest of the text. Indicating that it is more wrong to kill a whale than to kill a cow
This methodology places way too much emphasis on the breadth of the tests into a test centric view— say you had a dep that had an SSL vulnerability - most of the time you’re not going to be checking for this type of thing at the level of your app, and doing so - but you bet you need to ensure that you are using the version of the dep that has the vulnerability fixed
How to git-merge VBA in Excel workbooks
Electric Vehicles on the Road Are Set to Triple in Two Years
> Yeah, it's upsetting. As soon as merchandise X is prefixed with "wedding", the cost is doubled. Wedding cake? Boom. Wedding napkins? Check. Etc.

i believe one partial cause of this is because there are higher expectations around the quality of goods and services applied for weddings. e.g. if you make fancy decorated cakes to order, what are the odds that the customer or one of their relatives is going to go berserk and refuse to pay if it has some perceived flaw? probably higher if you are making the cake for a wedding compared to some other arbitrary event.
I find this article lacking, because it makes all of the same mistakes typical of these bandwagon anti-Scrum articles.

Despite working in a a Scrum team, I recognise literally nothing of the problems that are described. Our product owner works closely with both commercial and development groups to build the backlog. Pressure to build good technical solutions is reasonably balanced with commercial requirements. The development team is empowered to step in and request product changes when they think it's necessary. This happens because we are a team of skilled professionals who want to deliver working things at reasonable pace, and this applies to both commercial and development groups.

There is a weird underlying assumption in these kinds of articles that implicitly seems to assume that Scrum will somehow turn a bad team into a good one. I have no idea where that comes from. A team using Scrum still needs skilled people who know how to do their jobs effectively – and that includes the scrum master and product owner roles. Introducing it into a good team can then help to reduce the impact of common software development issues. It doesn't work for every company, team, or product – but that doesn't mean its without value.

I'd be more interested in articles that talked a little about better processes that we can use. I'm absolutely open-minded about the idea that there are other legitimate and effective ways to deliver software other than Scrum, because it's obviously the case. "These are the problems with Scrum and this is why they aren't a problem in <other process>" is more valuable than "If you have a bad team then Scrum is bad".
I just leave this here in the hope another programmer will pick it up.

https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
What is the advantage over motion/heat detection that has been in use at traffic lights for over a decade? If the new tech just uses the smartphone connection to detect if a car is approaching, why not simply detect cars? That also allows to control for size of the car, queues and isn't dependent on the smartphone used.
BeOS. The BeOS filesystem had some nifty metadata features and the company was keen to show those off. Plus, I suspect they had to get creative to seed the OS with apps back in the day.

As a result, many apps ended up feeling like a pretty thin veneer around a file explorer. My memory is a little foggy, but the music player and the email app come to mind.

The opposite model was the iTunes model: a monolithic app that reproduced a bunch of functionality of the file system, but ultimately nerfed the power.

I’m otherwise not too crazy nostalgic about BeOS (NeXT was the better OS in many ways). But man, some things were really great with that system.
Jupyter Lab may be more like what you're after: http://jupyterlab.readthedocs.io/en/latest/user/interface.ht...
No forced upgrades is good, but e.g. from the requirements in the howto on upgrading Mint 17 to 18:

* Good understanding of APT and vast experience in working from the command-line.

Have fun Grandma!
I expected to see custom compiled version with some code removed. Because lobotomizing sounds far more drastic than a pat on the hand.

Now that I'm thinking about this it would be something. Maybe profile it to see unused code after described configuration change. Then remove it and use Profile Guided Optimization to go further.
Lots of tools can do this. I use mitmproxy personally. You can easily customize it by using it as a python library.