Skip to content
Sign in
Artwork for Programming Tech Brief By HackerNoon
TechnologyEducationLanguage Learning

Programming Tech Brief By HackerNoon

HackerNoon

Learn the latest programming updates in the tech world.

Play
Open in
  • 124 episodes
  • Avg 17 min
  • English

Episodes 124

NewestOldestLongest
All4Unplayed4In progress0Played0
Counted on this page — what you have heard stays on this device, so it is not something the list can be paged by.
  • August 5 · 8 min

    What Computer Science Students Actually Need When They're Stuck

    This story was originally published on HackerNoon at: https://hackernoon.com/what-computer-science-students-actually-need-when-theyre-stuck. Computer science assignment help works best when it teaches debugging, testing, and software engineering thinking instead of just finished code. Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #software-development, #learning-to-code, #cs-student-paradox, #programming-homework, #computer-science, #academic-vs-real-world, #education, #programming-education, and more. This story was written by: @davidfaster. Learn more about this writer by checking @davidfaster's about page, and for more stories, please visit hackernoon.com. Programming assignments aren't just about passing tests they're a low-stakes way to practice the same skills real software engineers use every day: debugging root causes, testing edge cases, managing trade-offs like algorithmic complexity, and writing code that's maintainable rather than just functional. The gap between coursework and production software is real, but assignments are where that gap starts closing.

  • August 5 · 16 min

    How STPA Helps Find Unknown Unknowns Before They Cost You Millions

    This story was originally published on HackerNoon at: https://hackernoon.com/how-stpa-helps-find-unknown-unknowns-before-they-cost-you-millions. Learn how STPA helps engineers uncover unsafe system interactions, hidden assumptions, and failure modes before they become costly outages. Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #site-reliability-engineering, #stpa, #software-control-loops, #sre-risk-management, #autoscaling-failure-analysis, #ai-agent-safety-analysis, #control-structure-modelling, #hackernoon-top-story, and more. This story was written by: @slepovss. Learn more about this writer by checking @slepovss's about page, and for more stories, please visit hackernoon.com. Modern outages are often caused not by a single broken component, but by unsafe interactions between systems that appear healthy on their own. This article introduces STPA as a practical way to model control loops, uncover hidden assumptions, identify unsafe control actions, and turn them into constraints before they become expensive production incidents.

  • August 4 · 6 min

    Code Smell 208 - Don't Use Null for Real Places

    This story was originally published on HackerNoon at: https://hackernoon.com/code-smell-208-dont-use-null-for-real-places. Learn why using (0, 0) for missing coordinates creates bugs and how a polymorphic Location type keeps Kotlin models accurate. Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #code-smells, #null-code-smell, #kotlin-null-handling, #sentinel-values, #missing-coordinates, #location-modeling, #polymorphism, #hackernoon-top-story, and more. This story was written by: @mcsee. Learn more about this writer by checking @mcsee's about page, and for more stories, please visit hackernoon.com. Learn why using (0, 0) for missing coordinates creates bugs and how a polymorphic Location type keeps Kotlin models accurate.

  • August 4 · 12 min

    The Case Against Treating Outcomes as the Only Good Key Results

    This story was originally published on HackerNoon at: https://hackernoon.com/the-case-against-treating-outcomes-as-the-only-good-key-results. Should key results measure outcomes or outputs? This essay argues that outcome-only OKRs can hide the work, weaken learning, and reduce shared understanding. Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #okr, #okr-management, #management-by-objectives, #writing-effective-okrs, #outcome-based-key-results, #goal-setting-frameworks, #responsible-management, #hackernoon-top-story, and more. This story was written by: @taboca. Learn more about this writer by checking @taboca's about page, and for more stories, please visit hackernoon.com. When the stakes are high, our objectives all of the sudden are serious. We set great key results that look like wishes. And we keep on pushing our teams to "just solve the problem". The real problem is that we keep on hiding what we do, how we do, and why we do, we keep on forcing our culture to look professional, pushing us towards learning in retrospect and oriented to trial and error. Let's call the fathers of OKR to rescue the essence of it: Key Results are meant to start the conversation about how to close the gap.

Showing 121–124 of 124 episodes