bjoveski

If you want to learn more about MSFT during Ballmer era, i highly recommend the acquired podcast:

https://www.acquired.fm/episodes/microsoft-volume-ii

They come to the same conclusion as Dan - that Ballmer did a ton of things right and he was actually a much better CEO than the credit he's given today.

Part 1 of the podcast focuses on Bill Gates' era - both episodes are super engaging, the research and preparation they do is remarkably good.

Primer | full-stack eng | staff level | SF/Bay Area onsite | https://primer.com

Come join us at Primer and build the next generation education system with us. Primer Microschools are mixed-age classrooms where kids get personalized learning, get to be more ambitious, and learn to think for themselves.

We are seeking a staff-level engineer to join us as the third member of our engineering team. We are well funded Series A startup (Founders Fund; Khosla Ventures), have an experienced team (early Coinbase, early Uber), and have good traction.

About you:

  - You enjoy building features end-to-end.
  - You have previous startup experience: you've designed, built, and maintained production systems going from 0 to 1.
  - You have a strong grasp of engineering fundamentals.
  - You are excited about being a part of an early-stage team and setting the long-term vision of the organization.

About the role:

  - You will work closely with our educators, designer, and head of product to define and build delightful product experiences.
  - We interact with our users almost every day, and you'll meet lots of students, teachers, and parents. Trust us, you'll see how your work makes a real difference.
  - You will get a chance to set the foundations of our engineering culture and grow with the company. You will help refine our engineering principles and have opportunities for impact beyond your engineering work.
  - We are a small team that gets a lot done well. This is not a cushy 9-5 job - at the same time we do know how to pace the work and take care of ourselves.

Tech stack:

  - typescript, nodejs, graphql, prisma, nextjs, react, relay.
  - render, cloudflare, cloudinary, stripe, logrocket, chatgpt, metabase.

We love our setup and are sure you will too.

If you are interested, please say hi - bojan at primer dot com

Thank you a lot!!

Honeyland is a masterpiece!

There are two places where gas is paid: 1) when the customer pays to these intermediate addresses 2) when the funds are moved from the intermediate to the final address

1) is always paid by the customer that initiates the payment. 2) can be paid by anyone, as these contracts are permissionless and anyone can interact with them. At the moment Coinbase picks up the tab for doing this, but we will likely not be doing this in the long-term

author here!

that's how our ETH processing works at the moment, we derive different BIP44 addresses and the customers pay to them. But that approach is possible only because the transactions fees are paid in ethereum as well; you cannot pay the tx fees in ERC20. With smart contracts someone else can pay the fees, which makes it ideal for our use case.

NY has special license requirements regarding crypto currencies https://en.wikipedia.org/wiki/BitLicense

The file is encrypted locally before uploading to the network. Then the file is sharded, and the shards are replicated among the nodes. Once a shard falls below a certain replication threshold, it will get copied to a new node.

There are other schemes that don't require a copy of each shard, allowing you to reconstruct the file if any subset of the nodes is online.

I've been using an IFTTT recipe for saving the weekly playlists. Works like a charm.

https://ifttt.com/applets/311873p

cache:

https://webcache.googleusercontent.com/search?q=cache:BycZQa...

this might be a good guideline for the folks that don't want to read all of the paper.

http://web.mit.edu/6.033/www/assignments/rec-therac25.html

The Leveson paper is quite long, and not all parts are equally important:

    Skim Sections 1 and 2. You should understand the basics of the Therac-25's design and how it was used. (You may also find this figure a helpful accompaniment to Figure 1 on page 4.)
    Skim Sections 3.1-3.3, which detail a few of the Therac-25 incidents.
    Read Sections 3.4 and 3.5. These detail a particular incident, the software bug that led to it, and the response to the bug. Pay close attention to 3.5.3, which describes the bug.
    Skip Section 3.6. (It describes an additional incident and a different bug—feel free to read if you are interested, though)
    Read Section 4 closely.

Does anyone know what's the percentage cut? The article (and all of the comments) don't seem to say anything about that.

poemotion by Takahiro Kurashima has many amazing examples of this type of art. A very good gift for anyone that appreciates mathy art :)

You can order it here http://www.amazon.com/Poemotion-2-Takahiro-Kurashima/dp/3037...