BrianSletten
Brian Sletten is a liberal arts-educated software engineer with a focus on forward-leaning technologies. His experience has spanned many industries including retail, banking, online games, defense, finance, hospitality and health care. He has a B.S. in Computer Science from the College of William and Mary and lives in Auburn, CA. He focuses on web architecture, resource-oriented computing, social networking, the Semantic Web, AI/ML, data science, 3D graphics, visualization, scalable systems, security consulting and other technologies of the late 20th and early 21st Centuries. He is also a rabid reader, devoted foodie and has excellent taste in music. If pressed, he might tell you about his International Pop Recording career.
There are many attempts to build data-driven learning and reasoning capabilities these days in the worlds of machine learning and AI. Deep learning systems have had remarkable results, but even its thought leaders and strongest advocates acknowledge the need for “common sense” in the learning process. That means different things to different people, but Linked Data and Knowledge Graphs represent one approach to capture what we know about a domain. They are increasingly being used to present domain views that grow over time and aren't domain-specific using network-friendly standards.
When we productionalize machine learning systems, we are taking our models and injecting them squarely into our production systems. It is astonishing how rarely the topic of security crosses anyone's mind with respect to these models, the training process and what it means for often inexplicable systems that have an increasing bearing on our lives.
Spring has always been defined by its lightweight core. While there has been an overwhelming explosion in the external projects and protocols it integrates seamlessly with, it has also evolved internally to meet the needs of modern development requirements.
Spring has always been defined by its lightweight core. While there has been an overwhelming explosion in the external projects and protocols it integrates seamlessly with, it has also evolved internally to meet the needs of modern development requirements.
Rust is known for many things including being a safe, fast, popular programming language with a steep learning curve designed for systems programming, but finding its way into more and more areas. Rust deserves all of its reputations, but one of the things that doesn't get as much attention in discussions about the language's strengths is its support for "Fearless Concurrency". Language design, the safety-oriented memory model and the borrow-checking engine all combine to make writing concurrent applications in Rust a joy in comparison to some other popular languages.
WebAssembly demonstrations are invariably eye-popping and world-shaking. An amazing array of functionality has already been ported to this new ubiquitous runtime environment, but it isn't always clear how to go about it. There is a difference between code portability and application portability. We will cover both aspects of what WebAssembly does for us in both of these situations.
WebAssembly is one of the most disruptive technologies hitting our industry in quite some time. It gives us the capacity to write portable code that can truly run everywhere. Applications themselves are still tied to the APIs that they use, however. WASI extends the value proposition of the WebAssembly ecosystem to include application-level portability as well a vision for sandboxing that could materially help both our software portability and malware concerns. The combination of benefits provides a vision of the future that might not require Docker in the mix.
Zero fluff.