yourabstraction

11 ms·

61.
by yourabstraction 6y ago
If you want the code to flow easy, it's all about putting in the hours and working at the right level of difficultly. Not too hard, so that you're not making any progress, and not too easy such that it's not stimulating your
62.
by yourabstraction 6y ago
Yeah, it's really easy to get overwhelmed by the raw amount of stuff to study. I found I just needed to be consistent, and get through 3-5 leetcode problems a day, while trying to force myself to hit the problems in areas I was weaker.
63.
by yourabstraction 6y ago
I completely agree about leetcode lacking a technique map/graph/tree. This would be immensely useful. In my studies I found that I naturally gravitated to classes of problems I was already good at, because that way I could avoid t
64.
by yourabstraction 6y ago
See my response below to polishdude20 for some advice.
65.
by yourabstraction 6y ago
Yes, and I went against the standard advice to not look at the solution until you solve it yourself. I think for the first 50-100 problems it's best to not think too hard about it before looking at the solution, gaining a full understa
66.
by yourabstraction 6y ago
Yes, it's extremely tired. FAANG companies are not dumb, they hire at scale and know how to find talented engineers using a rigorous/repeatable interview process. I think most of the complaints come from people who fail these inte
67.
by yourabstraction 6y ago
Yup, I jumped into the if you can't beat em, join em camp with leetcode. I Did 160 problems (likely low for many people) before my last job search, and I now make 3x what I used to. I gotta admit it's a hell of an ego boost to cru
68.
by yourabstraction 6y ago
Yes, I think scheduling plays a large role in things too. But, the main thing I'm getting at is how to find creative ways to integrate leisure time into your working day. Taking a nap in the sun at lunch time not only gives me extra le
69.
by yourabstraction 6y ago
Everyone is talking about shifting time around by doing things like getting up earlier, but that doesn't get around a fundamental problem of not enjoying the working part of your day. You still have the same amount of time, just shifte
70.
by yourabstraction 6y ago
This is exactly it. The idea of a 10x engineer isn't one who codes a similar implementation 10x quicker, that's ridicules and clearly taking the idea too literally. There's a clear upper bound on implementation efficiency, an
71.
by yourabstraction 6y ago
Wow, thanks for this post, it seems obvious now, but it really gives me some closure on a startup role I burned out on after a year. I totally had foundersyndrome, and it was extremely stressful because there was a total mismatch between my
72.
by yourabstraction 6y ago
This is exactly how I look at technical debt, yet it seems so many people miss the appropriate financial metaphor, which seems obvious given debt is in the name. It seems popular to conflate technical debt with bad engineering, but appropri
73.
Ask HN: How do you develop an appreciation for CS and algorithms
2 points by yourabstraction 6y ago|0 comments