3PS · HackerTrans

This feels like the opposite to me? The MoT architecture looks like the ideal that the Bitter Lesson alludes to - just take all of your data in all of your formats (audio, image, text, action, video) and dump it all into a single shared latent space. Then let the model sort things out, with just enough structure to handle the different requirements/output formats needed (e.g. autoregressive stuff for sequence modeling/prediction, diffusion stuff for generation).

3PS

4 ay öncediscuss

Duolingo | Full-time | Multiple roles | $177K-$240K for NY roles | NY and London | Hybrid

Our mission is to develop the best education in the world and make it universally accessible. Our culture is eng-driven, friendly, and very data-driven thanks to our large userbase. Check out our blog to see what engineering at Duolingo can look like: https://blog.duolingo.com/hub/engineering/

Tech stack: (frontends) Swift/Kotlin/TypeScript, (backend) Python/Kotlin/Postgres/Dynamo, (infra) AWS/k8s/Terraform.

We're always hiring for engineers. A few roles below:

Senior Engineering Manager, Chess (NY) https://careers.duolingo.com/jobs/8385137002

Senior Android Engineer (NY) https://careers.duolingo.com/jobs/8217266002

Senior iOS Software Engineer (NY) https://careers.duolingo.com/jobs/8318257002

Engineering Director (London) https://careers.duolingo.com/jobs/8444624002

Senior Gameplay Programmer (London) https://careers.duolingo.com/jobs/8424809002

Base salary: $177-240K for the NY-based roles, unsure about the London-based roles.

Perks: breakfast and lunch served in office, 2-week winter break + 20 days of flexible time off.

3PS

5 ay öncediscuss

Duolingo | Full-time | Multiple roles | $177K-$300K | NY and Pittsburgh | ONSITE

Our mission is to develop the best education in the world and make it universally accessible. Our culture is eng-driven, friendly, and very data-driven thanks to our large userbase. More info about working as an engineer at Duolingo here: https://www.youtube.com/watch?v=WThT8sufdBE

Tech stack: (frontends) Swift/Kotlin/TypeScript, (backend) Python/Kotlin/Postgres/Dynamo, (infra) AWS/k8s/Terraform.

We're always hiring for engineers. A few roles below:

Senior Engineering Manager, Monetization: https://careers.duolingo.com/jobs/8414653002

Senior Android Engineer: https://careers.duolingo.com/jobs/8217266002

Engineering Manager, Chess: https://careers.duolingo.com/jobs/8385137002

Senior iOS Software Engineer: https://careers.duolingo.com/jobs/8318257002

Base salary: $200K-300K for Senior Eng Manager, $177K-$240K for the others (+equity).

Perks: free lunch, 2-week winter break + 20 days of flexible time off.

3PS

6 ay öncediscuss

This is also the case with Google Fuchsia, just replace 9P with FIDL. I'm really hoping Fuchsia doesn't end up just being vaporware since it has made some very interesting technical decisions (often borrowing from Plan 9, NixOS, and others.)

3PS

10 ay öncediscuss

Different bracketing.

"If it sounds too good to be true, it usually isn't (true)"

vs

"If it sounds too good to be true, it usually is (too good to be true)"

3PS

10 ay öncediscuss

I think you're technically correct here: if you just have a bunch of Merkle trees where each one tracks the hash of the previous block, it would be accurate to refer to it as a blockchain even if you're not bothering to implement any of the distributed consensus algorithms that cryptocurrencies are actually known for. It's probably not the first thing that would come to mind, but it is a correct way to use that word.

3PS

10 ay öncediscuss

> One way of thinking about a blockchain is to think of it as a shared datastructure to keep databases in sync. Any time you want to distribute your database over more than just a single central place, in a cryptographically secure way, you're probably going to re-invent a blockchain to do it.

Even more specifically, a blockchain is for when you want Byzantine fault tolerance, i.e. you don't trust one or more of the actors involved. This is the main distinguishing feature of blockchains IMO, the reason we have proof of work, proof of stake, etc. It's also the main thing I saw people getting wrong when using blockchains during the earlier waves of cryptocurrency fever; most proposals for blockchains did make sense as distributed public ledgers, but didn't really need the extra computational overhead because only trusted parties were adding blocks to begin with.

3PS

7 yıl öncediscuss

I'm curious, are you still experiencing issues with localhost networking? I'd read that as of build 18945, those issues should mostly be fixed. [1] Or is it that you're hosting applications on Windows and trying to access them from Linux?

[1] https://devblogs.microsoft.com/commandline/whats-new-for-wsl...

comments