Want to geek out over lunch? Interested in learning something new? Come check out our speakers and come hear about something fun. Every couple of months we host a meeting about something development related, be it security, a programming language, or a UI Framework. We provide the food, you provide the seat warmer.Sign Up Now
Have you ever heard the phrases “beauty is in the eye of the beholder” or “I like what I like” when someone is dismissing your design? Too often good designs are dismissed for aesthetic differences instead of appreciated for its intrinsic value.
Many features of good design are objective, not subjective, and can be either qualified or quantified with predictable results.
Together we will delve into the psychology, physiology, and mathematics of design principles for two key purposes:
On March 7th Visual Studio 2017 will be available for download and Visual Studio itself turns 20. Come join us to learn about what's new in the next version while having pizza and cake! (At least come for the pizza and cake. We've got a lot.)
Ever wonder why teams use Code Obfuscators? What do they do, and what are they for? We’ll look inside PreEmptive Solutions' Dotfuscator to see what it does, what it protects against, and some pitfalls when using it. To familiarize ourselves with its process we’ll look at some which replicates some of the functionality, and compare it against the commercial product.
Understanding the importance of putting the people before the process, and the process before the tool in order to achieve successful continuous improvement for any organization.
No, not really. You need to do user experience research involving the appropriate people as you design your website, product, or service. Come and explore the use of research tools to help you learn more about how people think and work. Join us as we walk our way through a User Experience Design process for Wally, who wants a web site to sell his wallets. He thinks all he needs to do is to put his content into the format of an already successful e-commerce site. Learn about potential customers through activities involving the session attendees and see how this information can be used to create a better design for Wally’s products. An informative and fun introduction to the UX process for anyone interested in creating great products.
Developers commonly face the problem of troubleshooting issues in a production environment with little or no information to accurately determine a solution. Policies prohibit needed access to servers, error logs often show an incomplete picture surrounding issues, and finding the root cause with a partial view of the entire system is frustrating and time consuming leading to increased stress and a longer time to resolution.
Organizations often deny additional expenditure for something not directly enhancing its profit and forces its staff to manually search for a problem’s root cause. The ramification of this is an organization’s failure to consider financial implications stemming from system under performance and outages. Ultimately, they perceive each issue and its resolution as a necessary expense and view finding the issue without incurring additional costs as positive.
With this, developers must find a way to reduce the effort to track and analyze potential issues without incurring additional expense, and by using various systems from open source projects along with relying on small changes to programming, it becomes easy to locate, analyze, and report problems in a clear and meaningful way which reduce downtime, stress, and overall cost.
In functional programming we often use pipelines and function composition to let data flow through a series of operations in a concise, readable manner. Object-oriented languages don't typically support this style of programming but it's possible to achieve a similar effect through method chaining and, by extension, fluent interfaces. Using these techniques however, is seldom an option as they are both architectural patterns that rely on having been deliberately built into the types with which they're used. This is further complicated by the typically statement-based nature of object-oriented languages. But all is not lost. In this talk we'll borrow a few ideas from functional programming so we can not only easily achieve a similar effect in C# but also fix existing broken fluent interfaces such as the one exposed by the StringBuilder.
Even in the most secure Windows environments the communication between development and infrastructure causes issues to slip through the cracks and holes to open on machines. Hopefully, a windows machine running IIS is hardened, but often the misconfiguration of accounts and poorly written .NET code allows attackers to gain information thought to be inaccessible. Once someone gains access to a machine, there are a number of places to look for credentials and alter programs which either allows access to other machines connected to it or change data processed by applications written by the organization.
Most organizations don’t even know these holes exist, because they don’t know where and how they are stored both in the server and applications. Changing registry settings to help with application health, switching account types systems run under, and aggressively validating data passing through parts of an application are all necessary for securing a system beyond the recommended processes. Even with all of this, systems which don’t re-validate inputs from “trusted tiers” are vulnerable, and any code which places unchecked business rules on exposed machines run the risk of being hijacked and subverted to an attackers benefit.