Skip to content

Instantly share code, notes, and snippets.

View SinaKarimi7's full-sized avatar
🌌
in parallel worlds

Cinna SinaKarimi7

🌌
in parallel worlds
  • Pale Blue Dot, Milky Way
View GitHub Profile
@realbardia
realbardia / main.cpp
Last active February 5, 2025 11:58
Very simple Neural Network using C++
#include <iostream>
#include <vector>
#include <cmath>
#include <cstdlib>
#include <ctime>
#include <random>
using namespace std;
// Activation and Derivative functions
@tavallaie
tavallaie / secure_erase.sh
Last active February 26, 2025 06:08
**Secure Data Erasure Script (Bash)** This Bash script securely erases data from a specified device with random data, ensuring irrecoverability. Use with caution.
#!/bin/bash
# Check if the script is run with superuser privileges
if [ "$EUID" -ne 0 ]; then
echo "Please run this script as root (sudo)."
exit 1
fi
# Prompt the user for the target devices
read -p "Enter the target devices (e.g., /dev/sdX /dev/sdY): " target_devices
@m-esm
m-esm / extract_tweets.js
Last active February 26, 2025 05:08
Extract tweets from browser
if (!window.tweets) window.tweets = {};
/**
* @param tweetElem {HTMLElement}
*/
window.parseTweetElement = (tweetElem) => {
const isQuote = !!Array.from(tweetElem.querySelectorAll("span")).find(
(p) => p.textContent === "Quote"
);
@afzouni
afzouni / shit-for-brains.md
Last active October 27, 2022 13:26
Shit for Brains - Block List Farsi Twitter

Total Accounts: 50,550 (2022-09-24)

Block List

List of Accouns is Here contains JSON, CSV and Raw Text.

Accouts gathering using Like Blockers and below links are theirs API.

Changelog:

  • 2022-09-19 (1 to 52)
  • 2022-09-24 (53 to 242) - by @torabkheslat and @MohammadJavadJamali
@JafarAkhondali
JafarAkhondali / getunicodes.py
Last active February 22, 2023 09:40
Finds all unicode characters that produce at least one character in ASCII range when converted to Uppercase or Lowercase.
"""
Finds all unicode characters that produce at least one character in ASCII range when converted to Uppercase or Lowercase.
Result:
Char ß with code(223) to uppercase contains ASCII char(S). Full uppercase: SS
Char ß with code(223) to uppercase contains ASCII char(S). Full uppercase: SS
Char İ with code(304) to lowercase contains ASCII char(i). Full lowercase: i̇
Char ı with code(305) to uppercase contains ASCII char(I). Full uppercase: I
Char ʼn with code(329) to uppercase contains ASCII char(N). Full uppercase: ʼN
Char ſ with code(383) to uppercase contains ASCII char(S). Full uppercase: S
addEventListener("fetch", (event) => {
event.respondWith(handleRequest(event));
});
let data = {
ok: false,
};
async function handleRequest(event) {
if (event.request.method == "POST") {
let body = await event.request.json();
if (body.url && body.title && body.telemark_code) {
@mhmda-83
mhmda-83 / excuses.json
Last active July 26, 2024 11:35
Devloper Excuses (extracted from http://developerexcuses.com/)
[
"The program has never collected that information",
"That wasn't in the original specification",
"The project manager told me to do it that way",
"There's currently a problem with our hosting company",
"Well done, you found my easter egg!",
"That feature would be outside of the scope",
"This code was not supposed to go in to production yet",
"The client must have been hacked",
"I'm still working on that as we speak",
@prologic
prologic / LearnGoIn5mins.md
Last active March 23, 2026 03:33
Learn Go in ~5mins
@ih2502mk
ih2502mk / list.md
Last active May 1, 2026 04:33
Quantopian Lectures Saved

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.