Skip to content

Instantly share code, notes, and snippets.


Amin Khansari akhansari

  • D-Edge
  • France
  • 08:16 (UTC +01:00)
View GitHub Profile
View windows-lcid-iso
1078 af
1052 sq
14337 ar-ae
15361 ar-bh
5121 ar-dz
3073 ar-eg
2049 ar-iq
11265 ar-jo
13313 ar-kw
akhansari / gist:10023621
Last active Aug 29, 2015
Generating an MD5 Hash from a string.
View gist:10023621
public string MD5Hash(string str)
return string.Join("", System.Security.Cryptography.MD5.Create()
.ComputeHash(System.Text.Encoding.UTF8.GetBytes(str)).Select(s => s.ToString("x2")));
akhansari / XmlTools.iss
Last active Feb 24, 2022
Xml tools for InnoSetup
View XmlTools.iss
function LoadValueFromXML(const AFileName, APath: string): string;
XMLNode: Variant;
XMLDocument: Variant;
Log('Get Xml text node: ' + AFileName);
Result := '';
View sampleClass.js
// class
var Greeter = (function () {
// constructor
function Greeter(message) {
// public variable
this.greeting = message;
akhansari /
Last active Dec 15, 2017
Guidelines and rules for GetHashCode

Guidelines and rules for GetHashCode

What is GetHashCode used for?

It is by design useful for only one thing: putting an object in a hash table. Hence the name.

Why do we have this method on Object in the first place?

It makes perfect sense that every object in the type system should provide a GetType method; data's ability to describe itself is a key feature of the CLR type system. And it makes sense that every object should have a ToString, so that it is able to print out a representation of itself as a string, for debugging purposes. It seems plausible that objects should be able to compare themselves to other objects for equality. But why should it be the case that every object should be able to hash itself for insertion into a hash table? Seems like an odd thing to require every object to be able to do.

akhansari / tasks.json
Created Feb 28, 2018
VSCode task for Hugo with error detection.
View tasks.json
"version": "2.0.0",
"tasks": [
"label": "Hugo",
"type": "shell",
"command": "hugo serve",
"group": "build",
"isBackground": true,
"problemMatcher": {
akhansari /
Created Oct 28, 2019 — forked from swlaschin/
Effective F#, tips and tricks


  • Use Onion architecture

    • Dependencies go inwards. That is, the Core domain doesn't know about outside layers
  • Use pipeline model to implement workflows/use-cases/stories

    • Business logic makes decisions
    • IO does storage with minimal logic
    • Keep Business logic and IO separate
  • Keep IO at edges

akhansari / event-sourced-user.fsx
Last active Dec 16, 2022
F# : Event Sourcing in a nutshell
View event-sourced-user.fsx
// ========= Event Sourcing in a nutshell
FriendlyName: string
Aggregate friendly name.
Initial: 'State
Initial (empty) state we will start with.
Decide: 'Command -> 'State -> 'Event list
akhansari / Program1-Minimal.fs
Last active Feb 11, 2022
F# : Different ways to create an API without a dependency
View Program1-Minimal.fs
open System
open Microsoft.AspNetCore.Builder
open Microsoft.AspNetCore.Http
open Microsoft.AspNetCore.Routing
type Item = { Id: int32; Name: string; Price: decimal }
let rnd = Random()
let getProducts () =
[ for _ in 1..3 do { Id = rnd.Next 100; Name = "Blueberry"; Price = 10m } ]
akhansari / onion-1.fs
Last active Sep 22, 2022
F# : Onion architecture in a nutshell
View onion-1.fs
// 1. pure, don't think about IO at all
module Domain =
let add x y = x + y
// 2. think about IO but not its implementation
module App =
let add (getX: unit -> Async<int32>) y =
async {
let! x = getX ()
return Domain.add x y