Preact.js - Fast 3kB alternative to React with the same ES6 API. If you’re looking for a VDOM implementation without all the abstraction, you must try this out. Been using it for a year or so, and have had many successes.
Disclaimer: Chrome 58 is the version of Chrome/Dev Tools I used when doing this episode. If you are on the stable version of chrome - it’s updated roughly every two-three weeks for minor releases, and every 6 weeks for major releases. So ye be warned, what I may say, where things may be, etc, could change if you’re listening tooth’s in the future.
What is Chrome dev tools?
How do I access it?
Select More Tools > Developer Tools from Chrome’s Main Menu.
Right-click a page element and select Inspect.
Press Command+Option+I (Mac) or Control+Shift+I (Windows, Linux).
Three dots vertically stacked on top of each other.
Click on this menu and hover over the three icons that are shown to the right of ‘Dock side’.
Choose your poison, personal preference
sometimes choose right side, when going into device emulating for example, some people choose the pop out window
Right click select ‘inspect’
Styles panel (double click, and change any value).
Computed panel, (double click on the box model picture where there are values, you can change these!)
First thing at the top is a visual representation of the box model of the element you selected.
You can edit all the values around the box model!
Below the box model visual, is a list of the actual computed CSS properties, meaning after all the applied styles, these are the ones that ‘won’, and are applied to the element after the cascade.
You can click the ‘Show all’ checkbox, and it will even show you the browser-specific styles applied to the element in question. Meaning you can see what you may need to override to get the styles you want for that element.
You can just start typing JS functions, things in global scope are here, and can be called
If jQuery is on the page you’re inspecting, for example, you can type $(‘selector’) and it will show that element in the console
Hit enter to do command
Multi line script you’re typing in? Hit shift+enter to go down a line, but not execute what you already typed in.
You are running in the context of the page of you’re on.
Type ‘document.body’ hit enter…it’s the html of the page, hover over things here in the console, and see those highlighted on the page
You can do things to the webpage here
document.body.style = ‘background: yellow’; will show the background of the page you’re looking at with yellow
Refresh the page, things are lost, if you’re saving/running things here.
Command or Control P to open file. Any file loaded on the page, image, JS, font, video.
Left panel organized by domain, with the top one being the page you’re looking at in the browser.
Next things might be extensions you have loaded in chrome
The domain at the top is what your current page is, the other domains below are what assets that may have been included on this page from other domains such as google analytics for example.
Can click through folder/file hierarchy here.
You can edit this files in place (refresh will blow your changes away), and save them if you choose.
Find a CSS file, click on it. is it all on one line?
Click on the curly braces in the lower left hand corner, pretty formatted for you!
Spike is a next-generation static site generator. It is built on top of webpack, and a foundation of html, css, and js parsers that accept plugins to transform the output. It’s fast, actively developed, and very data-friendly.
Read as, new static site generator based on Webpack, Babel, PostCSS, and Reshape. Seems like a toolset I would like.
I’ve never heard of Reshape before. Seems new. Git commit messages say, Aug 9, 2016 was first commit.
The story of how @WalmartLabs successfully migrated to React and Nodejs with efficiency and speed. At the end of this talk, you should be able to make your own successful strategy to transform your technology stack quickly and successfully.
What does a migration mean?
FE apps take about 10,000/rps
2 dozen apps comprise @walmartlabs
70% of Walmart.com traffic is on React and Node
Next year samsclub.com traffic will be on Electrode too
Took less than a year for them to migrate.
50 - 60% walmart users on mobile
responsiveness here was slow
productivity of engineers was slowing down (java, handlebars, etc)
Built the platform team first, small, cohesive, and versatile (full stack)
while simultaneously building organizational alignment - met with leaders, set realistic expectations, talked through concerns
anxiousness can spread through organization quickly; talk to leaders thougout the org, and talk through why it’s happening; make sure the business side is onboard and understands why
with some headway into the platform, we then built the vertical team: senior, bought in, vocal, distributed
distributed in terms of organization location
this team will be your future ambassadors
next we united the Platform and Vertical teams
Now you needed to decide on the first application to migrate: not too simple or complex, not business critical, server side render, bought in
we chose the ‘collections application’, choose collections of things
once we hose collections and started building, there was a constant feedback loop, to refine the platform and process
the application went live (about a month)
we continually monitored and fine-tuned: performance, conversion, scalability, reusability
Next Application? Walmart.com Checkout: client-side rendered, complex, single page application, business critical
Rinse and repeat
Finally, all the other applications start migrating (search, login, my account, profile pages)
This is where the ambassadors Play a Key Role
the small team is protected, and you don’t get crushed by requests from the organization; this larger vertical team can help with that (every single team has a person there with deep knowledge of the system)
currently onboarding Samsclube.com
What are the benefits we’re seeing?
impact on customer experience:
90% functional automation
40% reduction in bundle size
60% improvement in response time
impact on developer productivity
3x faster from code to production
Training days down from 5 days to 1 day
First commit from 7 days to 1
Improved talent recruiting
these kinds of things, changes the culture of the company