Deliberate practice techniques for software developers
As 2019 comes to a close, I’m continuing my tradition of reviewing posts from the past year. This year was divided into two halves. In the first half, I covered topics in discrete math, math for competitive programming, and math learning in general. In the second half, I changed my blog content approach. More on that later.
People debate how useful competitive programming practice is for getting better at real-world programming. But there’s one area where it definitely helps:
Why are people obsessed with competitive programming when it’s not used in real-world programming jobs? (answer)
Why is this post so short? Find the answer, and links to a blog table of contents, at A Summer 2019 Experiment.
To get better at solving coding interview problems, you have to solve a lot of coding interview problems. So a reasonable question to ask (though it’s hard to answer accurately) is:
How many LeetCode problems should I do? (answer)
Why is this post so short? Find the answer, and links to a blog table of contents, at A Summer 2019 Experiment.
This question seems basic, but it’s a core issue in math and programming practice:
What does one do when they read a problem statement, think a bit and figure they don’t know how to solve it? (answer)
Why is this post so short? Find the answer, and links to a blog table of contents, at A Summer 2019 Experiment.