Sonicrida Sonicrida

Moved to Shopify/graphql-design-tutorial

Adding manpower to a late software project makes it later.

Development managers often win their management roles primarily from having been stellar coders while displaying a modicum of people skills.

Programming teams can tell management that the product is one week from being functionally complete every week for the months.

A program can produce the desired results and be so poorly designed and/or executed that it cannot realistically be enhanced or maintained.

For too many managers (especially less technical managers, such as CEOs or CFOs) prototypes appear to be “done.”

[7:50 PM] acemarke: @jon.m : fwiw, I always have learned best when I had a project I was working on, and needed to implement some feature I'd never built before
[7:50 PM] acemarke: nothing motivates you to learn a particular concept or technology like needing it to build a feature
[7:50 PM] acemarke: ie, "learn generators" isn't terribly useful or motivating
[7:51 PM] acemarke: but "I need to make my async code easier to read / build a complex async logic feature, and Redux-Saga requires use of generator functions" is more of a specific motivation
[7:52 PM] acemarke: now, there's nothing wrong with going out and reading up on a specific feature - promises, generators, observables, etc
[7:52 PM] acemarke: always great to have more tools in the toolbox
[7:52 PM] acemarke: but ultimately you need something to apply those tools to
[7:52 PM] CPT: I agree. Having motivation helps
[7:52 PM] jon.m: I keep seeing this TreeHouse commercial on youtube that says a guy g

[8:27 PM] cquill: @acemarke Right, so many portions of the UI will be connected. But does each connected portion typically get its own container component? Seems verbose and redundant to have the following for each CRUD resource: UserList, UserListContainer, UserView, UserViewContainer, UserEdit, UserEditContainer, UserNew, UserNewContainer. Is there a simpler way?
[9:56 PM] acemarke: @cquill : this leads into one of my favorite (?) semi-rants, and one that I apparently need to write down so I can paste it
[9:57 PM] acemarke: A "container" component is simply any component whose primary job is to fetch data from somewhere, and pass that data on to its children
[9:58 PM] acemarke: With Redux, the wrapper components generated by connect are "container" components, since their job is to extract data from the Redux store
[9:58 PM] acemarke: I generally dislike the somewhat-common approach of trying to divide everything into a "components" folder and a "containers" folder
[9:59 P

There are a number of good introductory SQL resources available for free and online. There are also some paid resources which I recommend for beginners, that are very effective, and well worth expensing in my opinion.

A couple of notes:

I haven’t used all of these resources, but they come with strong recommendations around the web or myself/my peers.
You absolutely don’t need to use every single resource. Find a couple that work for you, and go to town.
You can always reach out to me if you have questions. I always paste this online when people are new to asking very technical questions – it’s not meant to be snarky – it's a gentle guide on how to compose your questions and gather necessary resources in order to best give technical people the information needed to get a quick/effective response: http://www.mikeash.com/getting_answers.html

Video/Class/Mini-course based:

Stanford Self-paced ‘Database’ course

The original Coursera

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

	import { take, put, call, fork, cancel, cancelled } from 'redux-saga/effects'

	import {EVENT_POLLING_START, EVENT_POLLING_STOP} from "constants/eventPolls";
	import {ClientEventType} from "constants/serverEvents";



	function* handleEventA(serverEvent) {
	yield put({type : serverEvent.type, payload : {name : serverEvent.eventAData}});
	}

	// The classic AJAX call - dispatch before the request, and after it comes back
	function myThunkActionCreator(someValue) {
	return (dispatch, getState) => {
	dispatch({type : "REQUEST_STARTED"});

	myAjaxLib.post("/someEndpoint", {data : someValue})
	.then(
	response => dispatch({type : "REQUEST_SUCCEEDED", payload : response}),
	error => dispatch({type : "REQUEST_FAILED", error : error})
	);

	// === Arrays

	var [a, b] = [1, 2];
	console.log(a, b);
	//=> 1 2


	// Use from functions, only select from pattern
	var foo = () => [1, 2, 3];