Beginis in the AI Infrastructure Industry

Begin

begin

Photo by on Jp Valery Unsplash Architect users often ask for some way to avoid large surprise bills from AWS. The budget-watch plugin sets a cost limit for your app and temporarily shuts it down when the limit is reached. It is the first step to solving this problem for our community. Scaling is a built-in feature of dynamic apps using cloud functions. But if your app can scale to infinity, so can your bill. Many users have this concern, even though it rarely happens. Amazon has many services to help monitor billing. Setting an account-wide budget alert is a relatively easy first line of defense. But configuring more fine-grained monitoring for a single app is not so easy. It’s a little like trying to fix your car by breaking into your mechanic’s garage. The billing services are too complicated for a small team to devote their limited resources to. The unit of deployment in Architect is an individual app. None of the AWS budget solutions easily scope to a single app. You might have one app you expect to cost $100 per month and a dozen other experimental apps that you expect to be free. You should be able to easily set these limits and have some assurance there will be no surprises. What Budget-Watch Does There are many ways an app could run up your bill. Maybe you hit the top of hacker news, or you might have an infinite loop. The simplest way to stop a runaway app is to shut down the compute resources. By setting reserved concurrency (how many simultaneous executions can run) on all lambdas to zero, you can effectively stop most things that cost money in your app. You install the plugin with , and then add the four lines shown below to your app manifest. npm install @architect/plugin-budget-watch @plugins
budget-watch

@budget
limit $40 If the app uses multiple plugins, budget-watch should be listed last so that it is the last one applied. When deployed, it attaches a budget alert scoped to just the resources of the app. If the cost of those resources exceeds the limit set, a shutdown is triggered. To restart the app, the limit can be increased or removed and the app redeployed. This resets the lambda concurrency, and the app will resume operation. You can see the code on for more details. github.com/architect/plugin-budget-watch Implementation details (the messy parts) We would love to see Amazon build this feature into the platform. Solving this problem from the outside exposes many rough edges in the billing and CloudFormation APIs. The three biggest challenges are: Enabling tags Slow billing updates Managing configuration drift Enabling Tags An ideal solution would be deployed entirely through the app manifest using CloudFormation (AWS’s infrastructure as code that Architect uses underneath). All that is needed to scope to an app is a single auto-generated tag ( ). But before this tag can be used, someone needs to navigate deep into the AWS console to activate it. This only needs to be done once, but it breaks the ideal user experience of avoiding the console altogether. Some users may not be allowed to activate tags because of account limits set by their organization. aws:cloudformation:stack-name Billing Updates Amazon bills you by the millisecond but only lets you check three times a day. It’s like touching a stove and finding out eight hours later that you got burned. You can set all kinds of alerts on all sorts of dimensions, but you can’t do any better than 8-12 hours of granularity. Even if you set an alert for a limit you have already passed, the notification may still be delayed for half a day until the next billing update. Drift detection Deterministic deploys are a core feature of Architect. You get the same infrastructure every time you deploy the same app manifest. This plugin should not break that contract. Setting a budget limit and resetting it after it has triggered are all done from the app manifest. To shut down the app, the plugin changes all concurrency by directly calling the lambda API. This causes a drift (out of band configuration changes to infrastructure) between your app and manifest. This drift needs to be reversed if the app is restarted. If you deploy the same CloudFormation template, it will not make any update because the template has not changed. AWS has “Drift Detection” that you can enable to monitor the out-of-band changes, but it requires clicking around the console to enable it. There is no way to turn drift detection on with CloudFormation, and there is no way to automatically reconcile that drift by having your template overwrite those configuration changes. Not only that, drift detection does not even monitor the relevant lambda configurations. The workaround for this drift reset is to use a CloudFormation Custom Resource as a reset mechanism. Custom resources are intended for provisioning infrastructure outside of AWS and connecting them to your stack through CloudFormation. They have lifecycle hooks for creating, updating, and deleting that run custom logic. After the budget-watch limit is triggered, it can be reset by increasing the limit in the manifest or by removing the limit. This triggers an update in the custom resource that resets the concurrency back to its original settings. Other approaches considered There are many ways to build a feature like this with AWS building blocks, but most suffer from the same limitations (i.e., 3x/day updates). Two promising approaches considered were cost anomaly detection w/SNS alerts and budget-triggered actions. Cost anomaly detection was not used primarily because the alerts look for deviations in billing rather than absolute limits. What is the “expected” budget for the app I just deployed for the first time? Budget-triggered actions seemed like the most promising solution provided by AWS. You set a budget with an alert that has automated actions attached. The challenge is that the actions you can specify are permissions, policy, and instance-based. These actions end up tightly coupled to implementation details of the app and must be updated as the app changes. Limitations The actual causes of large surprise bills are as varied as the many services that AWS offers. This solution cannot possibly catch every single one. It focuses on the biggest source and applies the broadest intervention. Architect is a very flexible framework. It is possible (especially with custom plugins) to include infrastructure that will not be shut down by budget-watch. This plugin is still in Beta. We encourage people to try it out and give feedback. If you want to add the plugin to your Architect project you can follow the instruction in the GitHub repository ( ). architect/plugin-budget-watch What about Begin users? has a generous free tier, so users do not have to worry about costs. But for those on the paid tier, we will soon make this feature available to all users of Begin. We hope that AWS will build this into the platform in a more usable way. Until then, we hope to relieve some of the fear of unexpected bills. If you want to build scalable web apps with Begin for a free account today. Begin.com sign up

Avoid Surprise Bills from AWS: 'Begin' Saving Today

The debate over whether to use a single-purpose function vs. a fat lambda continues to this day, and in this post, we hope to convince you that Fat Lambda is truly an anti-pattern. What is a Fat Lambda? A fat lambda is a pattern in which you group related code together in one or more files. This lambda uses internal routing to decide what code to execute based on the invocation event. The internal routing may be hardcoded: exports.handler =  async function (event, context) {
    const { path, httpMethod: method  } = event
    if (path === '/apps' && method === 'GET') {
        // get apps
    }
    else if (path === '/apps' && method === 'POST') {
        // create app
    }
    else if (path.startsWith('/apps') && method === 'PUT') {
        // update app
    }
    else if (path.startsWith('/apps') === '/user'
             && method === 'DELETE') {
        // delete app
    }
} or it could be using some middleware like Express: let arc = require('@architect/functions')
let express = require('express')

