Security is most effective when we build it into the software development lifecycle early — and the earlier developers learn how to do this, the more secure our software gets.
We want to train every final-year student and new graduate in New Zealand and Australia who’s aiming for a career in software development.
So, you’ve read the first blog post in our series, about the global move to make software more secure — huzzah! We’re diving into the second one here. Keen to read the third (and last) one too?
The Secure by Design approach features heavily in the guide the Australian government put out together with international government agencies and partners. But what is Secure by Design, and how does this shift in mindset impact your work as a software developer or team lead? Let’s dive in.
Remember when we all realized that the responsibility for our global plastic pollution problem didn’t just lie with the consumer, but also with the manufacturer?
The same is now happening for the tech sector.
This is the first blog post in a three-part series. Keen to read the second and third posts too?
Hey there, coders, testers, analysts, and software architects — we’ve got something new, just for you.
For the past few years, we’ve made secure development training accessible for more than 5,000 learners and nearly 1,500 organizations worldwide.
Today, we’re so happy to launch our Pro Plan — a new tier of access within SafeStack that’s designed for solo learners who want to level up their secure development skills and earn verified credentials, all with the support of our community.
You’re hiring for a new engineering role within your team. Great. You’ve made a shortlist, interviewed a bunch of people, and sent them a coding exercise they need to complete and submit. Now let’s add ChatGPT into the mix. How can we be sure that the code we receive from prospective hires is actually written by them? We can’t. Unless someone writes the code in front of us, there’s no way of knowing.