I’d like to express my gratitude and appreciation to @TejasKumar_ - the best mentor and manager I had pleasure to work with: supportive, caring, patient, fair, encouraging, always giving credit to others, not himself, helping each person on his team to shine and reach their goals
In longer switch statements, I occasionally do:
switch (value) {
case 1: {
···
break;
}
case 2: {
···
break;
}
}
Benefit: each case can declare its own variables, without having to worry about name clashes.
Type predicates are just an annotation and aren't actually checked. Meaning you can do some pretty wacky and unsafe things. Is there an technical constraint preventing TS from checking these?
@TejasKumar_@GroundControl Since few months, fasting for 14-16h almost every day, sometimes longer on the weekend. Allows me to melt some body fat and have bigger, more satisfying meals in the evening without counting calories. Still avoiding to eat ~too much~ sweets though - to prevent insulin spikes.
Software development productivity has little correlation to how fast you can produce code.
It's closer related to the total cost of ownership of that code.
Some code, you can write in one hour, and then proceed to waste days or months maintaining and troubleshooting.
🤩Just published📜 CSS selectors cheatsheet & 🕹game.
Feel free to print it out and stick it on the wall 🎑.
Thanks, @iamryanyu for making the game. 🙏
👇&🕹: https://t.co/ImACq1L8KN
📖: https://t.co/IBKNcIM8AG
👩🏻💻 Codepen
https://t.co/HeJyvLLrTV
#css#cssselectors@CodePen
I wish more people would appreciate the power of copy&paste. DRY too often leads to plenty of "reusable helpers". But software grows and what seemed reusable in the beginning ends up with lots of branches inside. Copy&paste until you find the proper abstraction is a good default.
I absolutely love pair programming.
Not because I learn what someone else is coding. I can do that from a review.
I learn their keyboard shortcuts and extensions.
You learn differ ways to troubleshoot and techniques on how they are efficient.