let app = express()
app.post('/apps', (req, res) => // Add App)
app.get('/apps', (req, res)=> // List Apps)
app.put('/apps/:id', (req, res)=> // Update App)
app.delete('/apps/:id', (req, res)=> // Delete App)

exports.handler = arc.http.express(app) Pros Related code is grouped together. Code is shared between event handlers. Cons Cold start time increases for every extra byte of code you add to your lambda. Changes to the way you handle one event necessitate updating the handlers for all the events. Fat functions do not follow the . single responsibility principle Higher cognitive burden when you need to modify the function. Routing logic needs to be hardcoded or delegated to another package like express. So What's the Alternative? Instead of creating a single function that handles multiple responsibilities, we have the single-purpose function pattern where many functions do only one thing. // add-app.js
exports.handler =  async function (event, context) {
    // add app
}
// get-app.js
exports.handler =  async function (event, context) {
    // get apps
}
// update-app.js
exports.handler =  async function (event, context) {
    // update app
}
// delete-app.js
exports.handler =  async function (event, context) {
    // delete app
} Pros Easier to optimize the function to reduce cold start times. Smaller lambdas make it easier to write testable code. It follows the single responsibility principle. Lower cognitive load when making changes to individual lambda. Routing logic is offloaded to CloudFormation/API Gateway. Cons Harder to share code between lambda. Maintaining multiple lambdas can be tiresome. Evaluating Fat Functions vs. Single Purpose Functions Fat Functions have a few pros over single-purpose functions, but I would argue that they do not override their negatives. Proponents of Fat Functions say that grouping related code and sharing code between event handlers is a significant advantage. However, using tools like or makes managing many functions and sharing code much more straightforward. Architect Serverless Now on to the cons. Cold starts Lambda functions are dynamically provisioned. When you request a lambda, it runs through the following steps: Downloads your code Start new execution environment Execute initialization code Execute the handler code The time in which it takes to complete the first three steps is what we consider the cold start penalty. This gives us a couple of levers we can pull to reduce cold start times. The first is memory allocated to the lambda. What is somewhat surprising about our findings is that the amount of memory allocated to your lambda has a negligible impact on cold start times. The other lever we can pull is code size. We were looking at cold start times using a package with a JavaScript function and several large binary files to increase the package size. None of these binary files are referenced from the JavaScript function, so they are never parsed/interpreted. They are merely included to increase the package size. We can see that downloading and unzipping the package does not affect the cold start time. However, when we increase the code complexity so that the runtime environment loads and parses more JavaScript, we immediately impact cold start times. We start with a base JavaScript function that includes no external dependencies and then increase the amount of code parsed during the code initialization phase. Avoiding fat functions and sticking with single-purpose functions limit the cold start penalty when running your lambdas. Reduce Update Thrashing When you deploy a change to a single-purpose function, you only update the code for handling a single event type. However, with fat functions, you update the code that handles multiple event types, which increases the likelihood of introducing bugs in unrelated code paths. Therefore you have to do more testing to ensure you are not affecting your production environment. Single Responsibility Principle The single-responsibility principle (SRP) states that every module, class or function in a computer program should have responsibility over a single part of that program's functionality, and it should encapsulate that part. All of that module, class or function's services should be narrowly aligned with that responsibility. Fat functions don't adhere to the SRP. In the above example, our fat function is responsible for creating, updating, reading, and deleting our apps. It also means our fat function does not follow the as it requires the ability to read, write and delete apps from our database. principle of least privilege Decomposing the fat function into single-purpose functions follows SRP and allows us to assign the lowest level of permissions to each function. Cognitive Burden Proponents of fat functions state that grouping related code together reduces the cognitive burden of maintaining the code, whereas we would argue that it is precisely the opposite: It is harder to tell from the outside exactly what responsibilities a fat function has as they are a multitude. In contrast, suitably named single-purpose functions like or are pretty self-explanatory. get-apps delete-apps-appID Debugging fat functions because of their branching structure could take more effort to understand, while a single purpose function is relatively straightforward. Fat functions often make debugging more difficult by bundling back-end code, another anti-pattern we will address in a future post. Whereas single-purpose functions generally product stack traces that point exactly to the line of code where the error occurred. In Conclusion The allure of fat functions to quickly convert a node application into “serverless” application is appealing, but the work doesn’t stop there. If you are currently running a monolithic node application, you can wrap your app in the and then decompose it into single-purpose functions. By breaking the app down into single-purpose functions over time, you will reap the most benefits. Architect Express Migration Helper First Published here

Why you Should Stop Using Fat Functions in Your Lambda Code

One of the books that caught my eye for technical development recently was the popular . Staff Engineer by Will Larson What really drew me to the book was the in-depth interviews with 14 people that were Staff Engineers who spanned the archetypes that he discusses in the book. For those of you that haven’t read the book, the archetypes are: typically scopes complex tasks, coordinates their team towards solving a problem, and unblocking them as necessary. They also closely partner with the team’s product manager. Tech Lead - responsible for the success of a specific technical domain within their company where the domain is complex and central to the company’s success. Architect - solves complex problems that are typically high-risk and need a clear approach. Solver - operates as a senior leader without direct managerial responsibilities. Right Hand - 9 Lessons I Learned from The Book Find work that energizes you Staff engineer at Stripe, Michelle Bu, talks about the importance of finding work that keeps her energized over work that is impactful. Her distinction between energized and impactful is the former is more inward-looking while the latter is more company-centric. I think at times, we feel pressure to take on the work that has the highest visibility because it will be what is easiest to call out in a promotion packet or what will stand out to senior organization members. However, work that excites you is essential to keep you motivated and enthusiastic. Teams or team leaders should make an effort to increase visibility for work that is not flashy but just as important such as work to reduce on-call noise, etc. I think it pays to take a look at the things you’re doing day-to-day and figure out what actually gets you enthusiastic and seeking out similar work. Be deliberate about learning Michelle Bu, also talks about being thoughtful about her technical gaps and being intentional about filling in those gaps by carefully choosing projects to work on. As a software engineer, it is very easy to repeat the same year, every year. By that, I mean you can have made little to no progress on your technical skills year after year if you’re not intentional about what you want to learn. In larger organizations, it’s easy to keep signing up to take on the type of work you already know how to do instead of challenging yourself and taking on work you think you might fail at. Whether it's learning through external courses, expanding the type of material you’re reading, or actively pursuing projects that use technologies you’re unfamiliar with, you have to intentionally get uncomfortable to grow. Be picky (if you can) about where you work I understand that not all of us have this luxury, but the general idea is to focus on working somewhere that will help you grow in ways that you want to and being intentional about where you’re going to get that growth. I’ve personally found that having a quarterly check in with myself and re-evaluating my current skills, what I want to gain, how I think I should grow has helped me be honest and objective with myself about my growth, and my growth at my company. Make an effort to make connections Make an effort to establish good relationships with peers, senior leaders with your company and people in the industry in general. This will help you in the long run when you may need to convince decision-makers to see your point of view or get buy-in for technical decisions. Senior Staff Engineer at Split, Joy Ebertz, says in his interview “The more senior you get, the less your job is about code.” Nelson Elhage, former Staff Engineer at Stripe, highlights that it's important to have good relationships with engineering leadership so you know what problems they perceive that you don’t perceive and you can understand what their incentives are. Cultivate a good relationship with your manager Bert Fan, Senior Staff Engineer at Slack, calls this out in his interview. He explains that developing a relationship with your manager where you trust one another will result in your manager handing you important projects. If you successfully execute on the project, it will be easier for your manager and yourself, to advocate for your promotion. In cultivating a good relationship with your manager, it is also important to be honest and open with them about what you want to do instead of just telling them what they want to hear. Remember that your manager's success depends on your success and you should be honest with them about what you like/dislike. When you notice problems, act on them instead of letting them go This theme was common in many of the interviews. One staff engineer said the higher up you go, the more you have to care about. The more junior you are, the more you can get away with not caring about things and assuming that it's someone else’s problem. The attitude of caring and taking responsibility, will show itself to the people around you. If you care about your impact and take responsibility for the effect that your code/what you do has on your product/codebase, it will show itself in your PR’s, in how you respond to Slack messages, and your in your depth of knowledge. If you don't care, then it might be a good time to dig deeper and figure out why. Follow your passions Acknowledge what you’re good at, what you care about and try to do more of that. We weren’t all made to churn out thousands of lines of code, or build complex architecture. However, we do each have different skills and strengths that we bring to the table which if cultivated, can do some real damage. Figure out what your strengths are and how you can apply them in the context of your role. Rick Boone talked about how he had always been fascinated by human psychology and behavior and his natural interest helped him excel at his role as Strategic Advisor to the VP of Infrastructure at Uber. So, figure out what you like, and how you can apply it to your role. Stay up to date A lot of the Staff Engineers interviewed seem to all have different resources that they learned from but some popular methods are following leaders in tech on Twitter and reading books. Some names mentioned for Twitter and personal blogs were Camille Fournier, Lara Hogan, David Fowler, Tanya Reilly. Some books mentioned include Radical Candor, , 7 Habits of Highly Effective People. Depending on the type of material you like to consume; social media, books, podcasts, Youtube videos….there’s ways to stay up-to-date in the medium that you want. Spend a little time figuring out what works for you! Fundamentals of Software Architecture Develop more context A theme that constantly came up was about how the higher up the ladder you go, the more distanced you become from the problems on the ground. Some of the ways that the leaders in the book described developing context to make decisions was paying attention to slack channels where bugs were posted, continuing to attend team standups, being assigned low priority tickets so they could still code, and finally having chats with engineers talking about what they’re working on, what problems they’re facing and what their ideal solutions would be. For engineers who aren’t managing people, its never too early to cultivate the habit of putting feelers out to know what’s going on around you. It's easy to get caught up in your day-to-day work bubble and the immediate concerns of your own projects. If you have the bandwidth, I’d say its never too early to start practicing the skills you need, like developing context, as you transition to more senior software engineering roles. “We are what we repeatedly do. Excellence, then, is not an act, but a habit.” — Will Durant

9 Lessons for Engineers of All Levels from 'Staff Engineer' by Will Larson 

How to Deploy Mancala With Minikube - A Beginner's guide

How to Write User Stories for Beginners Introduction Over my time as a Software Engineer, I’ve seen many ways people plan software projects. One method that keeps popping up is writing user stories as part of the scrum agile project methodology. They’re short descriptions of what a user wants to do, and they help everyone understand the goal. User story fit into the larger scrum system of scrum events. What Are User Stories? A user story is a small note that describes the user, what they need, and why they need it. For instance, if you’re building a sign-up page, you might say, “As a new visitor, I want to create an account so I can see my profile.” As a [type of user]: Identifies the user (visitor, admin, etc.). I want [action]: Describes what they want to do. So [goal]: Explains why.
These stories work well because they show the team the purpose behind each task. Why Do They Matter? Clarity for Everyone: Developers, testers, and product owners see the exact thing the user wants. No confusion. Simpler Prioritization: You can rank which user stories are more important for your product. Better Planning: Sprints and tasks become easier to estimate. You can also spot issues early. For example, if you have a fintech app, a story might be: “As a customer, I want to link my bank account so I can view my balance.” This one-liner tells your team what to build first. Key Elements of a Good User Story Simple Language: Keep the story short. Avoid stuffing too many details into it.


One Goal: If you need more than one goal, break the story into smaller parts.


Clear Reason: State why the user wants this. It helps the team see the bigger picture. Writing Acceptance Criteria Acceptance criteria are a checklist to confirm the story is done. For instance: “After sign-up, the user gets a welcome email.”
“The user can log in with the email and password they used.” These rules guide your developers and testers. In addition, they help confirm that everything works as expected. My Experience With User Stories I’ve worked with many teams that switched to agile and started using user stories. At first, they wrote huge, detailed stories. That is often confusing. Eventually, we learned to keep them short and test them right away. On the other hand, skipping acceptance criteria entirely led to guesswork, and we had to redo much work later. Through trial and error, we saw that a lean, clear user story works best. Also, involving the right people—developers, product owners, and QA—during story creation reduces last-minute surprises. Common Pitfalls Vague Descriptions: “As a user, I want to do stuff so I can do more stuff.” That’s too unclear.
Too Much Detail": Writing an entire manual in the story bogs everyone down.
No Acceptance Criteria: You’ll spend extra time debating if the story is done or not. Conclusion User stories keep things focused on user needs. Furthermore, they let you plan features in smaller steps. In short, a clear user story shows who wants something, what they want, and why. Add acceptance criteria, and you have a solid way to confirm the final product. I hope this helps you start writing your own user stories. They’ve helped me—and my teams—deliver more user-friendly features. Try them out, and see if they simplify your next project! Thanks for reading! Feel free to reach me at Just Another Tech Lead or on my channels (X and YouTube). How to Write User Stories for Beginners Introduction Over my time as a Software Engineer, I’ve seen many ways people plan software projects. One method that keeps popping up is writing user stories as part of the scrum agile project methodology. They’re short descriptions of what a user wants to do, and they help everyone understand the goal. scrum agile User story fit into the larger scrum system of scrum events . scrum events What Are User Stories? A user story is a small note that describes the user, what they need, and why they need it. For instance, if you’re building a sign-up page, you might say, “As a new visitor, I want to create an account so I can see my profile.” As a [type of user]: Identifies the user (visitor, admin, etc.). As a [type of user] : Identifies the user (visitor, admin, etc.). As a [type of user] I want [action]: Describes what they want to do. I want [action] : Describes what they want to do. I want [action] So [goal]: Explains why.
These stories work well because they show the team the purpose behind each task. So [goal]: Explains why. These stories work well because they show the team the purpose behind each task. So [goal] : Explains why. So [goal] These stories work well because they show the team the purpose behind each task. Why Do They Matter? Clarity for Everyone: Developers, testers, and product owners see the exact thing the user wants. No confusion. Clarity for Everyone : Developers, testers, and product owners see the exact thing the user wants. No confusion. Clarity for Everyone Simpler Prioritization: You can rank which user stories are more important for your product. Simpler Prioritization : You can rank which user stories are more important for your product. Simpler Prioritization Better Planning: Sprints and tasks become easier to estimate. You can also spot issues early. Better Planning: Sprints and tasks become easier to estimate. You can also spot issues early. Better Planning : Sprints and tasks become easier to estimate. You can also spot issues early. Better Planning For example, if you have a fintech app, a story might be: “As a customer, I want to link my bank account so I can view my balance.” This one-liner tells your team what to build first. Key Elements of a Good User Story Simple Language: Keep the story short. Avoid stuffing too many details into it. One Goal: If you need more than one goal, break the story into smaller parts. Clear Reason: State why the user wants this. It helps the team see the bigger picture. Simple Language: Keep the story short. Avoid stuffing too many details into it. Simple Language: Keep the story short. Avoid stuffing too many details into it. Simple Language: One Goal: If you need more than one goal, break the story into smaller parts. One Goal: If you need more than one goal, break the story into smaller parts. One Goal: Clear Reason: State why the user wants this. It helps the team see the bigger picture. Clear Reason: State why the user wants this. It helps the team see the bigger picture. Clear Reason: Writing Acceptance Criteria Acceptance criteria are a checklist to confirm the story is done. For instance: “After sign-up, the user gets a welcome email.” “The user can log in with the email and password they used.” “After sign-up, the user gets a welcome email.” “The user can log in with the email and password they used.” These rules guide your developers and testers. In addition, they help confirm that everything works as expected. My Experience With User Stories I’ve worked with many teams that switched to agile and started using user stories. At first, they wrote huge, detailed stories. That is often confusing. Eventually, we learned to keep them short and test them right away. On the other hand, skipping acceptance criteria entirely led to guesswork, and we had to redo much work later. Through trial and error, we saw that a lean, clear user story works best. Also, involving the right people—developers, product owners, and QA—during story creation reduces last-minute surprises. Common Pitfalls Vague Descriptions: “As a user, I want to do stuff so I can do more stuff.” That’s too unclear. Too Much Detail": Writing an entire manual in the story bogs everyone down. No Acceptance Criteria: You’ll spend extra time debating if the story is done or not. Vague Descriptions: “As a user, I want to do stuff so I can do more stuff.” That’s too unclear. Vague Descriptions: Too Much Detail": Writing an entire manual in the story bogs everyone down. Too Much Detail": No Acceptance Criteria: You’ll spend extra time debating if the story is done or not. No Acceptance Criteria: Conclusion User stories keep things focused on user needs. Furthermore, they let you plan features in smaller steps. In short, a clear user story shows who wants something, what they want, and why. Add acceptance criteria, and you have a solid way to confirm the final product. I hope this helps you start writing your own user stories. They’ve helped me—and my teams—deliver more user-friendly features. Try them out, and see if they simplify your next project! Thanks for reading! Thanks for reading! Feel free to reach me at Just Another Tech Lead or on my channels ( X and YouTube ). Just Another Tech Lead X YouTube

Agile: How to Write User Stories for Beginners

Building software can be complex. You might not have to think much about it when building your side project, but production software differs. It can require multiple components, all of which if not handled correctly can lead to chaos. But it doesn't need to be this complex. In today's article we will be delving into the world of architectural patterns, and discuss some divides your software into 3 simple components, each focusing on related tasks. Architectural patterns Whenever we are talking about architectural patterns in software design, the first ones to top the list include architectures like client-server, layered, monolithic, microkernel, even-driven, etc. These patterns are concerned with overall system architecture, including multiple applications, services, servers, etc. However, MVP, MVC, and MVVM focus on organizing code within a single application by separating data, user interface, and logic. These are a subset of architecture patterns that focus on the overall system. MVC, MVP, and MVVM For the sake of keeping the blog readable and not exceeding the word length, we will focus on just the architectural patterns that organize the code within a single application, namely: Model-View-Controller
Model-View-Presenter
Model-View-ViewModel Clearly, all three models have two components fixed, i.e. the Model and the View. So let's first discuss them in detail before coming to each of the architecture. Model The model consists of all the code that is related to data present in the software. It's the layer for communication of the database and network layers with the rest of the application. Its main responsibilities include: Handle data and business logic.


Encapsulate the application's data and the rules governing access to that data.


Handling data structures.


Performing CRUD (Create, Read, Update, and Delete) operations on data. View View is pretty much the front end of your application or everything that the user will be able to see and interact with. It's also known as the User Interface (UI) of your application. Its responsibilities include: Handle non-business logic and purely presentational logic.


Present the data provided by other layers to the user.


Receive user input and forward it to other layers.


May or may communicate directly with the Model layer. Model-View-Controller (MVC) Architecture Now that we have an understanding of what Model and View layers do, let's take a look at individual architectural patterns. Starting with MVC, it uses a Controller layer that communicates with both the Model and View layers. It's main responsibilities of the controller include: Manipulating data through the Model layer.
Receive instructions, aka the UI, from the View layer.
Update the View with changes defined due to control logic. Here, although the View layer cannot directly interact with the Model layer, it can however receive updates based on changes in the data. Hence all three layers are connected to each other in some form, with the controller being the main component. Model-View-Presenter (MVP) Architecture Here, the Presenter layer assumes the functionality of the "middle-man" between the Model and View layers and handles all the communication between them. There is no communication at all between the Model and View layers directly. Its responsibilities include: Update the UI or the View layer based on user actions.


Update the data or Model layer based on code logic.


Handle much of the business logic that would be otherwise handled in the controller in MVC architecture. Model-View-ViewModel (MVVM) Architecture This architecture at first glance is almost identical to MVP architecture. But there are some key differences between them: Multiple views can be mapped to a single ViewModel layer.


It uses data binding between the ViewModel layer and the View layer, making it more event-driven.


There is no concept of User Interface in this architecture. The View layer represents the actions of the user, not the interface. Side by Side comparison Aspect

MVC

MVP

MVVM



Full Name

Model-View-Controller

Model-View-Presenter

Model-View-ViewModel



Separation of Concerns

Basic

Better

Best



Data Flow

Two-way

One-way

One-way with data binding



View-Logic Relationship

Many-to-one

One-to-one

Many-to-one



Testability

Hard

Good

Best



Maintenance

Hard

Easy

Easy



Learning Curve

Easy

Easy

Harder



Performance

Can be slower due to tight coupling

Better performance with looser coupling

Smooth performance, especially for complex UIs



UI Updates

Controller updates View

Presenter updates View

ViewModel updates View through data binding



Dependency on UI Framework

High

Low

Low or no dependency



Scalability

Suitable for small-scale projects

Good for simple and complex projects

Ideal for large, data-heavy apps But which is the most popular you might ask? All of them are equally popular architectures being used according to the company's respective requirements for a product. Some companies adopting these different architectures are: MVC: StackOverflow, GoDaddy, Visual Studio website Dell
MVP: Google (for some Android apps)
MVVM: Apple (for some iOS apps using SwiftUI), Angular framework, Vue.js framework Also, many companies use a mix of these architectures depending on the specific needs of each project or product. The choice of architecture often depends on factors such as the complexity of the application, the development team's expertise, and the specific requirements of the project. Conclusion This article covered the basics of architectural patterns, from how overall architecture is designed to how a single application can be further divided into three components for better management and scalability. MVC, with its straightforward approach, remains popular for web applications.
MVP builds upon MVC's foundation, offering improved testability and a cleaner separation of concerns.
MVVM, the most recent of the three, has gained significant traction in modern application development. There is no clear winner between them and each pattern offers unique advantages and is suited to different projects and development scenarios. As the software development landscape continues to evolve, we may see further refinements of these patterns or the emergence of new architectures altogether. Want to learn more about the architectural patterns discussed? Here are some references I found helpful:

https://www.geeksforgeeks.org/android-architecture-patterns/
https://www.masaischool.com/blog/comparing-software-architecture-patterns/
https://www.apptension.com/blog-posts/mvc-vs-mvvm-vs-mvp Building software can be complex. You might not have to think much about it when building your side project, but production software differs. It can require multiple components, all of which if not handled correctly can lead to chaos. But it doesn't need to be this complex. In today's article we will be delving into the world of architectural patterns, and discuss some divides your software into 3 simple components, each focusing on related tasks. Architectural patterns Whenever we are talking about architectural patterns in software design, the first ones to top the list include architectures like client-server, layered, monolithic, microkernel, even-driven, etc. These patterns are concerned with overall system architecture, including multiple applications, services, servers, etc. However, MVP, MVC, and MVVM focus on organizing code within a single application by separating data, user interface, and logic. These are a subset of architecture patterns that focus on the overall system. MVC, MVP, and MVVM For the sake of keeping the blog readable and not exceeding the word length, we will focus on just the architectural patterns that organize the code within a single application, namely: Model-View-Controller Model-View-Presenter Model-View-ViewModel Model-View-Controller Model-View-Presenter Model-View-ViewModel Clearly, all three models have two components fixed, i.e. the Model and the View. So let's first discuss them in detail before coming to each of the architecture. Model The model consists of all the code that is related to data present in the software. It's the layer for communication of the database and network layers with the rest of the application. Its main responsibilities include: data Handle data and business logic. Encapsulate the application's data and the rules governing access to that data. Handling data structures. Performing CRUD (Create, Read, Update, and Delete) operations on data. Handle data and business logic. Handle data and business logic. Encapsulate the application's data and the rules governing access to that data. Encapsulate the application's data and the rules governing access to that data. Handling data structures. Handling data structures. Performing CRUD (Create, Read, Update, and Delete) operations on data. Performing CRUD (Create, Read, Update, and Delete) operations on data. View View is pretty much the front end of your application or everything that the user will be able to see and interact with. It's also known as the User Interface (UI) of your application. Its responsibilities include: Handle non-business logic and purely presentational logic. Present the data provided by other layers to the user. Receive user input and forward it to other layers. May or may communicate directly with the Model layer. Handle non-business logic and purely presentational logic. Handle non-business logic and purely presentational logic. Present the data provided by other layers to the user. Present the data provided by other layers to the user. Receive user input and forward it to other layers. Receive user input and forward it to other layers. May or may communicate directly with the Model layer. May or may communicate directly with the Model layer. Model-View-Controller (MVC) Architecture Now that we have an understanding of what Model and View layers do, let's take a look at individual architectural patterns. Starting with MVC, it uses a Controller layer that communicates with both the Model and View layers. Controller It's main responsibilities of the controller include: Manipulating data through the Model layer. Receive instructions, aka the UI, from the View layer. Update the View with changes defined due to control logic. Manipulating data through the Model layer. Receive instructions, aka the UI, from the View layer. Update the View with changes defined due to control logic. Here, although the View layer cannot directly interact with the Model layer, it can however receive updates based on changes in the data. Hence all three layers are connected to each other in some form, with the controller being the main component. Model-View-Presenter (MVP) Architecture Here, the Presenter layer assumes the functionality of the "middle-man" between the Model and View layers and handles all the communication between them. There is no communication at all between the Model and View layers directly. Its responsibilities include: Update the UI or the View layer based on user actions. Update the data or Model layer based on code logic. Handle much of the business logic that would be otherwise handled in the controller in MVC architecture. Update the UI or the View layer based on user actions. Update the UI or the View layer based on user actions. Update the data or Model layer based on code logic. Update the data or Model layer based on code logic. Handle much of the business logic that would be otherwise handled in the controller in MVC architecture. Handle much of the business logic that would be otherwise handled in the controller in MVC architecture. Model-View-ViewModel (MVVM) Architecture This architecture at first glance is almost identical to MVP architecture. But there are some key differences between them: Multiple views can be mapped to a single ViewModel layer. It uses data binding between the ViewModel layer and the View layer, making it more event-driven. There is no concept of User Interface in this architecture. The View layer represents the actions of the user, not the interface. Multiple views can be mapped to a single ViewModel layer. Multiple views can be mapped to a single ViewModel layer. It uses data binding between the ViewModel layer and the View layer, making it more event-driven. It uses data binding between the ViewModel layer and the View layer, making it more event-driven. There is no concept of User Interface in this architecture. The View layer represents the actions of the user, not the interface. There is no concept of User Interface in this architecture. The View layer represents the actions of the user, not the interface. Side by Side comparison Aspect

MVC

MVP

MVVM



Full Name

Model-View-Controller

Model-View-Presenter

Model-View-ViewModel



Separation of Concerns

Basic

Better

Best



Data Flow

Two-way

One-way

One-way with data binding



View-Logic Relationship

Many-to-one

One-to-one

Many-to-one



Testability

Hard

Good

Best



Maintenance

Hard

Easy

Easy



Learning Curve

Easy

Easy

Harder



Performance

Can be slower due to tight coupling

Better performance with looser coupling

Smooth performance, especially for complex UIs



UI Updates

Controller updates View

Presenter updates View

ViewModel updates View through data binding



Dependency on UI Framework

High

Low

Low or no dependency



Scalability

Suitable for small-scale projects

Good for simple and complex projects

Ideal for large, data-heavy apps Aspect

MVC

MVP

MVVM Full Name

Model-View-Controller

Model-View-Presenter

Model-View-ViewModel Separation of Concerns

Basic

Better

Best Data Flow

Two-way

One-way

One-way with data binding View-Logic Relationship

Many-to-one

One-to-one

Many-to-one Testability

Hard

Good

Best Maintenance

Hard

Easy

Easy Learning Curve

Easy

Easy

Harder Performance

Can be slower due to tight coupling

Better performance with looser coupling

Smooth performance, especially for complex UIs UI Updates

Controller updates View

Presenter updates View

ViewModel updates View through data binding Dependency on UI Framework

High

Low

Low or no dependency Scalability

Suitable for small-scale projects

Good for simple and complex projects

Ideal for large, data-heavy apps Aspect MVC MVP MVVM Aspect Aspect MVC MVC MVP MVP MVVM MVVM Full Name Model-View-Controller Model-View-Presenter Model-View-ViewModel Full Name Full Name Model-View-Controller Model-View-Controller Model-View-Presenter Model-View-Presenter Model-View-ViewModel Model-View-ViewModel Separation of Concerns Basic Better Best Separation of Concerns Separation of Concerns Basic Basic Better Better Best Best Data Flow Two-way One-way One-way with data binding Data Flow Data Flow Two-way Two-way One-way One-way One-way with data binding One-way with data binding View-Logic Relationship Many-to-one One-to-one Many-to-one View-Logic Relationship View-Logic Relationship Many-to-one Many-to-one One-to-one One-to-one Many-to-one Many-to-one Testability Hard Good Best Testability Testability Hard Hard Good Good Best Best Maintenance Hard Easy Easy Maintenance Maintenance Hard Hard Easy Easy Easy Easy Learning Curve Easy Easy Harder Learning Curve Learning Curve Easy Easy Easy Easy Harder Harder Performance Can be slower due to tight coupling Better performance with looser coupling Smooth performance, especially for complex UIs Performance Performance Can be slower due to tight coupling Can be slower due to tight coupling Better performance with looser coupling Better performance with looser coupling Smooth performance, especially for complex UIs Smooth performance, especially for complex UIs UI Updates Controller updates View Presenter updates View ViewModel updates View through data binding UI Updates UI Updates Controller updates View Controller updates View Presenter updates View Presenter updates View ViewModel updates View through data binding ViewModel updates View through data binding Dependency on UI Framework High Low Low or no dependency Dependency on UI Framework Dependency on UI Framework High High Low Low Low or no dependency Low or no dependency Scalability Suitable for small-scale projects Good for simple and complex projects Ideal for large, data-heavy apps Scalability Scalability Suitable for small-scale projects Suitable for small-scale projects Good for simple and complex projects Good for simple and complex projects Ideal for large, data-heavy apps Ideal for large, data-heavy apps But which is the most popular you might ask? All of them are equally popular architectures being used according to the company's respective requirements for a product. Some companies adopting these different architectures are: MVC: StackOverflow, GoDaddy, Visual Studio website Dell MVP: Google (for some Android apps) MVVM: Apple (for some iOS apps using SwiftUI), Angular framework, Vue.js framework MVC: StackOverflow, GoDaddy, Visual Studio website Dell MVP: Google (for some Android apps) MVVM: Apple (for some iOS apps using SwiftUI), Angular framework, Vue.js framework Also, many companies use a mix of these architectures depending on the specific needs of each project or product. The choice of architecture often depends on factors such as the complexity of the application, the development team's expertise, and the specific requirements of the project. Conclusion This article covered the basics of architectural patterns, from how overall architecture is designed to how a single application can be further divided into three components for better management and scalability. MVC, with its straightforward approach, remains popular for web applications. MVP builds upon MVC's foundation, offering improved testability and a cleaner separation of concerns. MVVM, the most recent of the three, has gained significant traction in modern application development. MVC, with its straightforward approach, remains popular for web applications. MVP builds upon MVC's foundation, offering improved testability and a cleaner separation of concerns. MVVM, the most recent of the three, has gained significant traction in modern application development. There is no clear winner between them and each pattern offers unique advantages and is suited to different projects and development scenarios. As the software development landscape continues to evolve, we may see further refinements of these patterns or the emergence of new architectures altogether. Want to learn more about the architectural patterns discussed? Here are some references I found helpful: https://www.geeksforgeeks.org/android-architecture-patterns/
https://www.masaischool.com/blog/comparing-software-architecture-patterns/
https://www.apptension.com/blog-posts/mvc-vs-mvvm-vs-mvp Want to learn more about the architectural patterns discussed? Here are some references I found helpful: https://www.geeksforgeeks.org/android-architecture-patterns/ https://www.masaischool.com/blog/comparing-software-architecture-patterns/ https://www.apptension.com/blog-posts/mvc-vs-mvvm-vs-mvp https://www.geeksforgeeks.org/android-architecture-patterns/ https://www.geeksforgeeks.org/android-architecture-patterns/ https://www.masaischool.com/blog/comparing-software-architecture-patterns/ https://www.masaischool.com/blog/comparing-software-architecture-patterns/ https://www.apptension.com/blog-posts/mvc-vs-mvvm-vs-mvp https://www.apptension.com/blog-posts/mvc-vs-mvvm-vs-mvp

Architecture Patterns for Beginners: MVC, MVP, and MVVM

Understanding Parallel Programming: Thread Management for Beginners

Set Up Your First Machine Learning Pipeline With This Beginner’s Guide 

Author:
(1) David Staines. Table of Links Abstract 1 Introduction 2 Mathematical Arguments 3 Outline and Preview 4 Calvo Framework and 4.1 Household’s Problem 4.2 Preferences 4.3 Household Equilibrium Conditions 4.4 Price-Setting Problem 4.5 Nominal Equilibrium Conditions 4.6 Real Equilibrium Conditions and 4.7 Shocks 4.8 Recursive Equilibrium 5 Existing Solutions 5.1 Singular Phillips Curve 5.2 Persistence and Policy Puzzles 5.3 Two Comparison Models 5.4 Lucas Critique 6 Stochastic Equilibrium and 6.1 Ergodic Theory and Random Dynamical Systems 6.2 Equilibrium Construction 6.3 Literature Comparison 6.4 Equilibrium Analysis 7 General Linearized Phillips Curve 7.1 Slope Coefficients 7.2 Error Coefficients 8 Existence Results and 8.1 Main Results 8.2 Key Proofs 8.3 Discussion 9 Bifurcation Analysis 9.1 Analytic Aspects 9.2 Algebraic Aspects (I) Singularities and Covers 9.3 Algebraic Aspects (II) Homology 9.4 Algebraic Aspects (III) Schemes 9.5 Wider Economic Interpretations 10 Econometric and Theoretical Implications and 10.1 Identification and Trade-offs 10.2 Econometric Duality 10.3 Coefficient Properties 10.4 Microeconomic Interpretation 11 Policy Rule 12 Conclusions and References Appendices A Proof of Theorem 2 and A.1 Proof of Part (i) A.2 Behaviour of ∆ A.3 Proof Part (iii) B Proofs from Section 4 and B.1 Individual Product Demand (4.2) B.2 Flexible Price Equilibrium and ZINSS (4.4) B.3 Price Dispersion (4.5) B.4 Cost Minimization (4.6) and (10.4) B.5 Consolidation (4.8) C Proofs from Section 5, and C.1 Puzzles, Policy and Persistence C.2 Extending No Persistence D Stochastic Equilibrium and D.1 Non-Stochastic Equilibrium D.2 Profits and Long-Run Growth E Slopes and Eigenvalues and E.1 Slope Coefficients E.2 Linearized DSGE Solution E.3 Eigenvalue Conditions E.4 Rouche’s Theorem Conditions F Abstract Algebra and F.1 Homology Groups F.2 Basic Categories F.3 De Rham Cohomology F.4 Marginal Costs and Inflation G Further Keynesian Models and G.1 Taylor Pricing G.2 Calvo Wage Phillips Curve G.3 Unconventional Policy Settings H Empirical Robustness and H.1 Parameter Selection H.2 Phillips Curve I Additional Evidence and I.1 Other Structural Parameters I.2 Lucas Critique I.3 Trend Inflation Volatility F Abstract Algebra This section supplies an introductory primer on homological algebra, De Rham cohomology and category theory, complimentary to the informal discussion in the text. Each occupies a subsection. At the end, a short part is devoted to additional details of a calculation from Proposition 20, which applies the methods here to the ultimate goal of the paper. F.1 Homology Groups This part develops the theory of singular homology to support the claims and analysis in the main text. Other popular homology constructions are discussed in Jacobson [1980]. Informally, the singular homology is built by a succession of mappings between n dimensional blocks and the paths around their boundaries. F.1.1 Singular Simplex its vertices are the k standard unit vectors and the origin. [112] Familiar examples include: F.1.2 Singular Chain Complex F.1.3 Homotopy Invariance for all n ≥ 0. This means that homology groups are topologically invariants. In particular, if X is a connected contractible space, then all its homology groups are 0 except I finish with a sketch of the proof of homotopy invariance of singular homology. A continuous map f : X → Y induces a homomorphism It is easy to see that where f♯ is a chain map which descends to homomorphisms on homology It is left to show that, if f and g are homotopically equivalent, then f∗ = g∗. This implies that if f is a homotopy equivalence then f∗ is an isomorphism. Let F : X × [0, 1] → Y be a homotopy, that takes f to g on the level of chains. It defines a homomorphism Therefore, they are homologous, which settles the claim. This paper is available on arxiv under CC 4.0 license. Author: (1) David Staines. Author: Author: (1) David Staines. Table of Links Abstract Abstract 1 Introduction 1 Introduction 2 Mathematical Arguments 2 Mathematical Arguments 3 Outline and Preview 3 Outline and Preview 4 Calvo Framework and 4.1 Household’s Problem 4 Calvo Framework and 4.1 Household’s Problem 4.2 Preferences 4.2 Preferences 4.3 Household Equilibrium Conditions 4.3 Household Equilibrium Conditions 4.4 Price-Setting Problem 4.4 Price-Setting Problem 4.5 Nominal Equilibrium Conditions 4.5 Nominal Equilibrium Conditions 4.6 Real Equilibrium Conditions and 4.7 Shocks 4.6 Real Equilibrium Conditions and 4.7 Shocks 4.8 Recursive Equilibrium 4.8 Recursive Equilibrium 5 Existing Solutions 5 Existing Solutions 5.1 Singular Phillips Curve 5.1 Singular Phillips Curve 5.2 Persistence and Policy Puzzles 5.2 Persistence and Policy Puzzles 5.3 Two Comparison Models 5.3 Two Comparison Models 5.4 Lucas Critique 5.4 Lucas Critique 6 Stochastic Equilibrium and 6.1 Ergodic Theory and Random Dynamical Systems 6 Stochastic Equilibrium and 6.1 Ergodic Theory and Random Dynamical Systems 6.2 Equilibrium Construction 6.2 Equilibrium Construction 6.3 Literature Comparison 6.3 Literature Comparison 6.4 Equilibrium Analysis 6.4 Equilibrium Analysis 7 General Linearized Phillips Curve 7 General Linearized Phillips Curve 7.1 Slope Coefficients 7.1 Slope Coefficients 7.2 Error Coefficients 7.2 Error Coefficients 8 Existence Results and 8.1 Main Results 8 Existence Results and 8.1 Main Results 8.2 Key Proofs 8.2 Key Proofs 8.3 Discussion 8.3 Discussion 9 Bifurcation Analysis 9 Bifurcation Analysis 9.1 Analytic Aspects 9.1 Analytic Aspects 9.2 Algebraic Aspects (I) Singularities and Covers 9.2 Algebraic Aspects (I) Singularities and Covers 9.3 Algebraic Aspects (II) Homology 9.3 Algebraic Aspects (II) Homology 9.4 Algebraic Aspects (III) Schemes 9.4 Algebraic Aspects (III) Schemes 9.5 Wider Economic Interpretations 9.5 Wider Economic Interpretations 10 Econometric and Theoretical Implications and 10.1 Identification and Trade-offs 10 Econometric and Theoretical Implications and 10.1 Identification and Trade-offs 10.2 Econometric Duality 10.2 Econometric Duality 10.3 Coefficient Properties 10.3 Coefficient Properties 10.4 Microeconomic Interpretation 10.4 Microeconomic Interpretation 11 Policy Rule 11 Policy Rule 12 Conclusions and References 12 Conclusions and References Appendices Appendices A Proof of Theorem 2 and A.1 Proof of Part (i) A Proof of Theorem 2 and A.1 Proof of Part (i) A.2 Behaviour of ∆ A.2 Behaviour of ∆ A.3 Proof Part (iii) A.3 Proof Part (iii) B Proofs from Section 4 and B.1 Individual Product Demand (4.2) B Proofs from Section 4 and B.1 Individual Product Demand (4.2) B.2 Flexible Price Equilibrium and ZINSS (4.4) B.2 Flexible Price Equilibrium and ZINSS (4.4) B.3 Price Dispersion (4.5) B.3 Price Dispersion (4.5) B.4 Cost Minimization (4.6) and (10.4) B.4 Cost Minimization (4.6) and (10.4) B.5 Consolidation (4.8) B.5 Consolidation (4.8) C Proofs from Section 5, and C.1 Puzzles, Policy and Persistence C Proofs from Section 5, and C.1 Puzzles, Policy and Persistence C.2 Extending No Persistence C.2 Extending No Persistence D Stochastic Equilibrium and D.1 Non-Stochastic Equilibrium D Stochastic Equilibrium and D.1 Non-Stochastic Equilibrium D.2 Profits and Long-Run Growth D.2 Profits and Long-Run Growth E Slopes and Eigenvalues and E.1 Slope Coefficients E Slopes and Eigenvalues and E.1 Slope Coefficients E.2 Linearized DSGE Solution E.2 Linearized DSGE Solution E.3 Eigenvalue Conditions E.3 Eigenvalue Conditions E.4 Rouche’s Theorem Conditions E.4 Rouche’s Theorem Conditions F Abstract Algebra and F.1 Homology Groups F Abstract Algebra and F.1 Homology Groups F.2 Basic Categories F.2 Basic Categories F.3 De Rham Cohomology F.3 De Rham Cohomology F.4 Marginal Costs and Inflation F.4 Marginal Costs and Inflation G Further Keynesian Models and G.1 Taylor Pricing G Further Keynesian Models and G.1 Taylor Pricing G.2 Calvo Wage Phillips Curve G.2 Calvo Wage Phillips Curve G.3 Unconventional Policy Settings G.3 Unconventional Policy Settings H Empirical Robustness and H.1 Parameter Selection H Empirical Robustness and H.1 Parameter Selection H.2 Phillips Curve H.2 Phillips Curve I Additional Evidence and I.1 Other Structural Parameters I Additional Evidence and I.1 Other Structural Parameters I.2 Lucas Critique I.2 Lucas Critique I.3 Trend Inflation Volatility I.3 Trend Inflation Volatility F Abstract Algebra This section supplies an introductory primer on homological algebra, De Rham cohomology and category theory, complimentary to the informal discussion in the text. Each occupies a subsection. At the end, a short part is devoted to additional details of a calculation from Proposition 20, which applies the methods here to the ultimate goal of the paper. F.1 Homology Groups This part develops the theory of singular homology to support the claims and analysis in the main text. Other popular homology constructions are discussed in Jacobson [1980]. Informally, the singular homology is built by a succession of mappings between n dimensional blocks and the paths around their boundaries. F.1.1 Singular Simplex F.1.1 Singular Simplex its vertices are the k standard unit vectors and the origin. [112] Familiar examples include: F.1.2 Singular Chain Complex F.1.2 Singular Chain Complex F.1.3 Homotopy Invariance F.1.3 Homotopy Invariance for all n ≥ 0. This means that homology groups are topologically invariants. In particular, if X is a connected contractible space, then all its homology groups are 0 except I finish with a sketch of the proof of homotopy invariance of singular homology. A continuous map f : X → Y induces a homomorphism It is easy to see that where f♯ is a chain map which descends to homomorphisms on homology It is left to show that, if f and g are homotopically equivalent, then f∗ = g∗. This implies that if f is a homotopy equivalence then f∗ is an isomorphism. Let F : X × [0, 1] → Y be a homotopy, that takes f to g on the level of chains. It defines a homomorphism Therefore, they are homologous, which settles the claim. This paper is available on arxiv under CC 4.0 license. This paper is available on arxiv under CC 4.0 license. available on arxiv

A Beginner's Guide to Homology

Most of us have interacted with large language models (LLMs) like GPT-4, and they have been impressive. However, you might have wondered: What if I want to give my personal data or a lengthy document to an AI and extract specific information from it? In this blog post, we’ll explore: Problems with traditional LLMs
What is Retrieval-Augmented Generation (RAG)?
How RAG works
Real-world implementations of RAG https://youtu.be/zW1ELMo7D5A?embedable=true Problems With Traditional LLMs While LLMs have revolutionized the way we interact with technology, they come with some significant limitations: Hallucination: LLMs sometimes hallucinate, meaning they provide factually incorrect answers. This occurs because they generate responses based on patterns in the data they were trained on, not always on verified facts. Example: An AI might state that a historical event occurred in a year when it didn’t. Outdated Knowledge: Models like GPT-4 have a knowledge cutoff date (e.g., May 2024). They lack information on events or developments that occurred after this date. Implication: The AI cannot provide insights on recent advancements, news, or data. Untraceable Reasoning: LLMs often provide answers without clear sources, leading to untraceable reasoning. Transparency: Users don’t know where the information came from. Bias: The training data may contain biases, affecting the output. Accountability: Difficult to verify the accuracy of the response. Lack of Domain-Specific Expertise: While LLMs are good at generating general responses, they often lack domain-specific expertise.


Outcome: Answers may be generic and not delve deep into specialized topics. What Is RAG? Imagine RAG as your personal assistant who can memorize thousands of pages of documents. You can later query this assistant to extract any information you need. RAG stands for Retrieval-Augmented Generation, where: Retrieval: Fetches information from a database. Augmentation: Combines the retrieved information with the user’s prompt. Generation: Produces the final answer using an LLM. How RAG Works The Traditional Method vs. RAG Traditional LLM Approach: A user asks a question. The LLM generates an answer based solely on its trained knowledge base. If the question is outside its knowledge base, it may provide incorrect or generic answers. RAG Approach: Document Ingestion: A document is broken down into smaller chunks. These chunks are converted into embeddings (vector representations). The embeddings are indexed and stored in a vector database. 2. Query Processing: The user asks a question. The question is converted into an embedding using the same model. A search engine queries the vector database to find the most relevant chunks. The top relevant results are retrieved. 3. Answer Generation: The retrieved information and the user’s question are combined. This combined input is passed to the LLM (like GPT-4 or LLaMA). The LLM generates a context-aware answer. The answer is returned to the user. Real-World Implementations of RAG General knowledge Retrieval: Input extensive documents (hundreds or thousands of pages). Efficiently extract specific information when needed. Customer Support: RAG-powered chatbots can access real-time customer data. Provide accurate and personalized responses in sectors like finance, banking, or telecom. Improved first-response rates lead to higher customer satisfaction and loyalty. Legal Sector: Assist in contract analysis, e-discoveries, or regulatory compliances. Streamline legal research and document review processes. As Thomas Edison once said: “Vision without execution is hallucination.” In the context of AI: “LLMs without RAG are hallucination.” By integrating RAG, we can overcome many limitations of traditional LLMs, providing more accurate, up-to-date, and domain-specific answers. In upcoming posts, we’ll explore more advanced topics on RAG and how to obtain even more relevant responses from it. Stay tuned! Thank you for reading! Most of us have interacted with large language models (LLMs) like GPT-4, and they have been impressive. However, you might have wondered: What if I want to give my personal data or a lengthy document to an AI and extract specific information from it? What if I want to give my personal data or a lengthy document to an AI and extract specific information from it? In this blog post, we’ll explore: Problems with traditional LLMs What is Retrieval-Augmented Generation (RAG)? How RAG works Real-world implementations of RAG Problems with traditional LLMs What is Retrieval-Augmented Generation (RAG)? How RAG works Real-world implementations of RAG https://youtu.be/zW1ELMo7D5A?embedable=true https://youtu.be/zW1ELMo7D5A?embedable=true Problems With Traditional LLMs While LLMs have revolutionized the way we interact with technology, they come with some significant limitations: Hallucination: LLMs sometimes hallucinate, meaning they provide factually incorrect answers. This occurs because they generate responses based on patterns in the data they were trained on, not always on verified facts. Example: An AI might state that a historical event occurred in a year when it didn’t. Hallucination: LLMs sometimes hallucinate, meaning they provide factually incorrect answers. This occurs because they generate responses based on patterns in the data they were trained on, not always on verified facts. Example: An AI might state that a historical event occurred in a year when it didn’t. Hallucination: Outdated Knowledge: Models like GPT-4 have a knowledge cutoff date (e.g., May 2024). They lack information on events or developments that occurred after this date. Implication: The AI cannot provide insights on recent advancements, news, or data. Outdated Knowledge: Models like GPT-4 have a knowledge cutoff date (e.g., May 2024). They lack information on events or developments that occurred after this date. Implication : The AI cannot provide insights on recent advancements, news, or data. Outdated Knowledge: knowledge cutoff date Implication Untraceable Reasoning: LLMs often provide answers without clear sources, leading to untraceable reasoning. Transparency: Users don’t know where the information came from. Bias: The training data may contain biases, affecting the output. Accountability: Difficult to verify the accuracy of the response. Untraceable Reasoning: LLMs often provide answers without clear sources, leading to untraceable reasoning . Transparency : Users don’t know where the information came from. Bias : The training data may contain biases, affecting the output. Accountability : Difficult to verify the accuracy of the response. Untraceable Reasoning: untraceable reasoning Transparency Bias Accountability Lack of Domain-Specific Expertise: While LLMs are good at generating general responses, they often lack domain-specific expertise. Outcome: Answers may be generic and not delve deep into specialized topics. Lack of Domain-Specific Expertise: While LLMs are good at generating general responses, they often lack domain-specific expertise. Lack of Domain-Specific Expertise: While LLMs are good at generating general responses, they often lack domain-specific expertise . Lack of Domain-Specific Expertise: domain-specific expertise Outcome: Answers may be generic and not delve deep into specialized topics. Outcome : Answers may be generic and not delve deep into specialized topics. Outcome generic What Is RAG? Imagine RAG as your personal assistant who can memorize thousands of pages of documents. You can later query this assistant to extract any information you need. RAG stands for Retrieval-Augmented Generation , where: RAG stands for Retrieval-Augmented Generation Retrieval: Fetches information from a database. Retrieval : Fetches information from a database. Retrieval Augmentation: Combines the retrieved information with the user’s prompt. Augmentation : Combines the retrieved information with the user’s prompt. Augmentation Generation: Produces the final answer using an LLM. Generation : Produces the final answer using an LLM. Generation How RAG Works The Traditional Method vs. RAG Traditional LLM Approach: Traditional LLM Approach: A user asks a question. A user asks a question. The LLM generates an answer based solely on its trained knowledge base. The LLM generates an answer based solely on its trained knowledge base. If the question is outside its knowledge base, it may provide incorrect or generic answers. If the question is outside its knowledge base, it may provide incorrect or generic answers. RAG Approach: RAG Approach: Document Ingestion: Document Ingestion: Document Ingestion: A document is broken down into smaller chunks. A document is broken down into smaller chunks. These chunks are converted into embeddings (vector representations). These chunks are converted into embeddings (vector representations). The embeddings are indexed and stored in a vector database. The embeddings are indexed and stored in a vector database . vector database 2. Query Processing: 2. Query Processing: The user asks a question. The user asks a question. The question is converted into an embedding using the same model. The question is converted into an embedding using the same model. A search engine queries the vector database to find the most relevant chunks. A search engine queries the vector database to find the most relevant chunks. The top relevant results are retrieved. The top relevant results are retrieved. 3. Answer Generation: 3. Answer Generation: The retrieved information and the user’s question are combined. The retrieved information and the user’s question are combined. This combined input is passed to the LLM (like GPT-4 or LLaMA). This combined input is passed to the LLM (like GPT-4 or LLaMA). The LLM generates a context-aware answer. The LLM generates a context-aware answer. The answer is returned to the user. The answer is returned to the user. Real-World Implementations of RAG General knowledge Retrieval: General knowledge Retrieval: Input extensive documents (hundreds or thousands of pages). Input extensive documents (hundreds or thousands of pages). Efficiently extract specific information when needed. Efficiently extract specific information when needed. Customer Support: Customer Support: RAG-powered chatbots can access real-time customer data. RAG-powered chatbots can access real-time customer data. Provide accurate and personalized responses in sectors like finance, banking, or telecom. Provide accurate and personalized responses in sectors like finance, banking, or telecom. Improved first-response rates lead to higher customer satisfaction and loyalty. Improved first-response rates lead to higher customer satisfaction and loyalty. Legal Sector: Legal Sector: Assist in contract analysis, e-discoveries, or regulatory compliances. Assist in contract analysis, e-discoveries, or regulatory compliances. Streamline legal research and document review processes. Streamline legal research and document review processes. As Thomas Edison once said: “Vision without execution is hallucination.” “Vision without execution is hallucination.” “Vision without execution is hallucination.” “Vision without execution is hallucination.” In the context of AI: “LLMs without RAG are hallucination.” “LLMs without RAG are hallucination.” “LLMs without RAG are hallucination.” “LLMs without RAG are hallucination.” By integrating RAG, we can overcome many limitations of traditional LLMs, providing more accurate, up-to-date, and domain-specific answers. In upcoming posts, we’ll explore more advanced topics on RAG and how to obtain even more relevant responses from it. Stay tuned! In upcoming posts, we’ll explore more advanced topics on RAG and how to obtain even more relevant responses from it. Stay tuned! Thank you for reading!

RAG: An Introduction for Beginners

Playwright and Chrome Browser Testing in Heroku: A Beginner's Guide

Heroku ukan dramaturgo ukat Chrome Navegador ukan yant’awipa: Qalltirinakatakix mä guia

Heroku-da dramaturq və Chrome Brauzer Testi: Başlayanlar üçün Bələdçi

Testiranje dramaturga i Chrome pretraživača u Heroku: Vodič za početnike

Pruebas del navegador Chrome y Playwright en Heroku: una guía para principiantes

Tès otè ak navigatè Chrome nan Heroku: Gid pou yon debutan

Heroku での Playwright と Chrome ブラウザのテスト: 初心者向けガイド

Тестирање на драматург и на прелистувачот Chrome во Heroku: водич за почетници

Penulis drama dan Ujian Penyemak Imbas Chrome dalam Heroku: Panduan Pemula

Testimi i dramaturgut dhe i shfletuesit Chrome në Heroku: Një udhëzues fillestar

Jaribio la Playwright na Kivinjari cha Chrome katika Heroku: Mwongozo wa Wanaoanza

การทดสอบนักเขียนบทละครและเบราว์เซอร์ Chrome ใน Heroku: คู่มือสำหรับผู้เริ่มต้น

Dramaturg va Chrome brauzerini Heroku’da sinovdan o‘tkazish: yangi boshlanuvchilar uchun qo‘llanma

RunLoops impact on asynchronous tasks I am Boris Dobretsov, and some time ago I published my first article - Understanding Parallel Programming: A Guide for Beginners. https://hackernoon.com/understanding-parallel-programming-a-guide-for-beginners?embedable=true In that article, I introduced basic concepts such as "processes" and "threads" and explained in simple terms what a processor, operating system, process, and thread are. Today, we will elaborate further on RunLoops and their impact on asynchronous tasks. But first, let's refresh our knowledge of what a RunLoop is and what it is responsible for. A RunLoop helps asynchronous tasks run at the right time without blocking or interfering with the main thread. It functions as a cycle of event handling, used to schedule tasks and coordinate incoming events. Its purpose is to keep the thread active when there is work to do and put it to sleep when there is none. As we know from the previous article, there are several main types of architecture for code organization: Synchronous single-threaded


Asynchronous single-threaded


Synchronous multi-threaded


Asynchronous multi-threaded Some of these are simpler, while others are designed to run several tasks (competing tasks) at the same time, making the development process more efficient and multifunctional. The most commonly used architecture in iOS application development is the asynchronous multi-threaded model. It is important to understand how to interact with these models and what to do to prevent overloading. That is why in this article we are going to discuss RunLoops impact on asynchronous tasks. As we also know from the previous article, asynchronous tasks can be paused mid-execution and resumed later. But who decides when to put a task on hold and when to resume it? It’s actually the task itself that makes this decision. This is because asynchronous tasks consist of two parts: the first starts the task, and the second executes asynchronously in response to a specific event. The latter part is added to a source for the RunLoop and is checked on each loop iteration. If the specified event occurs, the task proceeds. A basic example of an asynchronous task is a timer. Let me share the code which which demonstrates this idea: Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print("tick")
} In the above example, you can see the code which starts a timer that runs every quarter of a second, outputting "tick" to the console. The first part of the asynchronous task is creating the timer, and the second part is passing the block to the scheduled Timer method. The task is single-threaded: both the timer setup and block execution happen in the same thread. However, it is asynchronous since the block doesn’t execute immediately but after a delay that allows the thread to do other work in the meantime. This illustrates the interconnection between asynchronous tasks and the RunLoop. The timer block will be called every quarter second, with the RunLoop responsible for this condition. However, if the thread is busy with a long-running task and the iteration cannot be completed within 0.25 seconds, the timer's block will be delayed. Let's modify the example so that the block outputs the current time: Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print(Date())
} Let’s see what will be the console output: 2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000 In this case,  the timer goes off four times per second. Let's now add another asynchronous task that runs once every second and takes up the thread by waiting to be executed: Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print(Date())
}

Timer.scheduledTimer(withTimeInterval: 1, repeats: true) { timer in    
  sleep(1)
} Console output: 2017-09-26 05:17:33 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:35 +0000
2017-09-26 05:17:35 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:37 +0000
2017-09-26 05:17:37 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:39 +0000
2017-09-26 05:17:39 +0000
2017-09-26 05:17:40 +0000
2017-09-26 05:17:40 +0000 As you can see, the timer now triggers at irregular intervals, sometimes twice, sometimes three times per second. This happened because the thread was too busy running other code to process the timer in time. This example perfectly illustrates that there is no magic in asynchronous code. It relies on the RunLoop and competes with other tasks in the thread. My advice is: don’t rely on miracles when planning asynchronous tasks; consider whether they can be executed on time. If there is a likelihood that thread resources may be insufficient to run all tasks, consider offloading tasks to separate threads where they won’t face interference. Conclusion In the next article, we will talk about the main approaches to building multi-threaded code in iOS and will touch upon the concepts of Thread, Grand Central Dispatch (GCD), and Operation. Stay tuned! RunLoops impact on asynchronous tasks I am Boris Dobretsov, and some time ago I published my first article - Understanding Parallel Programming: A Guide for Beginners. Understanding Parallel Programming: A Guide for Beginners . Understanding Parallel Programming: A Guide for Beginners https://hackernoon.com/understanding-parallel-programming-a-guide-for-beginners?embedable=true https://hackernoon.com/understanding-parallel-programming-a-guide-for-beginners?embedable=true In that article, I introduced basic concepts such as " processes " and " threads " and explained in simple terms what a processor, operating system, process, and thread are. processes threads Today, we will elaborate further on RunLoops and their impact on asynchronous tasks. RunLoops But first, let's refresh our knowledge of what a RunLoop is and what it is responsible for. RunLoop A RunLoop helps asynchronous tasks run at the right time without blocking or interfering with the main thread. It functions as a cycle of event handling, used to schedule tasks and coordinate incoming events. Its purpose is to keep the thread active when there is work to do and put it to sleep when there is none. A RunLoop helps asynchronous tasks run at the right time without blocking or interfering with the main thread. It functions as a cycle of event handling, used to schedule tasks and coordinate incoming events. Its purpose is to keep the thread active when there is work to do and put it to sleep when there is none. RunLoop As we know from the previous article, there are several main types of architecture for code organization: Synchronous single-threaded Asynchronous single-threaded Synchronous multi-threaded Asynchronous multi-threaded Synchronous single-threaded Synchronous single-threaded Synchronous single-threaded Asynchronous single-threaded Asynchronous single-threaded Asynchronous single-threaded Synchronous multi-threaded Synchronous multi-threaded Synchronous multi-threaded Asynchronous multi-threaded Asynchronous multi-threaded Asynchronous multi-threaded Some of these are simpler, while others are designed to run several tasks (competing tasks) at the same time, making the development process more efficient and multifunctional. The most commonly used architecture in iOS application development is the asynchronous multi-threaded model . It is important to understand how to interact with these models and what to do to prevent overloading. That is why in this article we are going to discuss RunLoops impact on asynchronous tasks . asynchronous multi-threaded model RunLoops impact on asynchronous tasks As we also know from the previous article, asynchronous tasks can be paused mid-execution and resumed later. But who decides when to put a task on hold and when to resume it? But who decides when to put a task on hold and when to resume it? It’s actually the task itself that makes this decision. This is because asynchronous tasks consist of two parts: the first starts the task, and the second executes asynchronously in response to a specific event. The latter part is added to a source for the RunLoop and is checked on each loop iteration. If the specified event occurs, the task proceeds. A basic example of an asynchronous task is a timer . Let me share the code which which demonstrates this idea: timer Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print("tick")
} Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print("tick")
} In the above example, you can see the code which starts a timer that runs every quarter of a second, outputting "tick" to the console. The first part of the asynchronous task is creating the timer, and the second part is passing the block to the scheduled Timer method. The task is single-threaded: both the timer setup and block execution happen in the same thread. However, it is asynchronous since the block doesn’t execute immediately but after a delay that allows the thread to do other work in the meantime. This illustrates the interconnection between asynchronous tasks and the RunLoop. The timer block will be called every quarter second, with the RunLoop responsible for this condition. However, if the thread is busy with a long-running task and the iteration cannot be completed within 0.25 seconds, the timer's block will be delayed. Let's modify the example so that the block outputs the current time: Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print(Date())
} Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print(Date())
} Let’s see what will be the console output: 2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000 2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:16 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:17 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000
2017-09-26 05:13:18 +0000 In this case,  the timer goes off four times per second. Let's now add another asynchronous task that runs once every second and takes up the thread by waiting to be executed: Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print(Date())
}

