Skip to content

Instantly share code, notes, and snippets.

View shoaibk-dev's full-sized avatar

Shoaib Khan shoaibk-dev

View GitHub Profile

JSTL

collection of custom tag libraries for solving common problem such as;

  • iteration, collection and conditional
  • for processing xml document, formatting text, accessing database, and data manipulation

for manipulating scoped objects (out, set, remove) for performing conditional tests (if, choose, when, otherwise) for iterating over a collection or token (forEach, forTokens) parsing and formatting dates and numbers (parseNumber, formatNumber, parseDate, formatDate, etc)

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
<SOAP-ENV:Body>
<return>
<labparameters>
<identifier>attrFlag</identifier>
<priSeg>OBX</priSeg>
<priPos1>8</priPos1>
<priPos2>0</priPos2>
<secSeg>OBX</secSeg>
<secPos1>8</secPos1>
@shoaibk-dev
shoaibk-dev / System Design.md
Created January 4, 2019 19:09 — forked from vasanthk/System Design.md
System Design Cheatsheet

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

  1. Clarify and agree on the scope of the system
  • User cases (description of sequences of events that, taken together, lead to a system doing something useful)
    • Who is going to use it?
    • How are they going to use it?

FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.


Effective Engineer - Notes

What's an Effective Engineer?

@shoaibk-dev
shoaibk-dev / 0-startup-overview.md
Created December 31, 2018 16:06 — forked from dideler/0-startup-overview.md
Startup Engineering notes
// statically typed - type is enforced
// dynamically typed - infer variables at runtime
// weakly typed - allow type to be inferred as another type [1 + '2' = '12' => it coerce number into string]
// type coercion - process of converting value from one type to another
// type coercion can be imlicit[operators to value of different types] or explicit[type casting - Number(value)]
// === strict equality operator => does not trigger implicit type coercion [both type and value we're compairing have to be the same]
// == loose equality operator on the other hand does both comparision and type coercion [77 == '77' => true - perform type coercion]
// three type of conversion in js: to string, to boolean, to number
// conversion login for primitive and object work differently but both can only be converted to those three ways
@shoaibk-dev
shoaibk-dev / The Technical Interview Cheat Sheet.md
Created December 20, 2018 05:59 — forked from tsiege/The Technical Interview Cheat Sheet.md
This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon.

Studying for a Tech Interview Sucks, so Here's a Cheat Sheet to Help

This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.

Data Structure Basics

###Array ####Definition:

  • Stores data elements based on an sequential, most commonly 0 based, index.
  • Based on tuples from set theory.
For life and for Code
This picture was taken from the book: “Code Complete — Steve McConnell” from the section call Problem Definition where talks about
how the first prerequisite you need to fulfill before beginning construction is a clear statement of the problem that the system is
supposed to solve (sometimes call “product vision” or “mission statement”).
Key Points for this chapter:
A problem definition defines what the problem is without any reference to possible solutions.
Good : “We can’t keep up with orders from XYZ”
Bad : “We need to optimize our data-entry system to keep up orders from XYZ”
Java EE6 Web Profile, is a slimmed-down, "lite" version of Java that includes the APIs developers are most likely to need to
build Web applications. Over time, the Java EE has grown very large and complex.
Most applications don't require the full version of Java EE. The Java Community introduced the Web Profile in Java EE 6 to reduce
the download and runtime sizes for applications that don't need the full version.
The goal of Web Profile is to allow developers to create web applications with the appropriate set of technologies.
Table 1-3. Web Profile 7 Specification
Specification Version URL
JSF 2.2 http://jcp.org/en/jsr/detail?id=344