Explore >> Select a destination
|
You are here 
|
peterszasz.com | ||
| | | | |
earthly.dev
|
|
| | | | | In this article, the author shares their opinionated approach to interviewing engineers. They discuss the importance of problem-solving skills, the... | |
| | | | |
solutionslounge.com
|
|
| | | | | Hi - this is Gergely with the monthly, free issue of the Pragmatic Engineer. In every issue, I cover challenges at Big Tech and startups through the lens of | |
| | | | |
phauer.com
|
|
| | | | | How to stand out in job interviews as an engineer. | |
| | | | |
nurkiewicz.com
|
|
| | | When choosing or learning a new programming language, type system should be your first question. How strict is that language when types don't really match? Will there be a conservative, slow and annoying compiler? Or maybe a fast feedback loop, often resulting in crashes at runtime? And also, is the language runtime trusting you know what you are doing, even if you don't? Or maybe it's babysitting you, making it hard to write fast, low-level code? Believe it or not, I just described static, dynamic, weak and strong typing. | ||