Timer.scheduledTimer(withTimeInterval: 1, repeats: true) { timer in    
  sleep(1)
} Timer.scheduledTimer(withTimeInterval: 0.25, repeats: true) { timer in    
  print(Date())
}

Timer.scheduledTimer(withTimeInterval: 1, repeats: true) { timer in    
  sleep(1)
} Console output: 2017-09-26 05:17:33 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:35 +0000
2017-09-26 05:17:35 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:37 +0000
2017-09-26 05:17:37 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:39 +0000
2017-09-26 05:17:39 +0000
2017-09-26 05:17:40 +0000
2017-09-26 05:17:40 +0000 2017-09-26 05:17:33 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:34 +0000
2017-09-26 05:17:35 +0000
2017-09-26 05:17:35 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:36 +0000
2017-09-26 05:17:37 +0000
2017-09-26 05:17:37 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:38 +0000
2017-09-26 05:17:39 +0000
2017-09-26 05:17:39 +0000
2017-09-26 05:17:40 +0000
2017-09-26 05:17:40 +0000 As you can see, the timer now triggers at irregular intervals, sometimes twice, sometimes three times per second. This happened because the thread was too busy running other code to process the timer in time. This example perfectly illustrates that there is no magic in asynchronous code. It relies on the RunLoop and competes with other tasks in the thread. My advice is: don’t rely on miracles when planning asynchronous tasks; consider whether they can be executed on time. If there is a likelihood that thread resources may be insufficient to run all tasks, consider offloading tasks to separate threads where they won’t face interference. Conclusion In the next article, we will talk about the main approaches to building multi-threaded code in iOS and will touch upon the concepts of Thread , Grand Central Dispatch (GCD) , and Operation . Stay tuned! Thread Grand Central Dispatch (GCD) Operation

