sokrates

Daedalus is reinventing precision manufacturing. We are a team started by two OpenAI tech leads (we did the Rubik's cube robot hand project). We're building a distributed system for software-defined autonomous production of precision parts for spacecraft, medical devices, robots, and many others.

Tons of interesting challenging problems in the areas of distributed systems, reinforcement learning, computational geometry algorithms, robot perception & control, scheduling & optimization, FEM simulation, and many more.

No robotics experience required— we're looking for experienced software engineers (e.g. working on SaaS/infra) who are looking for a challenge. You'll join a multi-disciplinary team of folks hailing from SpaceX, Cruise, Stripe, Ripcord and others.

Our stack is built from scratch to power the next generation of robotics: Python, Rust, Bazel, gRPC, runC

Job posting:

San Francisco, CA — https://bit.ly/3udjQdC

Karlsruhe, Germany — https://bit.ly/39A4ojX

Or email me directly: [email protected]

Extended the melody & progression a bit. I'm so proud, this is awesome!

The awkward step naming, and the routing issue, are all with the default steps of an integration of something like Webrat or Capybara. In recent projects (and I think this is the default for newer versions of Capybara), no steps are automatically generated for you. You have to choose the level of detail you want to operate at yourself. Comparing character count of a method call and a Gherkin step is also a rather useless metric.

The "doesn't share code with my test env" issue is a trivial fix: move your test-but-also-cucumber-env code from test_helper.rb into another file, then require it from both cucumber's env.rb and test_helper.rb.

Personally, I write Cucumber features exactly because they mean I don't have to think about routing, or paths, or syntax. I try to put myself in the role of the user and write down what I want to accomplish, and how. A key indicator for reasonably abstracted feature files might be the equivalence "I changed something in a .feature file" IFF "I have to communicate a change to my users."

But if you want to shoot yourself in the foot, you really have to do it yourself.

Not the worst idea ever, in my opinion.

Cue rimshot.

Cue web of trust PSA.

No. AdBlock.

More info: http://boardgamegeek.com/boardgame/54/tikal

Concering the entropy argument, which makes logical sense to me, it remains to be seen how much of an impact coin loss makes. As long as the amount remains small enough, that makes the coins rarer and just makes them rise in value a bit. Of course, as soon as everyone loses their coins, we're screwed. Who knew?

Sadly, I think the conclusion is pretty accurate: once Bitcoin rises above the grass, states will try to crush it with everything they've got. And they will probably succeed.

Well, okay. Don't touch it. It ain't broken. I don't think there's anything wrong with showing people who are not network experts how easy it is to (believably) route things into nirvana. I guess the effects of fake routes being propagated could have been a lot worse than this. Why not promote some discussion and thought around BGP and friends? Maybe we can come up with something more resistant.