Skip to content

Instantly share code, notes, and snippets.

@wynand1004
wynand1004 / top_secret_decoder.py
Created October 10, 2017 00:05
Top Secret Decoder Practice
# Top secret decoder
# The CIA has discovered a plot against a major city
# SIGINT has intercepted a message with the location and date of the attack
# Unfortunately, the message is encoded.
# Due to your awesome Python skills, you have been hired to decode the message
# A double agent has provided the encoding scheme which is as follows:
# All numbers need to be changed to spaces
# All capital letters should be changed to *
# The lowercase letter q is equal to \n
# All other lowercase letters should be ignored.

I've recently joined Amazon Dublin from India and got opportunities to interview with Meta London, Zalando Berlin & some other companies. I extensively researched about companies hiring internationally which support visa & relocation for Tech roles. So sharing list of companies:

Do consider to STAR, if it helped you.

London

@rveitch
rveitch / falloutshelter_json_decrypt.php
Last active May 13, 2024 20:16
Fallout Shelter - Save Game File to JSON Decryption
<?php
/**
* Fallout Shelter - Save Game File to JSON Decryption
*/
/*
The save data is simply Rijndael CBC encrypted json using the passphrase "PlayerData" (without the quotes)
and the salt "tu89geji340t89u2" (without the quotes) stored in a file called Vault1.sav, Vault2.sav, or Vault3.sav
Locations:
Android = /sdcard/Android/data/com.bethsoft.falloutshelter/files/Vault*.sav
@wojteklu
wojteklu / clean_code.md
Last active May 13, 2024 20:15
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules

@FlorSanders
FlorSanders / JetsonNano2GB_LlamaCpp_SetupGuide.md
Created April 11, 2024 15:17
Setup llama.cpp on a Nvidia Jetson Nano 2GB

Setup Guide for llama.cpp on Nvidia Jetson Nano 2GB

This is a full account of the steps I ran to get llama.cpp running on the Nvidia Jetson Nano 2GB. It accumulates multiple different fixes and tutorials, whose contributions are referenced at the bottom of this README.

Procedure

At a high level, the procedure to install llama.cpp on a Jetson Nano consists of 3 steps.

  1. Compile the gcc 8.5 compiler from source.
@define-private-public
define-private-public / HttpServer.cs
Last active May 13, 2024 20:08
A Simple HTTP server in C#
// Filename: HttpServer.cs
// Author: Benjamin N. Summerton <define-private-public>
// License: Unlicense (http://unlicense.org/)
using System;
using System.IO;
using System.Text;
using System.Net;
using System.Threading.Tasks;
@bbqtd
bbqtd / macos-tmux-256color.md
Last active May 13, 2024 20:04
Installing tmux-256color for macOS

Installing tmux-256color for macOS

  • macOS 10.15.5
  • tmux 3.1b

macOS has ncurses version 5.7 which does not ship the terminfo description for tmux. There're two ways that can help you to solve this problem.

The Fast Blazing Solution

Instead of tmux-256color, use screen-256color which comes with system. Place this command into ~/.tmux.conf or ~/.config/tmux/tmux.conf(for version 3.1 and later):

@cheerfulstoic
cheerfulstoic / Repository Maintenance Levels.md
Last active May 13, 2024 20:03
Repository Maintenance Levels

After reading Why I'm Frequently Absent from Open Source by James Long and listening the corresponding The Changelog episode, I dwelt on the idea and believe that open source maintainers...

  • ... should never be ashamed if they don't have time for a project.
  • ... should be honest with themselves and open with their users so that everybody can be on the same page
  • ... are people and they have at one time or another responsibilities or hardships that they need to attend to which reasonably take them away from a project
  • ... may also reasonbly decide that they don't like the direction of a project or that they would like to explore other things and may leave a project permanently.

Along this line of thinking I've created a set of descriptions for different levels at which a project might be maintained. A maintainer can use these to announce to their users the current ability that they have to dedicate to a pr

@Hellisotherpeople
Hellisotherpeople / blog.md
Last active May 13, 2024 20:04
You probably don't know how to do Prompt Engineering, let me educate you.

You probably don't know how to do Prompt Engineering

(This post could also be titled "Features missing from most LLM front-ends that should exist")

Apologies for the snarky title, but there has been a huge amount of discussion around so called "Prompt Engineering" these past few months on all kinds of platforms. Much of it is coming from individuals who are peddling around an awful lot of "Prompting" and very little "Engineering".

Most of these discussions are little more than users finding that writing more creative and complicated prompts can help them solve a task that a more simple prompt was unable to help with. I claim this is not Prompt Engineering. This is not to say that crafting good prompts is not a difficult task, but it does not involve doing any kind of sophisticated modifications to general "template" of a prompt.

Others, who I think do deserve to call themselves "Prompt Engineers" (and an awful lot more than that), have been writing about and utilizing the rich new eco-system