Understanding Parallel Programming: A Guide for Beginners, Part II

After finishing the Mastermind project, which was the most difficult project so far, I moved to the Files and Serialization lesson in The Odin Project curriculum. I stumbled upon a lot of long articles full of technical language that for me, non-English native speaker were quite difficult to understand. Especially after coming back from my 9-5. When I was reading the last one, many things clicked and I thought it all could have been explained in a little easier way. I came up with an idea of how to make it in 6 simple steps and the results are below. This is a nice funky graph for you to visualize it: STEPS 1 - 2 Let’s start from the input. When you are typing something, input (IO) is taken from your keyboard and sent to TTY virtual device. TTY in Linux is the interface that handles input/output. STEP 3 The input is then passed to the TTY session (the terminal interface you interact with). STEP 4 From there, the TTY virtual device forwards it to the line discipline inside the kernel. Line discipline is the place where magic happens. For example, pressing BACKSPACE will clear the last character we typed in or process special keys, signals, and interpret commands. STEP 5 After processing, the line discipline sends the input to the foreground process (like a shell) via STDIN. STEP 6 When the process generates output, it then sends it to STDOUT or STDERR if it’s an error, which goes back through the TTY virtual device and then displays on the TTY session again. Final thoughts Don’t you think these processes are really interesting? Since I started learning how to code I was always curious about how everything works under the hood. What happens when you press some buttons, what kind of signals are sent, where they are going, and so on. Maybe in the future, I will make a similar graph to visualize something else. We will see what I will get stuck at soon. If you have more questions, drop a comment below! I’d love to hear what topics you’re struggling with or find intriguing. Your feedback helps me decide what to break down next. Happy learning! After finishing the Mastermind project, which was the most difficult project so far, I moved to the Files and Serialization lesson in The Odin Project curriculum. The Odin Project I stumbled upon a lot of long articles full of technical language that for me, non-English native speaker were quite difficult to understand. Especially after coming back from my 9-5. When I was reading the last one, many things clicked and I thought it all could have been explained in a little easier way. I came up with an idea of how to make it in 6 simple steps and the results are below. This is a nice funky graph for you to visualize it: STEPS 1 - 2 Let’s start from the input. When you are typing something, input (IO) is taken from your keyboard and sent to TTY virtual device. TTY in Linux is the interface that handles input/output. STEP 3 The input is then passed to the TTY session (the terminal interface you interact with). STEP 4 From there, the TTY virtual device forwards it to the line discipline inside the kernel. Line discipline is the place where magic happens. For example, pressing BACKSPACE will clear the last character we typed in or process special keys, signals, and interpret commands. STEP 5 After processing, the line discipline sends the input to the foreground process (like a shell) via STDIN. STEP 6 When the process generates output, it then sends it to STDOUT or STDERR if it’s an error, which goes back through the TTY virtual device and then displays on the TTY session again. Final thoughts Don’t you think these processes are really interesting? Since I started learning how to code I was always curious about how everything works under the hood. What happens when you press some buttons, what kind of signals are sent, where they are going, and so on. Maybe in the future, I will make a similar graph to visualize something else. We will see what I will get stuck at soon. If you have more questions, drop a comment below! I’d love to hear what topics you’re struggling with or find intriguing. Your feedback helps me decide what to break down next. Happy learning!

