F*: A Higher-Order Effectful Language Designed for Program Verification
F* (pronounced F star) is a general-purpose functional programming language with effects aimed at program verification. It puts together the automation of an SMT-backed deductive verification tool with the expressive power of a proof assistant based on dependent types.
6.1 PowerShell Core متشر شد.
درک مفهوم شردینگ دیتابیس
یک الگوی طراحی دیتابیس در حالت پارتیشن بندی افقی است. بیشتر برای زمانی مفید است که توسعه دیتابیس به صورت پویا مدنظر باشد.
Any application or website that sees significant growth will eventually need to scale in order to accommodate increases in traffic. For data-driven applications and websites, it's critical that scaling is done in a way that ensures the security and integrity of their data. It can be difficult to predict how popular a website or application will become or how long it will maintain that popularity, which is why some organizations choose a database architecture that allows them to scale their databases dynamically.
کوئری در معماری CQRS
croc ابزاری است که به هر دو کامپیوتری امکان انتقال ساده و ایمن فایلها و فولدرها را می دهد.
croc
is a tool that allows any two computers to simply and securely transfer files and folders. AFAIK, croc is the only CLI file-transfer tool that does all of the following:
- allows any two computers to transfer data (using a relay)
- provides end-to-end encryption (using PAKE)
- enables easy cross-platform transfers (Windows, Linux, Mac)
- allows multiple file transfers
- allows resuming transfers that are interrupted
- local server or port-forwarding not needed
- ipv6-first with ipv4 fallback
نوشتن کوئریهای بهینه در EF
- Writing efficient queries with Entity Framework Code First - Part 1
- Writing efficient queries with Entity Framework Code First - Part 2
- Writing efficient queries with Entity Framework Code First - Part 3
- The Four Deadly Sins of LINQ Data Access: Part 1–Overly Chatty Queries
- The Four Deadly Sins of LINQ Data Access: Part 2–Too Many Columns
- The Four Deadly Sins of LINQ Data Access: Part 3–Insufficiently Chatty Queries
- The Four Deadly Sins of LINQ Data Access: Part 4–Too Many Rows
سری آموزشی کار با GitHub
Vertical Slice Architecture, not Layers!
Why Vertical Slice Architecture? Nobody wants to deal with a system that is hard to change and easy to introduce bugs because it's a spaghetti code mess of various technical concerns. Clean Architecture is popular because it separates concerns into many different layers. But why are we organizing code by layers? Does adding a new feature require you to modify files across multiple projects in your UI, business, and data access layers? Vertical Slice Architecture is about how you organize code and focus on features instead of technical layers will make your system easier to change.