So I’ve been thinking about something.
If a picture is worth a thousand words, does a thousand-words description make a better picture?
At this point everyone has heard about DALLE-2. It’s an AI art generator that will take a human written description of a picture and attempt to create it. If you’ve tried it out, one thing you learn pretty quickly is that the more detailed a description you write, the more accurate the generated photos become.
Sometimes they have the best intentions but don’t quite make the impact they intend to make. Other times, they can even cause the exact opposite of their intent. Unfortunately, for the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA), that is exactly what has happened.
Before jumping into the unintended consequences of these two California laws, it’s probably best to explain what they are. Both laws were made with the intent of protecting the privacy of California consumers by making a set of requirements for medium and large businesses on what they can, and cannot do with California consumers’ data.
Content delivery networks or CDNs are, at their most basic level, multi-function services designed to deliver the content on your website to users fast. There are many CDNs out on the market these days. Some of them are offered as stand-alone services like Cloudflare, Fastly, or Akamai others are offered directly by the big cloud companies themselves like google CDN or AWS Cloudfront.
No matter which company you choose as a CDN provider, they all offer one service in common and that is the ability to deliver certain parts of your website’s content faster than if it were served from its origin where you host it.
What is KTLO? Well, KTLO stands for “Keep the lights on” and given the economic climate here in the US as of the time writing this, it might be a term that all of us start hearing way more often.
Keep the lights on is a fancy way of saying “maintain staffing levels and work on a product to only what is absolutely needed to keep it running reliably and securely”.
So I spend quite a bit of time reading and replying to comments on youtube videos and one thing I’ve gotta say is that it’s pretty obvious some of you are struggling with some self-confidence problems.
And I get it, getting involved in the tech industry can be pretty overwhelming. It seems like there’s a mountain of things to learn and there’s no way you could possibly get through it all and call yourself an expert.
Event-driven architecture is a common pattern found alongside microservice and other decoupled services or apps. In an event-driven architecture, each service in an ecosystem reacts and takes action upon an event it receives. There are both upsides and downsides to event-driven architecture but before we get into that, let’s take a look at an example of how event-driven architecture works so you know exactly what it is.
Let’s say we have a standard eCommerce system that allows users to purchase a product on a website.
What is a cloud architect?
As I’m sure you know, just code is not enough these days to make full solutions to real-world customer problems at scale. most enterprise-grade solutions are a combination of cloud computing solutions, third-party SAAS products, open source tools, as well as custom code stacks that require robust, scaleable hosting solutions. A cloud architect researches a variety of technology solutions and makes plans to combine these different tools to solve business-specific problems.
TDD stands for test driven development and at the surface its a pretty simple concept. Essentially, when practicing test driven development you write failing tests first then write your code to solve the problem which makes the test pass.
Upsides of TDD There are a number of benefits to TDD all related to the idea that the tests are written ahead of time. When you practice TDD as a development methodology, it forces you to focus on individual features until they are complete (because your tests describe very specific scenarios and will continue to fail until you solve them).
So I’ll just come out and say it… The idea of a 10X developer is a myth and a totally unrealistic expectation to apply to yourself (if you are a developer) or to your hiring practices (if you are a hiring manager).
The idea of the 10X developer (or 10X engineer if you prefer the fancier title) comes from the idea that there are devs out there that outperform their counterparts at an extreme rate.
What is a Serverless function or what is Serverless in general?
Serverless functions are a terrible name for what this actually is, but hey, who am I to get in the way of the marketing machines at cloud companies who really like to make things sound like they are better because they don’t have complicated stuff in them?
Anyways, Serverless is really an entire class of computing where instead of being charged for servers running all the time, you are instead charged for individual invocations of your functionality.