How to Understand IO and TTY in Linux for Beginners

According to @reganhimself, consider Pixel Pals as a kind of social experiment. It will be interesting to see what art people make collectively assuming more than one person buys the pixels required to draw a picture. It will also be interesting if people will work together and join forces to draw something coherently or go to war with one another! Before executing the steps, take a look at the information provided in the About tab at https://pixel-pals.art/ In principle, it’s simple: Buy a pixel token from a dispenser. Burn the pixel token specifying a Hex color code in the memo field e.g., #FFFFFF using the Freewallet “destroy” function. Grid cells will be colored in the order the burns are confirmed on the blockchain. Receive a tokenized final piece for each pixel burned when all cells are colored or a given timeframe passes. …but the tricky part lies in the details, especially for those unfamiliar with Bitcoin, Freewallet, funding a wallet, using a dispenser, or the burn functionality. So, this is the extended list of steps to participate in Pixel Pals: 1 — Read all the information on the website. 2 — Setting your Freewallet wallet (This is not available at the moment). 3 — Buy a pixel from the dispenser. 4 — Burn the pixel token specifying a Hex color code in the memo field e.g. #FFFFFF using the Freewallet “destroy” function. 5 — Grid cells will be colored in the order the burns are confirmed on the blockchain. 6 — Receive a tokenized final piece for each pixel burned when all cells are colored or a given timeframe passes. 1 — Read All the Information Available at Pixel-Pals Open a browser, and go to https://pixel-pals.art/ My first suggestion is to join their telegram group https://t.me/Pixel_Pals If you face any issue, the community will help you to get it solved. IMPORTANT: Never share your private key or seed word. More about it in the Freewallet section Read the About tab carefully; there is a lot of valuable information. 2 — Download, Install, and Fund Freewallet Freewallet is an open-source wallet for Bitcoin and Counterparty. It uses Legacy and Segwit Bitcoin addresses and lets you store Bitcoin, XCP, and user-created tokens among others. Download Freewallet: Open a browser, and go to https://freewallet.io/ . IMPORTANT: do not confuse with freewallet.org. !!! Be aware that Freewallet desktop versions are the only ones supporting all the functionality required in the steps. Select the version of your preference to start downloading the installer. Select the version of your preference to start downloading the installer. In this guide, Windows will be used. You will be sent to GitHub. Install FreeWallet: After you download FreeWallet, you can click on the downloaded file and the installation will start. Create FreeWallet: Not available yet IMPORTANT: Keep tour private key and seed words in a safe place. and never share them. if someone gains access to those they have full access to your wallet. If you lose those, you will not be able to access to the wallet and asset will be inaccesible forever. Once your wallet has been created, you will land at the main FreeWallet screen. Now, let’s figure out which address you need to fund. Click on the “Address” icon, and select View Address. In the pop-up screen, you will see a QR code and the address to copy. From your exchange, send some BTC to the specified address. Keep in mind that 1 Pixel Pal costs BTC 0.000025, but to cover miner fees, it’s best to add a bit extra. Sending an amount equivalent to USD 10 will be more than sufficient, allowing you to purchase multiple Pixel Pals. 3 — Buy a Pixel From the Dispenser A dispenser is an address that automatically sends a token back to you when you send BTC to it. The current token price is BTC 0.000025. So, if you send this amount to the dispenser address, you’ll receive one token directly to your address. Another example, sending BTC 0.00005 will return 2 tokens. To find the dispenser address, visit https://pixel-pals.art/. Click on Buy, and a new tab will open in the browser with the details of the dispenser. Identify the address and the amount to be sent. A few remarks before proceeding! IMPORTANT:
Do not send BTC if the “Give Quantity” is 0, as this means the dispenser is empty. Sending BTC in this case will not result in receiving a token.
Additionally, only send BTC from FreeWallet — not from an exchange account. Select and copy the entire address using your mouse cursor. Then, open FreeWallet to proceed with sending BTC to the dispenser. Select the account, and click with the mouse right button and a menu will appear. Fill in the information. Destination field: Paste the address you copied to your clipboard here. Amount field: The minimum amount is BTC 0.000025, as stated in the dispenser. In this example, BTC 0.000050 is being sent to purchase 2 Pixel Pals (because who doesn’t love Pixel Pals?). This is the simplest data setup for this example. You’ll notice that transaction fees are calculated automatically. IMPORTANT: Before proceeding sending funds, check and double check the information! If all the information is correct, click on “Send Funds” and a new pop-up will appear.This is your final chance to cancel the transaction. Please double-check the amount, and ensure the address is correct. If everything looks good, click “Yes.” A pop-up will then appear, allowing you to monitor your transaction status. You can click on it to check progress. Note that it may take some time for the transaction to be picked up, so don’t worry if it doesn’t appear immediately. By clicking “OK,” congratulations are in order — you’ve successfully purchased a token from the dispenser! Once your transaction is processed, the token will appear in FreeWallet. In this example, I purchased 2 PIXELPALS.gen2 tokens, which will be burned in the next step. 4 — Burn the pixel token specifying a Hex color code in the memo field eg #FFFFFF using the Freewallet “destroy” function. Make sure that you have in mind the colors that you want to select for the pixel. Go to https://coolors.co/palettes/trending, select a color that you like, and copy it to the clipboard. The information that you copied looks like this 03045e; add a # at the front, and you have the information that you will need to fill in #03045e. Select the token, and click on it with the right button of the mouse. Click on Destroy PIXELPALS.gen2 option and fill in the following information. Amount field: the number of tokens that you want to destroy. Memo: the color that you have selected. In this case, 2 tokens will be burned and will have the same color. Once you checked the information, click on the “Destroy” button and the following pop-up will appear. This is the last chance that you have to cancel the transaction. If you agree, click on the “Yes” button. After a few minutes, go back to the Pixel Pals website, and you will see your pixel added to the matrix. You’ve accomplished an impressive feat in the world of Bitcoin blockchain and Counterparty! As a community member, you’ve helped bring Pixel Pals one step further. This is definitely worth sharing! Click on the community's progress share button. A nice detail is that your token burn/destroy is announced in the telegram channel. You will receive a tokenized final piece for each pixel burned when all cells are colored or a given timeframe passes. Thank you for your attention, and if you wish check my stamp collections: https://stamped.ninja/profile/TonyNL/collections According to @reganhimself, consider Pixel Pals as a kind of social experiment. It will be interesting to see what art people make collectively assuming more than one person buys the pixels required to draw a picture. It will also be interesting if people will work together and join forces to draw something coherently or go to war with one another! Before executing the steps, take a look at the information provided in the About tab at https://pixel-pals.art/ https://pixel-pals.art/ In principle, it’s simple: Buy a pixel token from a dispenser. Burn the pixel token specifying a Hex color code in the memo field e.g., #FFFFFF using the Freewallet “destroy” function. Grid cells will be colored in the order the burns are confirmed on the blockchain. Receive a tokenized final piece for each pixel burned when all cells are colored or a given timeframe passes. …but the tricky part lies in the details, especially for those unfamiliar with Bitcoin, Freewallet, funding a wallet, using a dispenser, or the burn functionality. So, this is the extended list of steps to participate in Pixel Pals: 1 — Read all the information on the website. 2 — Setting your Freewallet wallet (This is not available at the moment). 3 — Buy a pixel from the dispenser. 4 — Burn the pixel token specifying a Hex color code in the memo field e.g. #FFFFFF using the Freewallet “destroy” function. 5 — Grid cells will be colored in the order the burns are confirmed on the blockchain. 6 — Receive a tokenized final piece for each pixel burned when all cells are colored or a given timeframe passes. 1 — Read All the Information Available at Pixel-Pals Open a browser, and go to https://pixel-pals.art/ https://pixel-pals.art/ My first suggestion is to join their telegram group https://t.me/Pixel_Pals https://t.me/Pixel_Pals https://t.me/Pixel_Pals If you face any issue, the community will help you to get it solved. IMPORTANT: Never share your private key or seed word. More about it in the Freewallet section IMPORTANT: Never share your private key or seed word. More about it in the Freewallet section IMPORTANT: Never share your private key or seed word. More about it in the Freewallet section Read the About tab carefully; there is a lot of valuable information. 2 — Download, Install, and Fund Freewallet Freewallet is an open-source wallet for Bitcoin and Counterparty. It uses Legacy and Segwit Bitcoin addresses and lets you store Bitcoin, XCP, and user-created tokens among others. Download Freewallet: Open a browser, and go to https://freewallet.io/ . https://freewallet.io/ https://freewallet.io/ IMPORTANT: do not confuse with freewallet.org. !!! IMPORTANT: do not confuse with freewallet.org. !!! IMPORTANT: do not confuse with freewallet.org. !!! Be aware that Freewallet desktop versions are the only ones supporting all the functionality required in the steps. Select the version of your preference to start downloading the installer. Select the version of your preference to start downloading the installer. In this guide, Windows will be used. You will be sent to GitHub. Install FreeWallet: After you download FreeWallet, you can click on the downloaded file and the installation will start. Create FreeWallet: Not available yet IMPORTANT: Keep tour private key and seed words in a safe place. and never share them. if someone gains access to those they have full access to your wallet. If you lose those, you will not be able to access to the wallet and asset will be inaccesible forever. IMPORTANT: Keep tour private key and seed words in a safe place. and never share them. if someone gains access to those they have full access to your wallet. If you lose those, you will not be able to access to the wallet and asset will be inaccesible forever. Once your wallet has been created, you will land at the main FreeWallet screen. Now, let’s figure out which address you need to fund. Click on the “Address” icon, and select View Address. In the pop-up screen, you will see a QR code and the address to copy. From your exchange, send some BTC to the specified address. Keep in mind that 1 Pixel Pal costs BTC 0.000025, but to cover miner fees, it’s best to add a bit extra. Sending an amount equivalent to USD 10 will be more than sufficient, allowing you to purchase multiple Pixel Pals. 3 — Buy a Pixel From the Dispenser A dispenser is an address that automatically sends a token back to you when you send BTC to it. The current token price is BTC 0.000025. So, if you send this amount to the dispenser address, you’ll receive one token directly to your address. Another example, sending BTC 0.00005 will return 2 tokens. To find the dispenser address, visit https://pixel-pals.art/ . https://pixel-pals.art/ https://pixel-pals.art/ Click on Buy, and a new tab will open in the browser with the details of the dispenser. Identify the address and the amount to be sent. A few remarks before proceeding! IMPORTANT: Do not send BTC if the “Give Quantity” is 0, as this means the dispenser is empty. Sending BTC in this case will not result in receiving a token. Additionally, only send BTC from FreeWallet — not from an exchange account. IMPORTANT: IMPORTANT: Do not send BTC if the “Give Quantity” is 0, as this means the dispenser is empty. Sending BTC in this case will not result in receiving a token. Do not send BTC if the “Give Quantity” is 0, as this means the dispenser is empty. Sending BTC in this case will not result in receiving a token. Additionally, only send BTC from FreeWallet — not from an exchange account. Additionally, only send BTC from FreeWallet — not from an exchange account. Select and copy the entire address using your mouse cursor. Then, open FreeWallet to proceed with sending BTC to the dispenser. Select the account, and click with the mouse right button and a menu will appear. Fill in the information. Destination field : Paste the address you copied to your clipboard here. Destination field Amount field : The minimum amount is BTC 0.000025, as stated in the dispenser. Amount field In this example, BTC 0.000050 is being sent to purchase 2 Pixel Pals (because who doesn’t love Pixel Pals?). This is the simplest data setup for this example. You’ll notice that transaction fees are calculated automatically. IMPORTANT: Before proceeding sending funds, check and double check the information! IMPORTANT: Before proceeding sending funds, check and double check the information! IMPORTANT: Before proceeding sending funds, check and double check the information! If all the information is correct, click on “Send Funds” and a new pop-up will appear. This is your final chance to cancel the transaction. Please double-check the amount, and ensure the address is correct. If everything looks good, click “Yes.” A pop-up will then appear, allowing you to monitor your transaction status. You can click on it to check progress. Note that it may take some time for the transaction to be picked up, so don’t worry if it doesn’t appear immediately. By clicking “OK,” congratulations are in order — you’ve successfully purchased a token from the dispenser! Once your transaction is processed, the token will appear in FreeWallet. In this example, I purchased 2 PIXELPALS.gen2 tokens, which will be burned in the next step. 4 — Burn the pixel token specifying a Hex color code in the memo field eg #FFFFFF using the Freewallet “destroy” function. Make sure that you have in mind the colors that you want to select for the pixel. Go to https://coolors.co/palettes/trending, select a color that you like, and copy it to the clipboard. https://coolors.co/palettes/trending , https://coolors.co/palettes/trending The information that you copied looks like this 03045e; add a # at the front, and you have the information that you will need to fill in #03045e. Select the token, and click on it with the right button of the mouse. Click on Destroy PIXELPALS.gen2 option and fill in the following information. Amount field: the number of tokens that you want to destroy. Memo: the color that you have selected. In this case, 2 tokens will be burned and will have the same color. Once you checked the information, click on the “Destroy” button and the following pop-up will appear. This is the last chance that you have to cancel the transaction. If you agree, click on the “Yes” button. After a few minutes, go back to the Pixel Pals website, and you will see your pixel added to the matrix. You’ve accomplished an impressive feat in the world of Bitcoin blockchain and Counterparty! As a community member, you’ve helped bring Pixel Pals one step further. This is definitely worth sharing! Click on the community's progress share button. A nice detail is that your token burn/destroy is announced in the telegram channel. You will receive a tokenized final piece for each pixel burned when all cells are colored or a given timeframe passes. Thank you for your attention, and if you wish check my stamp collections: https://stamped.ninja/profile/TonyNL/collections https://stamped.ninja/profile/TonyNL/collections https://stamped.ninja/profile/TonyNL/collections

 Pixel Pals - Step by Step for Beginners

