Let's say you work independently and you get by, but maybe you're a little afraid that if someone were looking over your shoulder you might be exposed — even if you're a senior dev?

For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (78)
memoization
Javascript Document object model.
TypeScript. I fail to see a profit in obfuscating the code so much for better linting.
Unit Tests. It comes from years of inheriting code that did not follow proper OOP guidelines, and thus not easy to write tests for. When entire swaths of business logic sits behind Button1_Click in Blah.aspx.cs, then there's just no easy way to introduce testing.
I've since learned that it's easier to put such logic in a Class Library project, and I even sometimes just have an additional Console Application that references it and I can easily step through without all the manual steps of the UI. I understand the concept, but I just don't have the practical experience 😅
Meaning of pseudo code
invented to make something complex more understandable without the burden of being totally syntactically correct.
if I would write a part in real code, and make one typo, probl. 50% of the people is complaining about "it doesn't compile" instead of getting the idea behind it.
Design Patterns, they are little hard to understand but when you understand them. It is like when you have hammer everything looks like a nail.
10 years on... SQL 😱 please don't tell anyone
Big-O notation.
I didn't graduate in CS, so I never had the chance to learn it academically. And while I could have taken some time to learn it on my own, in my everyday job it's not really that important to aim for the best performance.
It's not like I couldn't see common performance pitfalls, mind you. But if you ask me to compute the big-O value of a function, it's very possible I could be wrong.
And sometimes it bit me when doing Advent of code challenges.
CSS and ReactJS in general 😆
Favorite thread ever