Skip to main content

Tools, tools, tools. And Lambda's

I like tools. I learning about them, learning to use them and simply discovering them.

So, my current topics of interest are an assortment of languages and a discipline. The discipline is "Functional programming" - that lead off to a couple of languages.

Lately, I have been learning Ruby. I like its pure "object-orientedness" and its conciseness and its ability to support functional programming - if you have the discipline. Lambda's intrigued me, but I felt that I wasn't getting the whole picture. Then I read about LINQ - a project based on my bread and butter language, C#. LINQ adds Language Integrated Query capabilities and set handling features, basically to C# itself. Well, how do they do this? OK, Lambda's. In C# 3.0. Well there's something I didn't know about, but I'm starting to see something important take shape.

From there I followed my nose and ended up looking at many neat things. I have tripped over a number of functional programming tools such as Haskell, OCaml and F#. Haskell looked good as presented in A Gentle Introduction to Haskell 98 - particularly since this tutorial gives a good feel for the functional programming model.

How'd I get to functional programming? I tripped over Lambdas in C# 3.0.

Of course, to whet one's whistle regarding functional programming see Introduction to Functional Programming, which is geared somewhat towards Python, but is not hampered by that. The examples are readily understandable and I could see them through to Ruby.

My head is spinning. It's great. Which way do I go? F# and a head first into FP. Oh wait, what about my continued explorations into Ruby and Rails? Oh, and then when do I get to C# 3.0....

Comments

Post a Comment

Popular posts from this blog

You don't really know who you're talking to online...

The following is a story that I think highlights the assumptions that get you into trouble online... https://www.proofpoint.com/us/blog/threat-insight/i-knew-you-were-trouble-ta456-targets-defense-contractor-alluring-social-media This is particularly scary since we found so much utility in online connections during the pandemic and out of necessity, started trusting more online. Please note the timeline for this breach - it was a long, slow process, a key factor in many 'cons'. "Build trust" is a key first step, once someone has identified you as a party. You think...you're convinced you know who your talking to, but if you don't triangulate the identity with some non-online, ideally in-person information, you shouldn't trust. And even if you do get what seems like real-life confirmations of identity, you must look at questioning motives, needs, and keeping danger at arms-length. Online includes email, texting (sms), application chatbots, voice communicati...
Post a Comment
Read more

Threat Modeling Manifesto

Secure Your Code with Threat Modeling As a software developer, security should be a top priority. By proactively identifying and addressing potential vulnerabilities, you can significantly reduce the risk of breaches and data loss. What is Threat Modeling?   Threat modeling is a systematic approach to identifying, assessing, and mitigating security threats. It involves looking at your system from a hacker's perspective to uncover weaknesses and devise strategies to protect against attacks. See the  OWASP Cheat Sheet   Why is Threat Modeling Important? Proactive Security: By anticipating potential threats, you can take steps to prevent them. Risk Mitigation: Identify and address vulnerabilities before they can be exploited. Regulatory Compliance: Adhere to industry standards and regulations. Enhanced Security Posture: Strengthen your overall security posture. How to Get Started with Threat Modeling   The Threat Modeling Manifesto provides a valuable framewor...
Post a Comment
Read more

Where threat modeling can shine - an example from the EU MDCG-2019

From the  EU  MDCG 2019-16 Guidance on Cybersecurity for medical devices, December 2019 , this is the guidance on foreseeable risks.  Medical device manufacturers should ensure that a medical device is designed and manufactured in a way that ensures that the risks associated with reasonably foreseeable environmental conditions are removed or minimised. This may include the infield monitoring of the software’s vulnerabilities and the possibility to perform a device update (outside the context of a field safety corrective action) through, for example delivering patches to ensure the continued security of the device. During the risk management process, the manufacturer should foresee or evaluate the potential exploitation of those vulnerabilities that may be a result of reasonably foreseeable misuse. This, however, may depend on the specific situation. For example, using an unsecured memory-stick to enter data into a medical IT system can be considered “reasonably foreseeabl...
Post a Comment
Read more