jokh

Try github.com/amix/vimrc to start off. It has a nice look. You can then add more shortcuts/customize further as you gain more experience with vim.

Why doesn't Windows drop the purported compatibility with CP/M and get rid of control-z being a special file marker at this point? Lots of legacy code relying on it?

There should also be a Latex library (?) that makes your documents look like they were photocopied, so you can use the coffee stains and the photocopy to make it look like you spent long nights working on your assignments.

Because one day you might need to, and you'll write a 100 lines of code to do it. If you had known what a BFS is and how to write it, you'd be able to accomplish the same task in 10 lines of code.

What kind of internal integrations, if I may ask? Does it automatically deploy code for you on a successful build or something like that?

Any projects you're working on?

Oh, I had no idea it was open source. Thanks!

This would be really useful if it can be run offline. Much easier to use than writing code, compiling it with -S to produce assembly, then trawling through the assembly to look for the code you're interested in.

Who cares about the payoff? Startups will still pay you a good enough salary, and if they don't why would you even consider working there? It's not like startups don't pay a salary at all.

And if a startup does pay well, why is it risky to join? Worst case scenario it folds and goes bankrupt in a year. It's not like there's a shortage of software jobs that you'll be unemployed for a long time. Also, for people who want to become founders in the future, joining a startup is their best option to learn about how businesses are built and what mistakes to avoid in building said businesses.

So not everyone is joining startups just for the payoff or to make it big. People are way more realistic than that.

What's the alternative?

Yeah exactly. I don't understand why they wanted the scheduler to be written in Python, since the scheduler should be decoupled from the jobs they are running anyway.

> problem solving at an architectural level

That's a problem for people who haven't done internships and have just graduated. Architecture skills and knowing how things are/should be designed come from experience, which a lot of people don't have.

On the other hand, algorithms + data structure knowledge and how they're applied do not really require experience, just knowing fundamentals well.

So your method is definitely good for experienced people but not for new grads/interns. And these are methods the industry employs anyway — big companies do stress more on system design for industry hires, less so for new grads + interns.

That's why I said "pay reasonably well". It seems to me that most places that don't interview and filter candidates by asking algorithmic problems don't pay as well as those that do. That's just been my experience as a student that's interviewed for internships and is going to start interviewing for new grad positions in the fall.

Also

> (They do exist, even if they're not as common as they should be.)

I'm curious why you think interviews _should_ be non-algorithmic. How do you propose interviews be done? How else are you supposed to find if someone can employ critical thinking + has the necessary programming skills? And yes, most interview questions _are_ original and not straight from Leetcode so they do demonstrate critical thinking + programming skills.

That is true, but in order to get the jobs you described that pay reasonably well you still need to solve algorithmic problems on Leetcode or CTCI. And sometimes knowing different data structures and algorithms do come in handy, so some problems on Leetcode can be considered realistic.