Imed Adel imedadel

You have an array. Its sort order doesn't matter. You want to remove an item from this array.

The obvious thing to do would be to use splice:

function remove(array, item) {
  const index = array.indexOf(item);
  array.splice(index, 1);
}

4. Specialize in the New

You already know the value of a niche - you go up in market value the more specialized you are in anything. So what do you specialize in?

There are many schools of thought, including ones where you could be a generalist that doesn't specialize in anything. I find one rule to be simplest and most effective above all: Specialize in the New.

Didn't we just agree to avoid FOMO? Well yes, thats an important distinction - don't specialize in everything new. Specializing means you have to say no to a lot of things. Just pick something new that fascinates you, and hopefully many others as well. Since you're learning in public, you'll know when you hit on a real nerve. Budget in the idea that you'll fail a few times before you find Your Thing.

Then the other big objection: There are plenty of jobs/money/etc in (fill in the blank older technology) too! This is usually followed by some big numbers and anecdata. "My brother's cousin's roommate's friend took this COBOL job and now he's ear

3. Clone Open Source Apps

You already know you should be making projects to learn things and potentially add to your portfolio. You've read your Malcolm Gladwell, you know that you need 10,000 hours of deliberate practice. Given you're just starting out, I have a slightly contentious suggestion for you: DON'T make anything new.

Your decision-making is a scarce resource. You start every day with a full tank, and as you make decisions through the day you gradually run low. We all know how good our late-late-night decisions are. Making a new app involves a thousand micro decisions - from what the app does, to how it should look, and everything in between. Decide now: Do you want to practice making technical decisions or product decisions?

Ok so you're coding. You know what involves making zero product decisions? Cloning things. Resist the urge to make your special snowflake (for now). Oh but then who would use yet another Hacker News clone? I've got news for you: No one was gonna use your thing anyway. You

Note:

When this guide is more complete, the plan is to move it into Prepack documentation.
For now I put it out as a gist to gather initial feedback.

A Gentle Introduction to Prepack (Part 1)

If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code:

Babel lets you use newer JavaScript language features, and outputs equivalent code that targets older JavaScript engines.

	// This is a proper alternative to
	// https://github.com/BuckleScript/bucklescript/blob/b9508105b1a35537bdea9a1fabd10f6c65f776b4/jscomp/bsb/templates/react-hooks/src/FetchedDogPictures/FetchedDogPictures.re#L14
	// The one in that file uses Promise, but that's wrong.
	// We only used promise as a demo of its API. We'll remove it soon.

	// As you can see below, the pure XMLHttpRequest code is just as clean,
	// less mysterious for all, more performant, extensible, and actually correct.

	// Ignore these externals for now. They're just for illustration
	// purposes. I just copy pasted the Js code from


	const Chosed = (props) => {
	const elmt = React.useRef()

	React.useLayoutEffect(()=>{
	const $elmt = $(elmt.current)
	const handleChange = (e) => {
	props.onChange(e.target.value);
	}
	$elmt.chosen()

	<div id="root">
	<div class="full-page-loader">
	<img width="200" src="/logo/aiptrade-vertical-color-color.png" alt="AIP.Trade logo" />
	</div>
	</div>

	<template>
	<div id="app">
	<!-- <img src="./assets/logo.png">
	<HelloWorld msg="Welcome to Your Vue.js App"/> -->
	<div class="reveal">
	<div class="slides">
	<section>Single Horizontal Slide</section>
	<section>
	<section>Vertical Slide 1</section>
	<section>Vertical Slide 2</section>

	const CrossOriginLocalStorage = function(currentWindow, iframe, allowedOrigins, onMessage) {
	this.allowedOrigins = allowedOrigins;

	let childWindow;
	// some browser (don't remember which one) throw exception when you try to access
	// contentWindow for the first time, it works when you do that second time
	try {
	childWindow = iframe.contentWindow;
	} catch(e) {
	childWindow = iframe.contentWindow;

	# Example Dockerfile
	FROM hello-world