Skip to content

Instantly share code, notes, and snippets.

View shajanjp's full-sized avatar
🎯
Wiring up zeros and ones

Shajan Jacob shajanjp

🎯
Wiring up zeros and ones
View GitHub Profile
@shajanjp
shajanjp / semantic-responsive-sidebar.html
Created October 29, 2018 10:35
Responsive Sidebar for Semantic
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Document</title>
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css">
</head>
<body>
<div class="ui sidebar inverted vertical menu">
<a class="item">
{
"parserOptions": {
"ecmaVersion": 6
},
"extends": "google",
"rules": {
"require-jsdoc": [
"off"
],
"max-len": ["warn"]
@shajanjp
shajanjp / index.js
Created February 6, 2018 07:02
timeOut
// `npm install robotjs` before running
let robot = require("robotjs");
let curTime;
let tym;
let inMinutes;
robot.setMouseDelay(2);
let screenSize = robot.getScreenSize();
let height = (screenSize.height / 2) - 10;
@shajanjp
shajanjp / image_magick_hacks.md
Last active November 2, 2017 06:30
ImageMagick Script Hacks
convert sample-avatar.jpeg -resize 250x250^ -gravity center -crop 250x250+0+0 result.jpg
@shajanjp
shajanjp / .bashrc
Created October 29, 2017 15:22
Custom Bash style with git support
parse_git_branch() {
git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/ (\1)/'
}
export PS1="\u@\h \[\033[32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\]$ "
@shajanjp
shajanjp / unsolicited_advice_to_junior_developers.md
Created October 27, 2017 09:25
Unsolicited Advice To Junior Developers

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

  • Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

  • Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

  • Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

  • Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get