ksml

Go and Java can memory leak too. Furthermore, they are susceptible to data races that are not possible in safe Rust.

It's a silly exaggerated example. Point still stands, at least from my experience. Even with a rubric, people still (intentionally or unintentionally) find ways to do things that circumvent the learning goals/outcomes of the assignment

Meh. That sounds nice in theory, but there are many good practical reasons to keep answers private. The number one reason for me is it's very hard to build high quality exercises and assignments, and much easier for students to plagarize off answers on the internet. Reducing the temptation to cheat is pretty important for me.

Q: What has been your best investment?

A: My best investment has been a company that has been a good investment.

Very good.

Agreed. I think the lack of dedicated F-row is a dealbreaker for me, as I use the media control keys pretty often

Just want to mention that his email is on his blog, and he's surprisingly responsive for having such a big following. I once wrote him with some unrelated questions and he gave me a detailed response, which I really appreciated!

I don't think anyone is saying depression is your choice. No one chooses to be depressed, and I would never judge someone badly for being depressed. There's no shame in that. It's what you do about it that matters.

Therapy can take time to make a difference, but I would encourage you to give it a try!

I'd love to hear more

I agree with other comments saying that this is going to depend on what you're looking for and on your personal situation -- there is no job that is right for everyone.

That being said, I recently joined Coda as an SRE, and I have really enjoyed it so far. Company size is in my personal sweet spot: the team is small enough that it still has the startup aspects of having visibility into everything happening in the company and being able to work on anything you feel is important, but it's big enough that things are relatively stable, there are lots of resources, there aren't fires all the time. The team is incredible: everyone I have worked with is extremely capable but also extremely nice and humble. Many people joined from highly unconventional backgrounds but Coda hired them for their passion for their roles. I have also felt that the company prioritizes employees in ways both big and small, from little things (e.g. every interview started with checking in to make sure the time was still okay, nice gesture with the chaos of online/remote interviewing) to big things like comp/equity (instead of stock options, you have the option to receive the equity as a grant, or as a loan if you don't have capital to pay the taxes on a grant, and you have the option to sell some stock in every fundraising round even though we aren't public). Several of the founders had kids while starting the company, so there was a strong culture of work/life balance from the beginning. We have our share of tech debt, but so far I have thought the codebase and tooling have been really high quality too.

Email in my bio if you want to chat.

I think the bigger issue is with dishonesty in numbers. They're advertising a different set of numbers to students, and it does not seem like they're being very transparent with the process

That sounds like a pedagogy problem, not a language problem. From my experience [1], students learn JS just fine as a first language, as long as the learning process is structured well. Every practical language has its quirks, and no one learns a programming language by learning all the quirks at one time. You can be productive in JS without understanding all of the quirks, and then build up to that later.

When you're teaching, you should be enabling the student to do one more thing that they couldn't do before. If you're spending 30+ minutes trying to explain what an object is, you're trying to do way too much. You don't need to have a 100% complete and correct understanding of Javascript's object model to use objects.

> Contrast that with something like Java or even Rust where, despite the other complexities, it's pretty clear what the data is and how it is stored.

That's nonsense. Particularly with Rust, now you're deep in the weeds of pointers, stack vs heap vs other segments, and borrow checking rules.

[1] helped design a JS class at Stanford for first-time programmers. Also designed an intro Rust class.

No, parent comment isn't false, even if the wording could be more precise. It is true that M1 CPUs do not execute x86 instructions, but the machines do, in effect, execute x86 binaries. Also, M1 does have added instructions for TSO to improve performance of translated code.