So you want to write a sync system for a web app with offline and realtime support? Good luck. You might find the following resources useful.
Database in a browser, a spec (Stepan Parunashvili)
What problem are we trying to solve with a sync system?
The web of tomorrow (Nikita Prokopov)
| Concept | Definition |
|---|---|
| Autonomy | How well will this company give me autonomy to do my job? |
| Freedom | How much freedom will I have to balance work and personal life? |
| Responsibilities | What level of responsibilities will I have, and how extensive will they be? |
| Culture | How well does this company's culture align with my values, and how open is the company to allowing me to contribute to the culture I believe in? |
| Tech Stack | How closely does the tech stack used by this company align with my preferences, and to what extent is the company willing to allow me to use the stack I prefer? |
| Personal Growth | How big is the potential of this company to help me keep growing? |
Getting confused about the piles of development tools that people use for Javascript? Here's a quick index of what is used for what.
Keep in mind that you shouldn't add tools to your workflow for the sake of it. While you'll see many production systems using a wide range of tools, these tools are typically used because they solved a concrete problem for the developers working on it. You should not add tools to your project unless you have a concrete problem that they can solve; none of the tools here are required.
Start with nothing, and add tools as needed. This will keep you from getting lost in an incomprehensible pile of tooling.
Typical examples: Gulp, Grunt
| import { combineReducers } from 'redux'; | |
| // Define the context to search files | |
| const CONTEXT = require.context('./', true, /\.\/(.*)\/index.js?$/i); | |
| // Populate a object with the reducer | |
| const importReducer = (req) => (obj, path) => { | |
| const [, componentName] = path.match(/\.\/(.*)\/index.js?$/i); | |
| const reducer = { | |
| [componentName]: req(path).default |
| // connect() is a function that injects Redux-related props into your component. | |
| // You can inject data and callbacks that change that data by dispatching actions. | |
| function connect(mapStateToProps, mapDispatchToProps) { | |
| // It lets us inject component as the last step so people can use it as a decorator. | |
| // Generally you don't need to worry about it. | |
| return function (WrappedComponent) { | |
| // It returns a component | |
| return class extends React.Component { | |
| render() { | |
| return ( |
| /* | |
| ##Device = Desktops | |
| ##Screen = 1281px to higher resolution desktops | |
| */ | |
| @media (min-width: 1281px) { | |
| //CSS | |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
