Manheim, CSS Style Injection & Apprenticeships

Most of us know very little about the Dealer Auction Company Manheim. But, they are doing a great job promoting innovation not only for them & Cox (their parent company) but also the development community as a whole in Atlanta. I was impressed with their blending of professional development and partnership with Atlanta Fullstack. “As always this blog is more for my sanity than you.”

 

manheim_logo_eu

Style Injection

React‘s use of JSX a format that through transpilers such as Babel has allowed us to embedded our HTML into our JavaScript has opened the doors to even more componentization in our apps. Now, the idea is slowly gaining traction to also place our CSS in components as well. (You can find a link to the presentation here). I like the idea of continuing to build components (when you can) that are compartmentalized with all of the pieces of the puzzle in one place (as long as that puzzle is nice and simple). A few frameworks mentioned were:

RADIUM

JSS

CSSX

 

A HUGE Company Building An Apprenticeship Program

I think it is awesome that a large company is thinking about developing talent rather than hunting it down. It makes sense for Manheim, they are a Rails organization (I think) which means (and I’m stereotyping) that many of the potential developers they are going to attract are not from a traditional CS background (I think of bootcamps), it allows them to cultivate quality talent on a trial basis, it takes HR out of the equation. I could not find a link to their fall program but here is one to this summers application.

Advertisements
Manheim, CSS Style Injection & Apprenticeships

Notes From ReactATL Meetup

logo_og

Great time tonight at ReactATL Meetup hosted by Andrew Smith and Taggart Bowen-Gaddy. It was an open format where people could come in with questions or examples and just talk code. “Like always this is more for my sanity than yours”.

Andrew, talked about dealing with Redux and components the problems that come from multiple components using the same state. He talked about using Reselect and NuclearJS to deal with this with the creation of selectors. I have to be honest I need to dig into it to understand it but, both seem to have good documentation (I’ll add to the list of 45 other libraries I need to look at).

Taggart talked about FalcorJS, which is Netflix’s answer to data management between the server and client built for React.  He showed a proof of concept he has been working on for his team. It is basically a mutable  JSON file. You basically send out a call for a defined box and the server will work to fetch that data and manipulate what is in the box. This box can cache to keep from having to continuously update the whole file. I thought about the idea of “closures” for JSON data transfers (note: I could be completely wrong about this). He also talked in Redux about not using a true Action Generator file and instead holding the Actions in the Components to keep from experiencing errors due to poorly called or worded dispatches.

I showed off some simple React examples I have run up. They were good examples for the guys who had not seen Redux. You can access them below and compared the differences in main components between regular React and React Redux:

Weather App

Timer App,

Todo App w/ Redux (note: I am adding authentication and moving this over to Firebase so if you notice a functionality issue, sorry)

PS. I think Google’s Firebase is VOODOO. You can find the source code for these projects on my GitHub.

Notes From ReactATL Meetup

Take Aways From Atlanta NodeJS Meetup

Awesome time at my first NodeJS Atlanta Meetup. I was a much smaller group than they usually have so it allowed a lot of young developers to ask questions. Having only ran up simple NodeJS servers so far it was a great experience to hear from some who sit on the backend all the time. Here are a couple takeaways:

“As always this is for my sanity, not yours”

ARE PROMISES CURRIED FUNCTIONS?

I dig Promises, they make things simple to understand. If something resolves .then() do this next thing. New work on Promises and ES6 HERE (not sure I understand it all).

Function currying is creating a function that takes # variables and creating a copy of that function that takes a different # of variables:

Screen Shot 2016-05-20 at 11.51.11 AM

MY TAKE IS YES?…….MAYBE?

Yes, if we look at both currying and promises as guaranteeing something to be passed to the next function from a function that has finished executing (Closure).

 

HOW TO LAND A JOB DISCUSSION

Michael Gokey, Industry Veteran-

Fix a problem for me. Show me you can fix a problem I have in the interview. When you get in the door keep doing that for EVERYONE! The Business Dev guy had a $2 Million presentation on the line and his computer went down. Rather than shrug it off, I set him up on my computer. It took me off line for 3 hours, but I fixed a problem, helped him and I in the long run.

Also, there is a huge separation in opinions on the value of GitHUB with younger developers and hiring managers focusing on it and older developers not feeling that it has much value.

 

LEARNING FROM THE VETS

I enjoyed connecting afterwards with long time developers. Couple things on the list to check out:

Codality

Bower

Google Style Guide for JavaScript

Idiomatic JavaScript

 

Take Aways From Atlanta NodeJS Meetup