Discover and read the best of Twitter Threads about #NDCOslo
Most recents (24)
My last session for #NDCOslo 2019 will be "Everything is Cyber-broken 2" by @troyhunt and @Scott_Helme. I missed their talk last year due to flight timings so I'm excited to finally see it! 
Check out securityheaders.io, Report URI
Let's Encrypt is challenging traditional CAs
Argh. I took loads of notes but the Twitter app crashed and I lost them :( From memory and in no particular order:
Use OWASP lists
Debugging hardware errors is difficult. Always check whether a bug can be reproduced on more than one machine
Some bugs just aren't worth fixing
Distill your bio down to key points
Talking yourself down makes others awkward. Be positive
Next up at #NDCOslo is "making the most of security tests" by Paweł Krzywicki
White box - secure code reviews
Black box - penetration testing, look at system interfaces, use fuzzing tools etc
Red team - simulate a threat actor
Black box - penetration testing, look at system interfaces, use fuzzing tools etc
Red team - simulate a threat actor
Risk = severity * likelihood * detection difficulty
"fix what hurts the most"
DevOps is not about shipping features quickly. It's about delivering continuous value
The thread pool is managed by synchronisation context
Maximum number of threads governed by available virtual memory
Average age in the software industry is low
The industry is fast growing and newcomers outnumber highly experienced individuals
Next up is "the 7 deadly presentation sins" by Andrew (@coatsy) and Samantha (@BlitzBooks) Coates. Hopefully I'll pick up a few pointers for my inevitable #NDCOslo presentation when I get back to @TeamCodify!
Almost all issues in a performance are caused by either lack of preparation, or lack of previous exposure to pressure situations
Effective practice means repeating an activity until you get it right more times than you got it wrong
Time for something a little different - @richcampbell talking about returning to the moon and what developments in science this might bring. #ndcoslo
A lot of space tech has its roots in military designs. All early American rockets except the Saturn V were repurposed ICBMs
Water and other elements were proved to exist on the moon by essentially throwing a spacecraft the size of a bus at it
EC2 is Amazon's virtual machine service
Kibana is a log aggregation tool
Rust has been around for almost 15 years, and v1.0 was released 4 years ago
Aims to be a concurrent and safe systems-level programming language
Always learn and grow
"Your goal is delivery, not perfection"
Only 7% of emotional communication comes from the content of what you say. The rest comes from how you say it, and your facial expressions while you're saying it
Review the code, not the author
New GC limits and defaults to allow control over how much memory is used
AssemblyLoadContext replaces AppDomains. Supports unloading assemblies! Also supports loading both managed and native assemblies
All languages have trade-off, and different components of a system have different requirements.
Rust offers high performance. C# is a more mature ecosystem which allows developers to be productive
Hot tip: when submitting an abstract, keep in mind that a team who has spent the past 13hrs reading abstracts should be able to grasp the essence of your proposal after reading it max 2 times. If not, chances of rejection is very high. #ndcoslo
Making this into a thread of tips on writing abstracts for a tech conference so that the agenda committee correctly understands your intent.
#2: If you're submitting an "Introduction to [insert hot tech here]", consider submitting a second proposal on an Intermediate or Advanced level as well (given that you know the tech well enough). There is a limit to how many "Intro to X" talks we can accept.
Just realised that I've actually seen Richard deliver an earlier version of this talk at @ADNUGUK. Quite happy to listen again though!
Microsoft was originally a programming language company, not an OS company.
First up today is @fransrosen on Attacking Modern Web Technologies. #NDCOslo
AppCache can be exploited to redirect users to malicious content.
Service Workers are also a potential attack vector, though there are more limitations.
Programmers are immersed in programming like fish in water - are they the best people to articulate what programming is?
Spreadsheets are functional programming - except so intuitive that people don't realise they are programing.
.@adamralph giving a practical guide on finding service boundaries. Hoping this ties up earlier sessions on DDD, architecture and technical debt. #ndcoslo
Systems tend towards the Big Ball Of Mud architecture due to entropy.
This is often the gradual accretion of small, innocuous changes over a long period of time.
Hoping to pick up some networking tips from @korachuta next! #ndcoslo
People avoid networking because talking to people you don't know can be potentially awkward or embarrassing.
Up to 70% of opportunities may not be advertised.
Looking forward to a session on Domain-Driven Design by @ntcoding. There's been a few mentions of DDD in previous sessions. #ndcoslo
The best way to improve your product is to talk to your customers. The next best way is to talk to your development team.
Systems are becoming more fragmented, distributed. The number of devices running and interacting with these systems is increasing.
Writing pure functional code in C# often ends up being unreadable.
F# can express these concepts far more elegantly. Because it runs on .NET, we can call these functions from C#.
