8 Tips to Prevent Your Software from Becoming the Next Big Disaster

Worried about becoming the next headline for a major software disaster? In this video, I'll go over eight practical steps you can take to avoid becoming the next CrowdStrike. I'll cover all the bases from careful dependency management to using safer programming languages.

🔖 Chapters:
0:00 Intro
0:10 # 1Careful Dependency management
2:04 #2 Test Code Before Deploying
3:45 #3 Regularly Revisit and Update the Tools You Are Using
4:43 #4 Limit the amount of users affected
6:06 #5 Rethinking and Limiting Authorization
6:49 #6 Ensure Proper Logging and Monitoring
8:17 #7 Adopt a culture of code reviews
9:44 #8 Use a More Memory Safe Programming Language
10:50 Final Thoughts

#arjancodes #softwaredesign #python

[yickysan]

C++ has been moving towards being memory safe with the memory library but programmers really like c type programming and using raw pointers

[deutschWallah]

Arjan, ich habe deinen Kanal neulich gefunden. Ich muss sagen, dass einige deiner Videos sind sehr hervorragend. Du hast alles wirklich sehr leicht gemacht, besonders wenn es um "Debugging" und "Testing und Deployment" geht. Sehr hervorragend :) Hut ab :)👍

[RonaldChmara]

If I knew any way to boost this to the top of every developer, PM, CISO, CTO (etc.) feed I would, this hits almost all the major basic points.

I'd also add in at least one more thing:
"#9 Plan and budget for the 8 tips as part of regular professional practice."

There are millions of programmers and sec folks nodding along, but then "no time, need to close sprint" and "not budgeted for now" and similar constraints kick in, so the other 8 get neglected until a catastrophe.

[cetilly]

None of this matters if the European Union decides your practices are “anti-competitive” and force you to grant kernel access to any and all, while conveniently turning a blind eye to the MacOS. Dave Plummer does a really good explanation of this in his most recent video.

[alberthalbert]

If this became a Rust channel too I wouldn't be mad. Grasping how enums work with 'if let' and 'match' and separate control flow from type behavior gave me one of the biggest learning dopamine hits I've had in awhile

[AndreaDalseno]

The latest disaster involves a tradeoff between speed and security. If we are talking about security patches (to avoid exploiting some bugs), the canary channel will cause a delay that isn't acceptable.
I don't use Rust, but there are controversial opinions about its use in kernel programming; am I wrong?

[AriteZastrow]

haha - once I broke a whole SAP Module - nothing was working except my part, because I thoroughly tested it (my part only 😋)
some other time SAP itself released some update and crushed our "extension" - right at the beginning and so absolutely nothing was working anymore
but we found these issues already in testing stages
and some other time again - SAP update - no problem found in Test Stage (functionality was not carefully tested here) - made to production and caused a lot of Customer complaints because something was not working - but somehow was not that important so it took a few weeks to solve it 😂

with SAP its not that easy to do "canary releases" (I think) - you roll out the changes to the Production System and its there for all users
and you can not change the programming Language 😜 you have to use ABAP (Objects)

[franktewierikholscher]

I don't think anyone woud like to tell you about software disaster in theorie company, because it is embarrasing and harmfull for the credibility of the company.😮😮😮😮.. i think.

[hvulin]

or just be agile and put a disclaimer in your licence....