sciencewolf

Reminds me of https://ramenapps.com

This is outstanding!

As others have said, every other request is a 504 at the moment.

But for the platform itself-- pretty cool that you have file separations and visual renderings, going beyond simple code execution. I like it. I tried build something similar on algodaily.com a while back, but found that my audience wasn't that interested in creating tutorials.

Some feedback:

1) I wasn't immediately sure there were multiple steps at first.

2) Execution time is a bit slow.

3) I was monitoring the network calls and saw no requests when code executed -- are you doing this in the client? Just a heads up that there's some security vulnerabilities to be aware of.

4) The UI could use some polishing. Maybe look for a color palette that blends colors together better.

Congrats on shipping!

Hey Marc,

I'm not as cynical as notretarded, but I do wonder how you'll eventually make money. It can't be cheap to manually edit 1,000+ resumes weekly, so it does make me wonder what the end goal is and what the paid services will look like. Maybe some AI/data play?

Your blueprint to good technical resumes is super useful though-- I run a technical interview course and mentor quite a number of software engineers, will definitely share out.

I used to use the ladders all the time when looking for jobs, so thanks for creating that service too.

VSCode is a Microsoft product: https://github.com/microsoft/vscode - their core developers work at Microsoft

Spam would be my biggest concern too.

Hard disagree. Building, shipping, and learning from my mistakes is the only I was able to actually apply anything I learned from books. IMO the best method is to do both - start building now, and read books relevant to whatever part of the journey you're stuck on or need help with.

Wanted the fundamentals in a cheat sheet to review before interviews! Hope you learn something new today

Having a problem to solve in front of us can make us tinker on it's available solution and that's where those tutorial come handy.

This is huge. Start with the problem and read/watch enough to gather a solution, rather than learn for the sake of learning. Reminds of me just-in-time advice vs. just-in-case advice.

Technical interview course that focuses on being accessible to beginners through visuals - https://algodaily.com - Imagine leetcode with a lot of hand holding.

Recently wrote about hitting 3k MRR at https://algodaily.com/blog/what-i-didnt-expect-to-learn-from...

Can you link to an example summary we can play with?

I'm trying to understand why businesses would pay for these notes. The only things that come to mind are research/AI purposes-- essentially having a dataset to feed into marketing or market-research efforts? Maybe someone can enlighten me.

LOL /r/richpeoplefinance is not a real subreddit. Did you mean /r/personalfinance?

Same here. Staying in NYC to have access to headquarters and better tech opportunities. If remote continues after Covid passes, the Research Triangle sounds fun.

Check out https://www.arist.co/

Surprisingly, it's the skill of doing less than I can. The act of holding back has actually significantly boosted my focus. I write about it in https://algodaily.com/lessons/how-to-have-a-slow-and-boring-..., but purposely moving slower does the following:

1. It makes you focus on the task at hand, since you're no longer thinking about another vector (speed)

2. It guarantees that your daily energy reserves are enough to keep you interested

Totally, 100% agree with this. I would even take it one step further, and say that there are really good tools for developing this mental model nowadays. I didn't really feel like I understood what code was doing until I used tools like chrome devtools, pythontutor.com, or algodaily.com to visualize and step through iteration. It's helpful to know what's happening at each line with the call stack, variables, references, etc. -- but it can be intimidating to start. Drawing it out on paper first might be a better way to begin.

Digital color meter to get colors from webpages.

I would imagine most people you know would have a difficult time running a website, even on Wordpress or something remotely technical. I used to work at a large website builder (think Wix, Squarespace, etc.) and it was shocking how many people hired out the drag-and-drop functionality for their sites!

Wow, the response to this was great! Thanks all for upvoting. Small plug-- https://algodaily.com uses illustrations and visuals to teach technical interview concepts. We're coming out with a book soon! If you liked this cheat sheet, you may be interested in signing up for our 100 days of free interview problems newsletter at https://algodaily.com/challenges/daily

Thanks! There's definitely plans to include more. For now, a lot of additional material can be found at https://algodaily.com/curriculum :-)

Hope this helps some people :-) I've always wanted a cheat sheet that I could print out or save as a reference. A quick scan before interview day will be sure to help you feel more confident.

Hey Jack,

Just a heads up - I tried to sign up for your mailing list but kept seeing "ERROR: Did you forget to type your email?" even after typing the email. I've tried a few different emails and also tried viewing the page in incognito mode. Hope you get this fixed soon, as I'd really love to get more of your content!

When studying for interviews, I tried to use Python as much as possible for its clean syntax and expressiveness. However, it was surprisingly hard to find a "cheat sheet" where I could get a quick glance of trivial language-specific interview questions that I might get.

I created an interactive tutorial that covers the basics of Python, and possible interview questions that might be asked at the junior-mid level. It allows you to try the features as you review them. Hope you find it useful!

I actually wrote a very similar article recently: https://algodaily.com/blog/does-studying-for-whiteboard-inte...

I'm not sure how people in the comments are saying that the "advanced stuff is never used", when the author used the A* search algorithm at work! I'm especially fond of this passage:

You should also know about basic data structures that are pretty common, like hashtables, queues, or stacks. But specific algorithms like Dijkstra or A* are not ones you'd need to memorize: you'll have a reference for this, just like I had when implementing crypto.

Everyone complains about the lack of applications for these interviews, but there's not really an expectation to go beyond the fundamentals.

Backtracking is a very important concept, especially in whiteboard coding interviews. It is also often used to identify solutions that satisfy a given constraint.

After learning backtracking, I found that it changed the way I thought about problems. Rather than trying to "conjure up" a magical, efficient solution-- backtracking is actually the process of iteratively finding many solutions, without wasting time on ones that don't work.

We created this tutorial to help beginners understand the power of this technique. We try to accomplish this by walking the reader through increasingly difficult examples, showing how we can efficient backtrack our way to the right solution.

I wrote this as I recently picked up meditation (in the past year) and have found tremendous benefits professionally. This article explores exactly why this happens.

Thanks so much for the heads up :-) It's amazing how much of the user's perspective you miss when you're heads-down in code all day.

I've added some navigational indicators to hopefully make it a little clearer that you can press the footer buttons or swipe on the screen. Appreciate the friendly feedback!

I think I'd agree, but my argument is that going from a medium problem solved "pretty easily in a bad way" to a "fully optimized and efficient way" is easier than most people think. There's only a dozen or so patterns needed.

As an example, if you know the two pointer technique (https://algodaily.com/lessons/using-the-two-pointer-techniqu...), you're well on your way to solving at least 1/3 to half of array problems in a performant manner.

You need to figure out _why_ you can't do medium problems. If you can solve easy ones, it means you have the fundamentals down, and probably just need more exposure.

250 sounds like a lot, but I'd also be curious how you do the problems, and why you're having issues.

Where are you getting stuck? Are you looking at the answers immediately? Or are you struggling through the problem, and only peeking at hints as much as is needed to make a breakthrough?

Do you think through and recognize the patterns (two pointer, greedy, dynamic, etc) that are needed to tackle the problem, or are you just jumping into code instantly?

What do you do when you get stuck? Do you confidently ask for help, knowing hints are part of the game?

How's your timing? Are you getting in a brute force solution and an optimized one?

Addressing these concerns will reveal where you need work, and then you can continue to get better without being too affected by your current state. Remember, no one was born knowing how to solve these problems, so you can always get better and reach your economic goals.

Small plug -- we created AlgoDaily (https://algodaily.com) to teach programming interview skills using a visual, patterns-based approach. The lessons on approaching the interview and how to prepare might be especially helpful.