It can be... but it also can be a drag if that&#x27;s not your immediate area of study.  Security is incredibly important, but it is an overhead: including a cognitive overhead.  If I&#x27;m futzing around with a toy project to learn about how, say, distributed agents can make use evolutionary selection to create efficient protocols amongst themselves (yes, a completely bullshit set of terms strung together) and I fully expect this to never leave a group of VMs on a home server.... yeah, security is <i>NOT</i> something I&#x27;m going to sweat.  Doing so would be a distraction and counter-productive to my goals.<p>To be fair to your point, however, by not constantly practicing secure coding techniques, regardless of context, I could get out of the habit of secure coding as a default.  I may simply not think about it at a time when I should be.  By always considering, even in my bullshit toy project, I stick to my good practices and more consistently apply them when it counts.  But the argument that security coding can be interesting and fun is not a good enough argument to care about it all the time.