Understanding Parallel Programming: A Guide for Beginners

Table of Contents An Introduction To The World of Passes
Passes New Partnership Launch: The Beginning of a Gaming Revolution
Passes New Partnership Launch: The Significance of the Near Future
Passes Onboarding: How To Get Started with Passes An Introduction To The World of Passes If you are a content creator, entrepreneur, or artist in the Web 3 space, you most likely have heard of different content monetization platforms that help content creators earn a living. Today, I am letting you in on a well-guarded secret. I will be telling you about Passes as a platform, their latest partnership launch, and what that means for the gaming industry in the near future. Passes is an all-in-one content monetization platform that helps content creators engage with their fans, become entrepreneurs, and build their professional brands. Since its inception in 2022, the platform has been intentional about fostering collaborations that boost diversity of content for fans and generate revenue for creators. It is no wonder why on the 23rd of October 2024, Passes announced its new partnership with gaming creators SSSniperwolf and Neekolul as the latest creator partners on the platform. Today, I will be telling you all about the launch and its significance in the gaming industry. Passes New Partnership Launch: The Beginning of a Gaming Revolution Passes new partnership is set to provide fans with a new experience as they connect with their favorite gaming creators. As Passes creators, SSSniperwolf and Neekolul will headline Passes' growing roster of gaming and streaming talent, offering their audiences a variety of exclusive experiences and interactions, from limited-time merch drops to live meet-and-greets, gameplay challenges, and more. This collaboration is set to redefine how fans connect with creators, bringing a new era of engagement to the platform. SSSniperwolf, a gaming powerhouse with millions of subscribers, expressed her excitement about the partnership: "This is gonna be so much fun! I’ve always wanted to find new ways to interact with my fans, and Passes is making that happen. We’ve got some really cool stuff coming your way—exclusive content, live streams, and more. You definitely don’t want to miss what’s next, it’s gonna be huge!" Neekolul, known for her innovative streaming style and captivating content, added: "I’m thrilled to join Passes as a creator. Together, we’re going to offer fans something totally fresh and interactive. I can't wait to reveal what's in store!" Lucy Guo, Passes Founder and Chief Executive Officer, highlighted the importance of the new partnership for the platform’s growth: "SSSniperwolf and Neekolul are pioneers in gaming and digital entertainment. At Passes, we’re always looking to create partnerships that give fans unparalleled access to their favorite creators, and we couldn’t be more excited to welcome these two gaming icons to the Passes family. This collaboration not only expands our presence in the gaming world but also enhances our mission to deliver truly one-of-a-kind experiences that bring fans closer to the creators they love." The Creator program on Passes is designed to empower creators by offering them innovative tools and opportunities to engage with their audience like never before. This latest expansion with SSSniperwolf and Neekolul underscores Passes’ commitment to staying at the forefront of creator-fan relationships in the gaming and streaming spaces. This will translate to more adoption of gaming by fans of other creators and easier entry for gaming content creators on the platform. Passes New Partnership Launch: The Significance of the Near Future Passes as a platform has a community of over a thousand creators and more than half a million users. Most of the popular creators focus on industries like sports, astrology, music, and fashion. Passes new partnership with SSSniperwolf and Neekolul creates a space on the platform for more gaming and streaming content, diversifying fan options. The new creators, SSSniperwolf and Neekolul are also bringing in their millions of fans onto the Passes platform. This will increase the number of fans using the platform and generate more awareness about the platform. Generally, creator revenue will increase, and more content creators will jump on the platform, especially those in the gaming industry. The gaming content creation industry is expanding daily as the number of gamers worldwide increases. The global gaming market was projected to reach a value of $159.3 billion by the end of 2020, and subsequently generate more revenue in the future with the entrance of new gaming technologies like virtual reality and cloud gaming. A good number of content creators want to tap into the revenue that gaming provides. In addition, gamers are always searching for diverse gaming content on different content platforms. Passes, in the near future, will provide a content monetization platform with diverse content for gamers and more revenue-generation opportunities for gaming content creators to jump on. Passes Onboarding: How To Get Started with Passes If you are a content creator with over a hundred thousand fans and you are looking for a content monetization platform where you can connect with fans, grow your business, and earn an income, you are in luck. Get started on Passes today by following this step-wise guide. Apply to become a Creator on Passes.
Choose a profile picture + banner + bio.
Verify your identity with a selfie + government ID.
Make at least 2 membership tiers with different prices and perks.
Add 3-5 locked wall posts.
Add 1-2 free wall posts.
Add Welcome Messages to make passive income.
Post your Passes URL on your other social media accounts to connect with fans.
Set up your Payouts and receive instant payments on PayPal and bank transfer. If you have followed the above steps, congratulations. You have successfully set up a Passes Creator account and you are on your way to earning five times more profit, selling limited merch, and connecting with millions of fans. Table of Contents Table of Contents An Introduction To The World of Passes Passes New Partnership Launch: The Beginning of a Gaming Revolution Passes New Partnership Launch: The Significance of the Near Future Passes Onboarding: How To Get Started with Passes An Introduction To The World of Passes Passes New Partnership Launch: The Beginning of a Gaming Revolution Passes New Partnership Launch: The Significance of the Near Future Passes Onboarding: How To Get Started with Passes An Introduction To The World of Passes An Introduction To The World of Passes If you are a content creator, entrepreneur, or artist in the Web 3 space, you most likely have heard of different content monetization platforms that help content creators earn a living. Today, I am letting you in on a well-guarded secret. I will be telling you about Passes as a platform, their latest partnership launch, and what that means for the gaming industry in the near future. Passes is an all-in-one content monetization platform that helps content creators engage with their fans, become entrepreneurs, and build their professional brands. Since its inception in 2022, the platform has been intentional about fostering collaborations that boost diversity of content for fans and generate revenue for creators. Passes Passes It is no wonder why on the 23rd of October 2024 , Passes announced its new partnership with gaming creators SSSniperwolf and Neekolul as the latest creator partners on the platform. Today, I will be telling you all about the launch and its significance in the gaming industry. on the 23rd of October 2024 SSSniperwolf SSSniperwolf Neekolul Neekolul Passes New Partnership Launch: The Beginning of a Gaming Revolution Passes New Partnership Launch: The Beginning of a Gaming Revolution Passes new partnership is set to provide fans with a new experience as they connect with their favorite gaming creators. As Passes creators, SSSniperwolf and Neekolul will headline Passes' growing roster of gaming and streaming talent, offering their audiences a variety of exclusive experiences and interactions, from limited-time merch drops to live meet-and-greets, gameplay challenges, and more. This collaboration is set to redefine how fans connect with creators, bringing a new era of engagement to the platform. SSSniperwolf, a gaming powerhouse with millions of subscribers, expressed her excitement about the partnership: "This is gonna be so much fun! I’ve always wanted to find new ways to interact with my fans, and Passes is making that happen. We’ve got some really cool stuff coming your way—exclusive content, live streams, and more. You definitely don’t want to miss what’s next, it’s gonna be huge!" Neekolul, known for her innovative streaming style and captivating content, added: "I’m thrilled to join Passes as a creator. Together, we’re going to offer fans something totally fresh and interactive. I can't wait to reveal what's in store!" Lucy Guo, Passes Founder and Chief Executive Officer, highlighted the importance of the new partnership for the platform’s growth: "SSSniperwolf and Neekolul are pioneers in gaming and digital entertainment. At Passes, we’re always looking to create partnerships that give fans unparalleled access to their favorite creators, and we couldn’t be more excited to welcome these two gaming icons to the Passes family. This collaboration not only expands our presence in the gaming world but also enhances our mission to deliver truly one-of-a-kind experiences that bring fans closer to the creators they love." The Creator program on Passes is designed to empower creators by offering them innovative tools and opportunities to engage with their audience like never before. This latest expansion with SSSniperwolf and Neekolul underscores Passes’ commitment to staying at the forefront of creator-fan relationships in the gaming and streaming spaces. This will translate to more adoption of gaming by fans of other creators and easier entry for gaming content creators on the platform. Passes New Partnership Launch: The Significance of the Near Future Passes New Partnership Launch: The Significance of the Near Future Passes as a platform has a community of over a thousand creators and more than half a million users. Most of the popular creators focus on industries like sports, astrology, music, and fashion. Passes new partnership with SSSniperwolf and Neekolul creates a space on the platform for more gaming and streaming content, diversifying fan options. Passes as a platform Passes as a platform The new creators, SSSniperwolf and Neekolul are also bringing in their millions of fans onto the Passes platform. This will increase the number of fans using the platform and generate more awareness about the platform. Generally, creator revenue will increase, and more content creators will jump on the platform, especially those in the gaming industry. SSSniperwolf SSSniperwolf Neekolul Neekolul The gaming content creation industry is expanding daily as the number of gamers worldwide increases. The global gaming market was projected to reach a value of $159.3 billion by the end of 2020, and subsequently generate more revenue in the future with the entrance of new gaming technologies like virtual reality and cloud gaming. global gaming market global gaming market A good number of content creators want to tap into the revenue that gaming provides. In addition, gamers are always searching for diverse gaming content on different content platforms. Passes, in the near future, will provide a content monetization platform with diverse content for gamers and more revenue-generation opportunities for gaming content creators to jump on. Passes Onboarding: How To Get Started with Passes Passes Onboarding: How To Get Started with Passes If you are a content creator with over a hundred thousand fans and you are looking for a content monetization platform where you can connect with fans, grow your business, and earn an income, you are in luck. Get started on Passes today by following this step-wise guide. Apply to become a Creator on Passes. Choose a profile picture + banner + bio. Verify your identity with a selfie + government ID. Make at least 2 membership tiers with different prices and perks. Add 3-5 locked wall posts. Add 1-2 free wall posts. Add Welcome Messages to make passive income. Post your Passes URL on your other social media accounts to connect with fans. Set up your Payouts and receive instant payments on PayPal and bank transfer. Apply to become a Creator on Passes. Creator Creator Choose a profile picture + banner + bio. Verify your identity with a selfie + government ID. Make at least 2 membership tiers with different prices and perks. Add 3-5 locked wall posts. Add 1-2 free wall posts. Add Welcome Messages to make passive income. Post your Passes URL on your other social media accounts to connect with fans. Set up your Payouts and receive instant payments on PayPal and bank transfer. Payouts Payouts If you have followed the above steps, congratulations. You have successfully set up a Passes Creator account and you are on your way to earning five times more profit, selling limited merch, and connecting with millions of fans.

