Explore >> Select a destination
|
You are here 
|
jao.io | ||
| | | | |
blog.ploeh.dk
|
|
| | | | | Combine a strong type system with Property-Based Testing to specify software. | |
| | | | |
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. | |
| | | | |
boxbase.org
|
|
| | | | | I lost motivation to all the Unity/C# projects I started during the warm summer days. It feels like any deployment gains are erased by the development pains these tools put you to suffer. | |
| | | | |
www.basicinputoutput.com
|
|
| | | A blog about UEFI BIOS C programming software development engineering computer science history | ||
