Josh Lee
banner
itsjoshlee.bsky.social
Josh Lee
@itsjoshlee.bsky.social
13 followers 12 following 160 posts
Fullstack Software|AI|Cloud|Cybersecurity|Tacos Ruby, React, & AWS + Tools like LangChain, Ollama, PyTorch to Build Secure, Compliant & Cost-Effective Software
Posts Media Videos Starter Packs
In you're in legal and interested about "the cloud" it could seem pretty daunting from a security perspective... But knowing just some of the basics can make you much more confident when making decisions - or even just talking about the technology you're using.
#legaltech #cloud #datasecurity
Designing a Cloud Risk Management Program That Keeps Law Firms Compliant and Clients Confident With…
Moving your law firm to the cloud opens a ton of doors, but let’s be real — it also brings new risks you can’t ignore. It’s not just about…
medium.com
A client once left SSH wide open on their servers because “we just needed quick access.”

Within weeks, their logs showed thousands of random connection attempts from around the world.

Uh. don't do that! lol

#SSH #SecureShell #IP #IPs #VPN #InternetProtocol #Cybersecurity #InformationSecurity #GRC
Turns out the Chinese language may be on to something Because your brain actually does work like a computer.And here's how you can use that information to write better software.

And here's how you can use that information to write better software.

(2/2)
#Ruby #software #coding #RAM #WriteSoftware
You don't need to name methods like 'sumUpAllTheItemsInTheCart'

But writing cleaner code instead of trying to write smart one-liners can make your software much more maintainable.
imagine you're also have to keep up with other items like remembering the q variable means "quantity" instead of just using "quantity" for the variable name, you don't remember what method "calcAv" does, and you're not sure if you're expecting to return a float or an integer.

What I'm saying is...
cart = [ { name: 'apples', quantity: 2}, { name: 'bananas', quantity: 3}, {name: 'cake', quantity: 2}]

When we read code like cart[0][:name], our internal voice is saying "Grab the first item and get the name."

Now that might not seem like much in this example, but...
converting indexes into what they represent. So, while we're coding we may think "Grab the first item and access the value at index 0 to get the product name" when reading cart[0][0].

Instead, if we wrote out that same code as:
when writing code, this is much more important than you'd initially think.

Let's say we're writing code for a shopping cart and store items in a nested array like so:

cart = [ ['apples', 2], ['bananas', 3], ['cake', 2]]

When using that code, we have an extra mental step of...
In fact, the average person can only hold about 5 to 7 items in their short term memory. We often use a technique called 'chunking' to hold more information. So instead of remembering a phone number like 5015551234 (10 items) we remember it as [501]-[555]-[12]-[34] (4 chunks.)

And...
More on exactly why that's important for software developers in a second....

When focusing on something, we typically use our short term memory by loading up the information in our head, using it, and then quickly discarding it.

But most people's short-term memory isn't really that great...
But there can be a balance between knowing when to use AI and when not to use AI.

And at the very least, you should have an idea how AI is being used in the legal field - even if you don't plan on using it yourself

(2/2)
#AI #ArtificialIntelligence #AilnTheLegalIndustry #AiInLegalField #Legalfield
But there can be a balance between knowing when to use AI and when not to use AI.
And at the very least, you should have an idea how AI is being used in the legal field - even if you don't plan on using it yourself.

(2/2)
#AI #ArtificialIntelligence #AilnTheLegalIndustry #AiInLegalField #Legalfield
Your ops team isn’t just “keeping the lights on” or called to put out fires. They’re collaborative and thinking about how to make shipping safer and faster.

(3/6)
Here’s what high-performing DevOps actually looks like:

Your developers aren’t tossing code over the wall. They own what they build—from writing the tests to helping debug production issues.

(2/4)