Passes New Partnership Launch: Is It the Beginning of a Gaming Revolution?

HackerNoon: What is your company in 2–5 words? Dave Wreski: The open-source email security provider. Why is now the time for your company to exist? Email-borne risk has never been greater. Over 90% of modern cyberattacks begin with a phishing email. Attacks like spear phishing, fileless malware, and zero-day exploits are becoming increasingly difficult to detect and block. Basic email protection, like the security features provided in Microsoft 365 and Google Workspace, is no longer sufficient to make email safe for business. Advanced, multi-layered solutions capable of anticipating and blocking known and emerging threats before they reach the inbox are necessary in this modern threat environment. What do you love about your team, and why are you the ones to solve this problem? As users of and contributors to open-source development, we share the values of transparency and collaboration. Our unique use of open-source development in email security enables us to provide flexible, cost-efficient, and exceptionally secure solutions and offer real-time updates to keep our customers ahead of the latest threats. If you weren’t building your startup, what would you be doing? I would be contributing to Internet security in another way. Before starting Guardian Digital, I was a security engineer at UPS, which I enjoyed and found very rewarding. I also love cooking and writing, so I would likely pursue these passions. At the moment, how do you measure success? What are your metrics? I measure success in the number of malicious emails our solution blocks, protecting our clients from a potential cyberattack or data breach. I also take pride in retaining our clients, many of whom have been with us for decades, and continuing to acquire new clients worldwide. In a few sentences, what do you offer to whom? We offer threat-ready, fully supported protection against the latest and most advanced email threats for businesses of all sizes in all industries. Our multi-layered security system anticipates and blocks all threats before they reach the inbox, leveraging AI-based detection and expert around-the-clock system monitoring and support. Our managed services extend small businesses’ IT resources and enhance security, delivering a rapid return on investment (ROI). What’s most exciting about your traction to date? We have continued to grow our Product offering and client base over the past 2+ decades. We now offer Security Awareness Training and vCISO email security services. We have also developed an intuitive real-time Dashboard for our solution, giving businesses complete visibility and control over their email security. Where do you think your growth will be next year? We expect to continue acquiring new clients over the next year, as we are investing heavily in our marketing efforts and developing our solution. Our clients come to us for additional protection against today’s advanced threats that go unidentified by default cloud email security in Microsoft 365 and Google Workspace. Our clients are looking to reduce support overhead while bolstering cloud email protection to defend against threats like targeted spear phishing and business email compromise, making our solution ideal for their requirements. Tell us about your first paying customer and revenue expectations over the next year. Guardian Digital's roots are as an open-source Internet security company. It provides businesses of all sizes with solutions to common business security problems, such as user privacy solutions, firewalls, secure routers, and secure web servers. Our founder, Dave Wreski, started his infosec career at United Parcel Service when the commercial Internet was in its infancy. Dave found a way to use open source to build and install open source security solutions in local businesses that were equivalent to or exceeded the solutions UPS was paying hundreds of thousands of dollars per year for virtually the same protection provided by open source. Using this knowledge, his programming and development background, and the skills learned as the security architect for UPS, Dave built a company around this idea and started selling service and support solutions to small businesses—first in the local area to businesses that needed cheap but effective networking solutions, then online to thousands of businesses worldwide that needed a secure enterprise all-in-one server solution called EnGarde. EnGarde was our first business product, sold to tens of thousands of businesses worldwide, and set the foundation for Guardian Digital's current position. What’s your biggest threat? Our biggest threat is modern cyberattackers, who continue to try to outsmart the latest, most advanced security solutions. Cybersecurity is an ongoing “cat and mouse” game between threat actors and security providers. We are confident we can keep our clients ahead of the latest threats via advanced, layered open-source technology and expert system management, monitoring, and support. HackerNoon : What is your company in 2–5 words? HackerNoon Dave Wreski : The open-source email security provider. Dave Wreski Dave Wreski Why is now the time for your company to exist? Email-borne risk has never been greater. Over 90% of modern cyberattacks begin with a phishing email. Attacks like spear phishing, fileless malware, and zero-day exploits are becoming increasingly difficult to detect and block. Basic email protection, like the security features provided in Microsoft 365 and Google Workspace, is no longer sufficient to make email safe for business. Advanced, multi-layered solutions capable of anticipating and blocking known and emerging threats before they reach the inbox are necessary in this modern threat environment. What do you love about your team, and why are you the ones to solve this problem? As users of and contributors to open-source development, we share the values of transparency and collaboration. Our unique use of open-source development in email security enables us to provide flexible, cost-efficient, and exceptionally secure solutions and offer real-time updates to keep our customers ahead of the latest threats. If you weren’t building your startup, what would you be doing? I would be contributing to Internet security in another way. Before starting Guardian Digital , I was a security engineer at UPS, which I enjoyed and found very rewarding. I also love cooking and writing, so I would likely pursue these passions. Guardian Digital At the moment, how do you measure success? What are your metrics? I measure success in the number of malicious emails our solution blocks, protecting our clients from a potential cyberattack or data breach. I also take pride in retaining our clients, many of whom have been with us for decades, and continuing to acquire new clients worldwide. In a few sentences, what do you offer to whom? We offer threat-ready, fully supported protection against the latest and most advanced email threats for businesses of all sizes in all industries. Our multi-layered security system anticipates and blocks all threats before they reach the inbox, leveraging AI-based detection and expert around-the-clock system monitoring and support. Our managed services extend small businesses’ IT resources and enhance security, delivering a rapid return on investment (ROI). What’s most exciting about your traction to date? We have continued to grow our Product offering and client base over the past 2+ decades. We now offer Security Awareness Training and vCISO email security services. We have also developed an intuitive real-time Dashboard for our solution, giving businesses complete visibility and control over their email security. Where do you think your growth will be next year? We expect to continue acquiring new clients over the next year, as we are investing heavily in our marketing efforts and developing our solution. Our clients come to us for additional protection against today’s advanced threats that go unidentified by default cloud email security in Microsoft 365 and Google Workspace. Our clients are looking to reduce support overhead while bolstering cloud email protection to defend against threats like targeted spear phishing and business email compromise, making our solution ideal for their requirements. Tell us about your first paying customer and revenue expectations over the next year. Guardian Digital's roots are as an open-source Internet security company. It provides businesses of all sizes with solutions to common business security problems, such as user privacy solutions, firewalls, secure routers, and secure web servers. Our founder, Dave Wreski, started his infosec career at United Parcel Service when the commercial Internet was in its infancy. Dave found a way to use open source to build and install open source security solutions in local businesses that were equivalent to or exceeded the solutions UPS was paying hundreds of thousands of dollars per year for virtually the same protection provided by open source. Using this knowledge, his programming and development background, and the skills learned as the security architect for UPS, Dave built a company around this idea and started selling service and support solutions to small businesses—first in the local area to businesses that needed cheap but effective networking solutions, then online to thousands of businesses worldwide that needed a secure enterprise all-in-one server solution called EnGarde. EnGarde was our first business product, sold to tens of thousands of businesses worldwide, and set the foundation for Guardian Digital's current position. What’s your biggest threat? Our biggest threat is modern cyberattackers, who continue to try to outsmart the latest, most advanced security solutions. Cybersecurity is an ongoing “cat and mouse” game between threat actors and security providers. We are confident we can keep our clients ahead of the latest threats via advanced, layered open-source technology and expert system management, monitoring, and support.

"Over 90% of modern cyberattacks begin with a phishing email" says Guardian Digital CEO & Founder

"90% jila jichha pacha ciberataques ukax mä correo electrónico phishing ukampiw qalltawayi" sasaw Guardian Digital CEO & Founder jupax saraki

"Més del 90% dels ciberatacs moderns comencen amb un correu electrònic de pesca", diu el CEO i fundador de Guardian Digital.

„Über 90 % der modernen Cyberangriffe beginnen mit einer Phishing-E-Mail“, sagt CEO und Gründer von Guardian Digital

"Πάνω από το 90% των σύγχρονων επιθέσεων στον κυβερνοχώρο ξεκινούν με ένα ηλεκτρονικό "phishing" λέει ο Διευθύνων Σύμβουλος & Ιδρυτής της Guardian Digital

"Más del 90% de los ciberataques modernos comienzan con un correo electrónico de phishing", afirma el director ejecutivo y fundador de Guardian Digital

"Máis do 90% dos ciberataques modernos comezan cun correo electrónico de phishing", afirma o CEO e fundador de Guardian Digital.

「現代のサイバー攻撃の90%以上はフィッシングメールから始まる」とガーディアンデジタルのCEO兼創設者は語る

"Орчин үеийн кибер халдлагын 90 гаруй хувь нь фишинг цахим шуудангаар эхэлдэг" гэж Guardian Digital-ийн Гүйцэтгэх захирал, үүсгэн байгуулагч хэлэв.

"90% masnin kunan pacha ciberataques kaqmanta huk phishing correo electrónico kaqwan qallarinku" Guardian Digital CEO & Founder nin

„Viac ako 90 % moderných kybernetických útokov začína phishingovým e-mailom,“ hovorí generálny riaditeľ a zakladateľ Guardian Digital

“การโจมตีทางไซเบอร์ในยุคใหม่กว่า 90% เริ่มต้นจากอีเมลฟิชชิ่ง” CEO และผู้ก่อตั้ง Guardian Digital กล่าว

Guardian Digital CEO'su ve Kurucusu, "Modern siber saldırıların %90'ından fazlası kimlik avı e-postasıyla başlıyor" diyor

