Explore >> Select a destination
|
You are here 
|
algobeans.com | ||
| | | | |
chelseatroy.com
|
|
| | | | | Last week Aisha Blake hosted me for a conversation about computer science education, from designing an activity to a session to a course. Luckily, we got this recording, so you can watch it anytime! Here's that link to the recording again. Additional notes on what we covered: First, here is the "Designing a Course" blog... | |
| | | | |
randalolson.com
|
|
| | | | | Full stack data scientist, artificial intelligence researcher, and consultant | |
| | | | |
johanneslederer.com
|
|
| | | | | Ali, Pegah, and Milena just returned from the World Congress in Probability and Statistics, where they showcased our work on mathematical machine learning and AI. They also brought a lot of inspiration and motivation back home to Hamburg. Welcome back! We are proud that you are such great ambassadors for our team. | |
| | | | |
enterprisecraftsmanship.com
|
|
| | | Hard coding is often considered an anti-pattern. Having values that can change over time hard-coded in the source code requires recompilation every time these values actually change. While this statement is true, I think that hard coding should be the default choice when developing an application. Hard coding vs configuration file When you work on a project or feature, there always are some magic numbers or strings that potentially can change in future. | ||
