In this guide, I’ll walk you through every step of building my Dactyl Manuform keyboard, from soldering diodes to flashing firmware. This was my very first keyboard build, so I didn’t go fancy with customization or aesthetics (I didn’t even use a bottom plate, as I’ll explain in the Post-Mortem Analysis section).
So the current total size of my website is 7.46 KB, to be exact
They act as endpoints in a two-way communication channel.
For communication of two machines or applications each app/machine creates a socket.
Each socket is associated with IP and port.
OSI
Sockets operate at layer 4 - transport layer.
Application layer calls down the socket api, for example browser, backend server etc
I will be adding the things i usb c-fied in my life to this post, i am too lazy to write tutorial but one day i might edit this.
Starting with my Natural Ergonomic Keyboard 4000.
In this blog post, we’ll dive into the concept of domain models, explore the differences and discuss how these choices impact your software design.
WTH is a Domain Model?
Instead of saying something like "the term domain model refers to an abstraction that represents the real-world concepts and behaviors of a system" i find that stackoverflow reply more helpful:
If you were to take your program and strip away the gui and the DBMS, and replace it with a command line interface, and a MySQL server instance, then port the whole thing to a different platform with different system calls and file system access api calls, the part that you didn't change in that process is the domain model.
Types of Domain Models
My touchpad felt laggy and jumpy on my Lenovo Yoga 7 after a week i bought it. It starts with finger rubbing and it is not OS related doesnt go away if i dont press to hard on it to make it contact with something on the body and release the static energy. I opened up the laptop and observed the issue and its grounding problem.
When you have different objects and services that does different things and developed by different teams how do you connect them becomes an issue.
DI is a design pattern that aims to decouple object from their dependencies. Instead of creating their own dependencies internally, object receive them from an external source. By using DI we can configure as needed at runtime; with DI dependencies injected at runtime rather than at compiling.
Dependency injection works together perfectly with SOLID principles.
Single Responsibility Principle - DI can help you isolate responsibility of class.
Open-Closed Principle - With new functionalities we can inject new dependencies instead of changing code base.
Dependency Inversion Principle - Dependencies depend on interfaces instead of concrete classes.
There are three types of DI: Constructor Injection, Setter Injection and Interface Injection.
I will give examples as POJO classes, this pattern can be applied to any language and there are solutions in Spring and .NET.
I will build an awesome(?) music lister that lists your musics from particular artist.
When developing an API for a business, one of the key requirements often revolves around managing different user types and their respective permissions. In this scenario, we'll focus on three user types: admin, individual user, and corporate user.
User Roles Overview:
In this post, we’ll focus on implementing the authentication and authorization mechanisms necessary to enforce these roles, ensuring the system adheres to the statelessness principle of REST.
 | |
| Authentication vs Authorization image from javatpoint.com |
An architectural pattern that models the state changes made by applications as an immutable sequence
or “log” of events. Instead of modifying the state of the application
in-place.
Generally with crud applications we hold only current state not how we got there. That might be issue for some applications. For example lets think an online banking application. If only thing they can see is current balance not how they got to that balance, no withdrawal, deposit or fee history.