You may be wondering what DOCKERIZE is. It means using Docker to containerize your dApp project. Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. Applications include web apps, APIs, mobile apps, and backend services. It includes the code you write, the libraries you use, and the configurations needed for it to run. Infrastructure like operating system(OS), Network setting, web servers, database, and other services your application interacts with. It also involves the hardware or virtual machines where your application runs. Docker allows you to package and run your application as a single entity in a loosely isolated environment called a CONTAINER. Container Containers are lightweight and contain everything needed to run the application, so you don't need to rely on what's installed on the host. You can share containers while you work, and be sure that everyone you share with gets the same container that works in the same way. For example, you and your colleagues are working on a dApp project that uses Node.js and Hardhat. Initially, you set up the project on your local machine, knowing that before your colleagues can run the application locally, they would need to install Node.js and Hardhat on their systems. Now, let’s imagine one of your colleagues is using a machine that isn't compatible with Node.js and Hardhat. How would you solve this problem? With Docker, you can package your application, along with all its dependencies, into a single container that can run on any operating system. This solves the issue of installing software or dependencies separately on different machines. Images After you’ve containerized your application, how do you get it to run? As a frontend developer, when starting a new React app, you usually run npx create-react-app or npm init vite@latest. For an existing project, you'd typically run git pull followed by npm install to get it running locally. Similarly, to run a container, you need something called a container image. A container image is a standardized package that includes all the files, binaries, libraries, and configurations needed to run your application inside a container. It’s like having everything bundled together so it can run consistently across any environment. See below for a container image: Practicals In this section, you will learn how to containerize and share your app. Prerequisites You have installed the latest version of Docker Desktop.
You have installed a Git client.
You have an IDE or a text editor to edit files. Docker recommends using Visual Studio Code. Containerize Your Application In your root directory, initialize docker using this command prompt: docker init Provide answers to the prompts. ? What application platform does your project use? Node  
? What version of Node do you want to use? 20.16.0  
? Which package manager do you want to use? npm  
? Do you want to run "npm run build" before starting your server? No  
? What command do you want to use to start the app? ["npm", "run", "dev"]  
? What port does your server listen on? 5173 You will see three additional files in your directory, namely .dockerignore, compose.yaml and DockerFile. Dockerfile: A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image.
compose.yaml: The Compose file, or compose.yaml file follows the rules provided by the Compose Specification in how to define multi-container applications.
.dockerignore: This file excludes files and directories from the build context. Inside Dockerfile, clear out the file and add the following: # syntax=docker/dockerfile:1  
ARG NODE_VERSION=20.16.0  
FROM node:${NODE_VERSION}-alpine  
# Use development node environment by default.  
ENV NODE_ENV development  
WORKDIR /app  
# Copy package.json and package-lock.json to the working directory  
COPY package.json package-lock.json ./  
# Install dependencies  
RUN npm install  
# Copy the rest of the source files into the image  
COPY . .  
# Change ownership of the /app directory to the node user  
RUN chown -R node:node /app  
# Switch to the node user  
USER node  
# Ensure node_modules/.bin is in the PATH  
ENV PATH /app/node_modules/.bin:$PATH  
# Expose the port that the application listens on  
EXPOSE 5173  
# Run the application  
CMD ["npm", "run", "dev"] Build your container image using this: docker build -t <your-image-name> . To see your container image, go to your docker desktop, click on Images, as shown below  or you can use this command prompt, docker images to see your container image in your terminal.  6. Run the image: docker run -p 5173:5173 <your-image-name> You should see an output like this: > vite-project@0.0.0 dev
> vite

  VITE v5.4.2  ready in 222 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://172.17.0.2:5173/ Sharing the Application Sign up or Sign in to Docker Hub.
Select the Create Repository button.  
Name your repository with the same container image name. Make sure the Visibility is Public.
Select Create. Sign in to Docker Hub using the command line docker login -u <YOUR USERNAME> Enter your Password Your Password won’t be visible while typing Use the docker tag command to give the getting-started image a new name. Replace YOUR-USER-NAME with your Docker ID: You may encounter this denied: requested access to the resource is denied while pushing.
To fix this,

relogin using docker login, press enter.
After that, you will be navigated to your browser,
copy your OTP the terminal and input it,
press CONFIRM
repush the image

You will see an output like: This shows your image has been built and pushed into a registry. Your team can now pull this image and run the application on their local machine. You can check by searching for your container image on the search bar on your docker desktop or docker hub. Troubleshooting Port Conflict:

Error: if the port 8000 was already in use.
Solution: Identified the process using port 8000 and terminated it using the following commands: # Find the process using port 8000  
lsof -i :8000  
# Kill the process (replace <PID> with the actual process ID found from the previous command)  
kill -9 <PID> Alternatively, you could run the Docker container on a different port: docker run -p 8001:8000 my-vite-app Update an Application Anything you update your app. e.g., you change a syntax or function,

Stop your docker desktop, click on Containers
Stop the port, and click on delete.  
Rebuild the Application using the docker build command. docker build -t <your-image-name> . Rerun the app. docker run -p 5173:5173 <your-image-name> Conclusion By following this guide, you can easily package your application and its dependencies into a container, share it with your team, and run it easily on any machine. This not only enhances collaboration but also mitigates issues related to environment setup and compatibility. You may be wondering what DOCKERIZE is. It means using Docker to containerize your dApp project. DOCKERIZE DOCKERIZE Docker Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. applications infrastructure Applications include web apps, APIs, mobile apps, and backend services. It includes the code you write, the libraries you use, and the configurations needed for it to run. Applications include web apps, APIs, mobile apps, and backend services. It includes the code you write, the libraries you use, and the configurations needed for it to run. Applications Infrastructure like operating system(OS), Network setting, web servers, database, and other services your application interacts with. It also involves the hardware or virtual machines where your application runs. Infrastructure like operating system(OS), Network setting, web servers, database, and other services your application interacts with. It also involves the hardware or virtual machines where your application runs. Infrastructure Docker allows you to package and run your application as a single entity in a loosely isolated environment called a CONTAINER. CONTAINER. Container Containers are lightweight and contain everything needed to run the application, so you don't need to rely on what's installed on the host. You can share containers while you work, and be sure that everyone you share with gets the same container that works in the same way. For example, you and your colleagues are working on a dApp project that uses Node.js and Hardhat. Initially, you set up the project on your local machine, knowing that before your colleagues can run the application locally, they would need to install Node.js and Hardhat on their systems. Now, let’s imagine one of your colleagues is using a machine that isn't compatible with Node.js and Hardhat. How would you solve this problem? With Docker, you can package your application, along with all its dependencies, into a single container that can run on any operating system. This solves the issue of installing software or dependencies separately on different machines. Images After you’ve containerized your application, how do you get it to run? As a frontend developer, when starting a new React app, you usually run npx create-react-app or npm init vite@latest . For an existing project, you'd typically run git pull followed by npm install to get it running locally. Similarly, to run a container, you need something called a container image . npx create-react-app npm init vite@latest git pull npm install container image A container image is a standardized package that includes all the files, binaries, libraries, and configurations needed to run your application inside a container. It’s like having everything bundled together so it can run consistently across any environment. See below for a container image: Practicals In this section, you will learn how to containerize and share your app. Prerequisites You have installed the latest version of Docker Desktop. You have installed a Git client. You have an IDE or a text editor to edit files. Docker recommends using Visual Studio Code. You have installed the latest version of Docker Desktop . Docker Desktop You have installed a Git client . Git client You have an IDE or a text editor to edit files. Docker recommends using Visual Studio C ode. Visual Studio C ode. Containerize Your Application In your root directory, initialize docker using this command prompt: In your root directory, initialize docker using this command prompt: docker init docker init Provide answers to the prompts. Provide answers to the prompts. ? What application platform does your project use? Node  
? What version of Node do you want to use? 20.16.0  
? Which package manager do you want to use? npm  
? Do you want to run "npm run build" before starting your server? No  
? What command do you want to use to start the app? ["npm", "run", "dev"]  
? What port does your server listen on? 5173 ? What application platform does your project use? Node  
? What version of Node do you want to use? 20.16.0  
? Which package manager do you want to use? npm  
? Do you want to run "npm run build" before starting your server? No  
? What command do you want to use to start the app? ["npm", "run", "dev"]  
? What port does your server listen on? 5173 You will see three additional files in your directory, namely .dockerignore, compose.yaml and DockerFile. You will see three additional files in your directory, namely .dockerignore , compose.yaml and DockerFile. .dockerignore compose.yaml DockerFile. Dockerfile: A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image. compose.yaml: The Compose file, or compose.yaml file follows the rules provided by the Compose Specification in how to define multi-container applications. .dockerignore: This file excludes files and directories from the build context. Dockerfile : A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image. Dockerfile compose.yaml : The Compose file, or compose.yaml file follows the rules provided by the Compose Specification in how to define mul ti-container applications. compose.yaml compose.yaml Compose Specification in how to define mul .dockerignore : This file excludes files and directories from the build context. .dockerignore Inside Dockerfile, clear out the file and add the following: Inside Dockerfile , clear out the file and add the following: Dockerfile # syntax=docker/dockerfile:1  
ARG NODE_VERSION=20.16.0  
FROM node:${NODE_VERSION}-alpine  
# Use development node environment by default.  
ENV NODE_ENV development  
WORKDIR /app  
# Copy package.json and package-lock.json to the working directory  
COPY package.json package-lock.json ./  
# Install dependencies  
RUN npm install  
# Copy the rest of the source files into the image  
COPY . .  
# Change ownership of the /app directory to the node user  
RUN chown -R node:node /app  
# Switch to the node user  
USER node  
# Ensure node_modules/.bin is in the PATH  
ENV PATH /app/node_modules/.bin:$PATH  
# Expose the port that the application listens on  
EXPOSE 5173  
# Run the application  
CMD ["npm", "run", "dev"] # syntax=docker/dockerfile:1  
ARG NODE_VERSION=20.16.0  
FROM node:${NODE_VERSION}-alpine  
# Use development node environment by default.  
ENV NODE_ENV development  
WORKDIR /app  
# Copy package.json and package-lock.json to the working directory  
COPY package.json package-lock.json ./  
# Install dependencies  
RUN npm install  
# Copy the rest of the source files into the image  
COPY . .  
# Change ownership of the /app directory to the node user  
RUN chown -R node:node /app  
# Switch to the node user  
USER node  
# Ensure node_modules/.bin is in the PATH  
ENV PATH /app/node_modules/.bin:$PATH  
# Expose the port that the application listens on  
EXPOSE 5173  
# Run the application  
CMD ["npm", "run", "dev"] Build your container image using this: Build your container image using this: docker build -t <your-image-name> . docker build -t <your-image-name> . To see your container image, go to your docker desktop, click on Images , as shown below or you can use this command prompt, Images docker images docker images to see your container image in your terminal. 6. Run the image: docker run -p 5173:5173 <your-image-name> docker run -p 5173:5173 <your-image-name> You should see an output like this: > vite-project@0.0.0 dev
> vite

  VITE v5.4.2  ready in 222 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://172.17.0.2:5173/ > vite-project@0.0.0 dev
> vite

  VITE v5.4.2  ready in 222 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://172.17.0.2:5173/ Sharing the Application Sign up or Sign in to Docker Hub. Select the Create Repository button. Name your repository with the same container image name. Make sure the Visibility is Public. Select Create. Sign up or Sign in to Docker Hub. Sign up Docker Hub. Select the Create Repository button. Create Repository Name your repository with the same container image name. Make sure the Visibility is Public . Visibility Public Select Create . Create Sign in to Docker Hub using the command line Sign in to Docker Hub using the command line docker login -u <YOUR USERNAME> docker login -u <YOUR USERNAME> Enter your Password Enter your Password Your Password won’t be visible while typing Your Password won’t be visible while typing Use the docker tag command to give the getting-started image a new name. Replace YOUR-USER-NAME with your Docker ID: Use the docker tag command to give the getting-started image a new name. Replace YOUR-USER-NAME with your Docker ID: docker tag getting-started YOUR-USER-NAME You may encounter this denied: requested access to the resource is denied while pushing. To fix this, relogin using docker login, press enter.
After that, you will be navigated to your browser,
copy your OTP the terminal and input it,
press CONFIRM
repush the image You will see an output like: You may encounter this denied: requested access to the resource is denied while pushing. denied: requested access to the resource is denied To fix this, relogin using docker login, press enter. After that, you will be navigated to your browser, copy your OTP the terminal and input it, press CONFIRM repush the image relogin using docker login , press enter. docker login After that, you will be navigated to your browser, copy your OTP the terminal and input it, OTP press CONFIRM CONFIRM repush the image You will see an output like: This shows your image has been built and pushed into a registry. Your team can now pull this image and run the application on their local machine. You can check by searching for your container image on the search bar on your docker desktop or docker hub . docker hub Troubleshooting Port Conflict:

Error: if the port 8000 was already in use.
Solution: Identified the process using port 8000 and terminated it using the following commands: Port Conflict : Error: if the port 8000 was already in use.
Solution: Identified the process using port 8000 and terminated it using the following commands: Port Conflict Error: if the port 8000 was already in use. Solution: Identified the process using port 8000 and terminated it using the following commands: Error : if the port 8000 was already in use. Error 8000 Solution : Identified the process using port 8000 and terminated it using the following commands: Solution 8000 # Find the process using port 8000  
lsof -i :8000  
# Kill the process (replace <PID> with the actual process ID found from the previous command)  
kill -9 <PID> # Find the process using port 8000  
lsof -i :8000  
# Kill the process (replace <PID> with the actual process ID found from the previous command)  
kill -9 <PID> Alternatively, you could run the Docker container on a different port: Alternatively, you could run the Docker container on a different port: docker run -p 8001:8000 my-vite-app docker run -p 8001:8000 my-vite-app Update an Application Anything you update your app. e.g., you change a syntax or function,

Stop your docker desktop, click on Containers
Stop the port, and click on delete.  
Rebuild the Application using the docker build command. Update an Application Anything you update your app. e.g., you change a syntax or function, Stop your docker desktop, click on Containers
Stop the port, and click on delete.  
Rebuild the Application using the docker build command. Update an Application Anything you update your app. e.g., you change a syntax or function, Update an Application Stop your docker desktop, click on Containers Stop the port, and click on delete. Rebuild the Application using the docker build command. Stop your docker desktop, click on Containers Containers Stop the port, and click on delete. Rebuild the Application using the docker build command. docker build docker build -t <your-image-name> . docker build -t <your-image-name> . Rerun the app. Rerun the app. docker run -p 5173:5173 <your-image-name> docker run -p 5173:5173 <your-image-name> Conclusion By following this guide, you can easily package your application and its dependencies into a container, share it with your team, and run it easily on any machine. This not only enhances collaboration but also mitigates issues related to environment setup and compatibility.

A Beginner's Guide to Dockerizing a Vite dApp Project

የ Vite dApp ፕሮጀክትን ለመቆጠብ የጀማሪ መመሪያ

Guía para principiantes sobre cómo dockerizar un proyecto de dApp de Vite

Unha guía para principiantes para dockerizar un proxecto Vite dApp

Vite dApp プロジェクトを Docker 化する初心者向けガイド

დამწყებთათვის გზამკვლევი Vite dApp პროექტის დოკერიზაციისთვის

Panduan Pemula untuk Melabuhkan Projek Vite dApp

Vite dApp परियोजना डकराइज गर्नको लागि एक शुरुआती गाइड

Huk qallariqpa yanapakuynin huk Vite dApp Proyecto Dockerizing kaqpaq

Mwongozo wa Waanzilishi wa Kuweka Mradi wa Vite dApp

ንጀመርቲ መምርሒ ንዶከርይዝድ ፕሮጀክት ቫይት ዲኣፕ

“Vite dApp” taslamasyny dokerlemek üçin başlangyç gollanma

Hướng dẫn cho người mới bắt đầu về Dockerizing một dự án dApp Vite

Stories, News & Mentions about BEGIN

Begin’s Stories on HackerNoon