Skip to content

Instantly share code, notes, and snippets.

View Maharramoff's full-sized avatar
🇦🇿

Maharramoff

🇦🇿
View GitHub Profile
@Maharramoff
Maharramoff / java-formatter.xml
Created October 23, 2024 11:12
Java formatter settings
<?xml version="1.0" encoding="utf-8"?>
<profiles version="21">
<profile kind="CodeFormatterProfile" name="Default" version="21">
<setting id="org.eclipse.jdt.core.formatter.tabulation.char" value="space"/>
<setting id="org.eclipse.jdt.core.formatter.use_tabs_only_for_leading_indentations" value="false"/>
<setting id="org.eclipse.jdt.core.formatter.indentation.size" value="4"/>
<setting id="org.eclipse.jdt.core.formatter.tabulation.size" value="4"/>
<setting id="org.eclipse.jdt.core.formatter.text_block_indentation" value="0"/>
<setting id="org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_type_header" value="true"/>
<setting id="org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_declaration_header" value="true"/>
@Maharramoff
Maharramoff / GitCommitEmoji.md
Created March 29, 2023 13:11 — forked from parmentf/GitCommitEmoji.md
Git Commit message Emoji
@Maharramoff
Maharramoff / API Contract Example Spec.md
Created January 10, 2023 22:00 — forked from BeattieM/API Contract Example Spec.md
An example of an API contract between the server and front-end devices

#Users

  • User object
{
  id: integer
  username: string
  email: string
  created_at: datetime(iso 8601)
  updated_at: datetime(iso 8601)
}

So, are you building microservices? Take a look at a few of these symptoms, and decide for yourself:

  • ❌ A change to one microservice often requires changes to other microservices
  • ✅ Deploying one microservice requires other microservices to be deployed at the same time
  • ❓ Your microservices are overly chatty
  • ❌ The same developers work across a large number of microservices
  • ✅ Many of your microservices share a datastore
  • ✅ Your microservices share a lot of the same code or models
@Maharramoff
Maharramoff / project-structure.md
Created October 11, 2022 07:17
Project Structure

🗄️ Project Structure

Most of the code lives in the src folder and looks like this:

src
|
+-- assets            # assets folder can contain all the static files such as images, fonts, etc.
|
+-- components # shared components used across the entire application
@Maharramoff
Maharramoff / JavaScript Hacks.md
Created July 14, 2022 11:52 — forked from nurmdrafi/JavaScript Hacks.md
JavaScript Hacks by Rafé
@Maharramoff
Maharramoff / gist:effb94c04ef17548b4a435f1e16cf931
Created October 13, 2021 08:24 — forked from igal/gist:53855
.gitrc aliases for common git commands
# Aliases for common git commands. E.g., enter "git d" for "git diff"
# These settings live in the ~/.gitconfig file.
[alias]
b = branch
ba = branch -a
ci = commit
co = checkout
d = diff
dc = diff --cached
@Maharramoff
Maharramoff / JetbrainsEvaluationReset_2020.py
Created June 5, 2021 19:00 — forked from mreyesv/JetbrainsEvaluationReset_2020.py
[Activate] A Python Script To Reset The Evaluation License Of These Jetbrains Products Released In 2020 Or Later (IntelliJIdea, CLion, Rider, PyCharm, RubyMine, GoLand )
# Reset Jetbrains 2020 Products
import glob
import os
import winreg
from os import path
from os.path import expanduser
home = expanduser("~")
newJetbrainsHome = path.join(home, "AppData\Roaming\JetBrains")
@Maharramoff
Maharramoff / git-layout-for-client-customizations.txt
Created January 23, 2021 09:51 — forked from abeham/git-layout-for-client-customizations.txt
Discusses approaches to structure a git repository for software that is customized for several clients
Consider a software that is customized for each client. It contains common components, modules, and
client-specific customizations thereof. For instance,
Common
+ Common.ClientA
+ Common.ClientB
ModuleA
+ ModuleA.ClientB
ModuleB
+ ModuleB.ClientA