We've all heard it... or something similar. There's probably one senior guy at work who tells you this at least once a month. You've got an idea for an amazing new feature or practice that's going to save your company both time and money, but it's too 'cutting edge'; your management fears the unfamiliar and you are cruelly stifled.
"It doesn't work like that in Enterprise" is a passionate and motivational story about my journey as a developer in the face of one of the worst fallacies in our industry. The extremes of my experience will make you laugh & cry in equal measure, and maybe help put your own frustrations into perspective. Just remember, it does get better... and you probably got off very f***g lightly!
Let's turn the table. Suppose your goal is to deliberately create buggy programs in C and C++ with serious security vulnerabilities that can be "easily" exploited. Then you need to know about things like stack smashing, shellcode, arc injection, return-oriented programming. You also need to know about annoying protection mechanisms such as address space layout randomization, stack canaries, data execution prevention, and more. This session will teach you the basics of how to deliberately write insecure programs in C and C++. Warning: there will be lots of assembler code in this talk.
David Fowler and Damian Edwards will answer *your* questions about the all new ASP.NET vNext in this follow on talk after you've got the overview from Scott Hanselman. Come prepared with the questions you want answers to or just watch and learn as we peel back the layers of the new story.
It’s time for a design revolution in open technology. Companies like Google and Facebook that dominate the Internet promise us free services in exchange for the right to watch and study us; to mine and farm us. Like quarries, like livestock, we are natural resources to be exploited in a brave new digital world of corporate surveillance that threatens our most fundamental freedoms.
There are open alternatives but they are too difficult for most of us to use.
It is time to bring design thinking to open source and build beautiful, seamless open consumer products that are easy to use and which respect our fundamental freedoms.
It's undisputed that regular peer reviews are one of the most effective ways to maintain high quality in a code base. Yet, so many development teams choose not to adopt them for their software project.In the publishing industry, no written word ever sees the light of day before it has gone through an extensive period of critical review. This applies to books, scientific papers and newspaper articles alike. Why not software?
In this session we'll explore the social and practical reasons why code reviews aren't as widely adopted in modern software development shops as they should be.We'll also look at a few concrete tools and techniques that teams can put in place to help them overcome the most common road blocks. In the end, we'll see how code reviews help peers leverage each other's knowledge and skills to ensure their work is as good as it can possibly be.